Rockbox Development > Starting Development and Compiling
Issues with making Gigabeat S build
(1/1)
Mad Cow:
With the latest SVN revision, 18432, I can't compile the Gigabeat S bootloader. It makes it to the end, then spews out error messages like this:
--- Quote ---/usr/local/arm-elf/lib/gcc/arm-elf/4.0.3/../../../../arm-elf/bin/ld: ERROR: /usr/local/arm-elf/lib/gcc/arm-elf/4.0.3/libgcc.a(_udivsi3.o) uses FPA instructions, whereas /home/user/rockbox/gigaboot/bootloader/bootloader.elf does not
--- End quote ---
I'm using the newest vmware image with the latest vmware player. I've never seen this error before so I have no idea what it means. Is the issue with SVN or am I doing something wrong?
EDIT: Just realized that this happens when compiling even a normal build for the S, compiling for the gigabeat F works perfectly though. Is there an issue with the gigabeat s build script?
EDIT: Fixed it, ran rockboxdev.sh and everything was fine. Now I have a new problem though, I can't seem to get it mounted in the vmware image, which doesn't allow me to fix the filesystem as per instructions. Dmesg shows nothing useful, how do I find out where it's mounted?
NicolasP:
It won't mount because the partition table needs to be fixed. You just need to know which block device it is (e.g /dev/sdb). The dmesg output should tell you this.
Mad Cow:
I guess I worded it wrong, but still, dmesg doesn't say anything like that, I've already tried the vmware image which is debian and I'm going to try pendrive linux soon.
EDIT: That worked, now my gigabeat is up and running. :) Mods, you can delete or lock this thread if you want.
NicolasP:
It would probably be even more helpful for others who might have this issue if you described what you did to fix the problem.
Mad Cow:
I just booted off a live version of pendrive linux and used fdisk from there.
Navigation
[0] Message Index
Go to full version