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

Makefile:1: /base_tools: No such file or directory #32

Open
marinalunaterry opened this issue May 9, 2020 · 8 comments
Open

Makefile:1: /base_tools: No such file or directory #32

marinalunaterry opened this issue May 9, 2020 · 8 comments

Comments

@marinalunaterry
Copy link

marinalunaterry commented May 9, 2020

Hi, when I run build.sh I get the following issues at the end, and it leads me to not be able to use install.sh afterward I think because of a lack of libgcc.a and libc.a. Here's the error:

Makefile:1: /base_tools: No such file or directory
make: *** No rule to make target '/base_tools'. Stop.
make: Leaving directory '/home/marina/git/agbcc/libgcc'

Edit: To clarify, when I try running install.sh after this I get thrown:
cp: cannot stat 'libgcc.a': No such file or directory

@PikalaxALT
Copy link
Contributor

You need to define the DEVKITPRO and DEVKITARM environment variables. Also, don't ever try to install if the build failed - this should be a no-brainer.

@BigBahss
Copy link

BigBahss commented Jun 9, 2020

I was having this same issue, even after following the instructions closely and trying again from scratch multiple times. My DEVKITPRO and DEVKITARM environment variables were defined, so that clearly wasn't the issue.

Here's what I found. The build was failing because it couldn't find the file:
'/opt/devkitPro/devkitARM/base_tools'
So I checked to make sure that the file exists. What do you know, it does exist, except the directory 'devkitPro' was misnamed as 'devkitpro'. Manually renaming this directory solved the issue.

I haven't looked very deep into this issue, so I don't know what is responsible for creating/naming this directory, but maybe a more enlightened individual could shed some light on this matter. I will say that my OS is Manjaro (Arch) and I made sure all my software was up-to-date before starting the process.

@PikalaxALT
Copy link
Contributor

@BigBahss That is a problem with how you defined your environment variables. Manually renaming the directory is not the correct solution.

@BigBahss
Copy link

BigBahss commented Jun 9, 2020

I believe I've found the problem, 'pokeemerald/INSTALL.md' instructs you to define DEVKITPRO like this:
export DEVKITPRO=/opt/devkitPro
Yeah, it tells you to define it as 'devkitPro', not 'devkitpro'. As far as I can see, every other resource tells you to define it in all lowercase, including devkitpro.org. I was following the pokeemerald instructions, so it's not a problem with how I defined it.

After writing this I went and took a closer look at the INSTALL.md file in pokeemerald. The most recent commit on that changes it from 'devkitpro' to 'devkitPro'. So at this point I'm honestly just very confused why this inconsistency exists. Is there a purpose for this that I'm not getting?

@EduApps-CDG
Copy link

I'm with Ubuntu and i'm having same issue

@lilystudent2016
Copy link

I met same issue in win10 wsl2 Ubuntu. It took me long time to find up how to solve it.

Ubuntu needs sudo command to run ./build.sh and sudo command would reset all environment variables.
So the DEVKITPRO and DEVKITARM will be lost.

Just using sudo visudo command changes Defaults env_reset to Defaults !env_reset in /etc/sudoers.

You will sucessfully complete sudo ./build.sh now!
Good luck have fun !!

@rawr51919
Copy link

Fixed in #37

@rawr51919
Copy link

rawr51919 commented Jun 26, 2022

If this issue comes up for you again, do the following if you're on Ubuntu Linux:

sudo apt install arm-none-eabi-binutils

This will allow you to install agbcc without the need for devkitpro/devkitarm
Something to easily add to a README I figure (added a stub in #57)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
6 participants