arm-none-eabi-gcc can't actually compile anything

support for the ARM toolchain
Post Reply
Zeturic
Posts: 2
Joined: Sat Feb 23, 2019 4:22 am

arm-none-eabi-gcc can't actually compile anything

Post by Zeturic » Sat Feb 23, 2019 4:46 am

Apologies if this is in the wrong board.

I am on 64-bit Windows 10 and I used the installer. I opted to only include the files for GBA development. After doing a clean install, I can't actually compile anything.

I get no output, and the return code is 1.

Code: Select all

$ /opt/devkitpro/devkitARM/bin/arm-none-eabi-gcc --version
arm-none-eabi-gcc.exe (devkitARM release 51) 8.2.0
Copyright (C) 2018 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

$ cat test.c
void foo() {}

$ /opt/devkitpro/devkitARM/bin/arm-none-eabi-gcc -c test.c

$ echo $?
1
And, just to be extra clear, no it doesn't create a test.o.

The same thing happens regardless of what I try to compile.

User avatar
fincs
( ͡° ͜ʖ ͡°)
Posts: 46
Joined: Mon Jul 12, 2010 9:45 pm
Location: Seville, Spain
Contact:

Re: arm-none-eabi-gcc can't actually compile anything

Post by fincs » Sat Feb 23, 2019 4:23 pm

Hi,

Windows version of tools rely on being put on PATH in order to find certain DLLs. If you're getting started with GBA development, we recommend checking out the GBA examples, including the template project. We designed a build system that allow any project to compile on any supported OS (Windows/Linux/Mac), and it also takes care of the PATH issue automatically. Please check it out :)

For more information, read Build System on the wiki.
Donate to devkitPro - help us stay alive!

Zeturic
Posts: 2
Joined: Sat Feb 23, 2019 4:22 am

Re: arm-none-eabi-gcc can't actually compile anything

Post by Zeturic » Sat Feb 23, 2019 8:17 pm

Old versions worked, so I didn't even consider that r51 might be so sensitive to its environment.

Anyway, thank you.

WinterMute
Site Admin
Posts: 1367
Joined: Tue Aug 09, 2005 3:21 am
Location: UK
Contact:

Re: arm-none-eabi-gcc can't actually compile anything

Post by WinterMute » Sun Feb 24, 2019 11:38 am

r51 isn't "sensitive to its environment". devkitARM/bin needs to be in path at compile time so the tools gcc runs can find the required dlls.
Help keep devkitPro toolchains free, Donate today

devkitPro IRC support
Personal Blog

Post Reply

Who is online

Users browsing this forum: No registered users and 3 guests