devkitARM built from source on FreeBSD
Posted: Wed Aug 08, 2012 10:29 pm
Hello,
I have been trying to compile devkitPro on my FreeBSD computer, hoping to eventually develop stuff for my Nintendo DS lite. I have just finished compilation, but I haven't tested yet whether the cross-compiler is correct.
In the process I have found several issues with the build scripts, so I was wondering how much interest there is in my detailing the issues and the solutions I have found.
I guess some of them will not be of any interest (for example, FreeBSD has no libdl and the dl_* functions are in libc, so -ldl has to be removed from binutils build), but others are genuine problems in the build scripts (for example, libgba not being built but expected by maxmod) and/or in the packages (for example, maxmod calling arm-eabi-strip when it has been replaced by arm-none-eabi-strip), and still others are nitpicking (for example, bzip2 -cd $archive | tar -x -C $targetdir, relies on tar reading standard input by default, which is not guaranteed (it tries to read first tape device on FreeBSD, even when there is no tape device), so adding a -f- switch make it sounder).
So, should I put together a list of such issues, along with patches, or should I just keep all that to myself?
Thanks a lot for the nice toolchain,
Natasha
I have been trying to compile devkitPro on my FreeBSD computer, hoping to eventually develop stuff for my Nintendo DS lite. I have just finished compilation, but I haven't tested yet whether the cross-compiler is correct.
In the process I have found several issues with the build scripts, so I was wondering how much interest there is in my detailing the issues and the solutions I have found.
I guess some of them will not be of any interest (for example, FreeBSD has no libdl and the dl_* functions are in libc, so -ldl has to be removed from binutils build), but others are genuine problems in the build scripts (for example, libgba not being built but expected by maxmod) and/or in the packages (for example, maxmod calling arm-eabi-strip when it has been replaced by arm-none-eabi-strip), and still others are nitpicking (for example, bzip2 -cd $archive | tar -x -C $targetdir, relies on tar reading standard input by default, which is not guaranteed (it tries to read first tape device on FreeBSD, even when there is no tape device), so adding a -f- switch make it sounder).
So, should I put together a list of such issues, along with patches, or should I just keep all that to myself?
Thanks a lot for the nice toolchain,
Natasha