Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

build.sh does not build libgcc/libgcc.a, required by install.sh #1

Closed
PikalaxALT opened this issue Apr 30, 2016 · 5 comments
Closed

Comments

@PikalaxALT
Copy link
Contributor

No description provided.

@PikalaxALT PikalaxALT changed the title build.sh does not build libgcc.a, required by install.sh build.sh does not build libgcc/libgcc.a, required by install.sh Apr 30, 2016
@PikalaxALT
Copy link
Contributor Author

PikalaxALT commented Apr 30, 2016

I should note that I'm using 32-bit Cygwin with devkitARM-r45-i686 + libgba + gba examples. Entering the libgcc and running make raises this error about 6 times:

/bin/sh: line 5: /opt/devkitpro/devkitARM/bin/arm-none-eabi-as: cannot execute binary file: Exec format error

Tried the x86-64 build as well, same result.

@ghost
Copy link

ghost commented Apr 30, 2016

That is odd. I have not used cygwin. If you are on Windows, you can use the compiled files I have made at https://github.com/YamaArashi/pokeruby-tools. If you really want to build this yourself, I would recommend using the MSYS environment that comes with devkitARM rather than cygwin.

@ghost
Copy link

ghost commented Apr 30, 2016

OK. I have installed cygwin and was able to successfully build this without any errors. How did you install devkitARM and why is it within your cygwin "/opt" directory?

huderlem pushed a commit that referenced this issue Dec 30, 2018
 Fix installation of ld, binutils, and gas in directory, and apply better indentation style to gas/
@ketsuban
Copy link

I had this problem and it turned out I'd forgotten to set the DEVKITPRO and DEVKITARM environment variables.

@rawr51919
Copy link

rawr51919 commented Jan 27, 2020

I had this problem and it turned out I'd forgotten to set the DEVKITPRO and DEVKITARM environment variables.

Does this mean that this issue has been fixed? I guess that means that we should be doing something to update those environment variables somehow.

RevoSucks pushed a commit that referenced this issue Sep 3, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants