- gcc updated to 4.6.0.
- binutils updated to 2.21.
- newlib updated to 1.19.0.
- ndstool extraction now working on amd64.
- grit fixes for shared palette creation.
devkitARM release 33
-
- Site Admin
- Posts: 1989
- Joined: Tue Aug 09, 2005 3:21 am
- Location: UK
- Contact:
devkitARM release 33
The binaries for devkitARM release 33 are now available. As usual the windows binary is available through the Automated Installer/Updater, for other platforms check the devkitARM getting started page on the wiki.
Re: devkitARM release 33
i got
process monitor show that collect2 tried to open folowing files:
\devkitARM\arm-eabi\bin\arm-eabi-ld.exe
\devkitARM\bin\arm-eabi-arm-eabi-ld.exe
looks like unnecessary prefix used. is it my setup problem or bug in devkitarm?
then tried linking something with -flto flag.collect2: cannot find 'ld'
process monitor show that collect2 tried to open folowing files:
\devkitARM\arm-eabi\bin\arm-eabi-ld.exe
\devkitARM\bin\arm-eabi-arm-eabi-ld.exe
looks like unnecessary prefix used. is it my setup problem or bug in devkitarm?
-
- Site Admin
- Posts: 1989
- Joined: Tue Aug 09, 2005 3:21 am
- Location: UK
- Contact:
Re: devkitARM release 33
Seems like a bug, sorry. I'll have a look & see if I can figure out where it went wrong.
Only seems to show up with the -flto option and only on windows as far as I can tell atm.
Only seems to show up with the -flto option and only on windows as far as I can tell atm.
Re: devkitARM release 33
anyway it doesn't work i copy linker to needed name and got errors like described here.WinterMute wrote:Seems like a bug, sorry.
-
- Site Admin
- Posts: 1989
- Joined: Tue Aug 09, 2005 3:21 am
- Location: UK
- Contact:
Re: devkitARM release 33
that's a bit sneaky :p
add -mcpu=arm946e-s to your compile flags, assuming this is DS code. If it's the same problem I saw then it looks like the --with-cpu=arm7tdmi configure option is causing -mcpu=arm7tdmi to be emitted in the compile flags when using -flto.
add -mcpu=arm946e-s to your compile flags, assuming this is DS code. If it's the same problem I saw then it looks like the --with-cpu=arm7tdmi configure option is causing -mcpu=arm7tdmi to be emitted in the compile flags when using -flto.
Who is online
Users browsing this forum: No registered users and 4 guests