agbcc icon indicating copy to clipboard operation
agbcc copied to clipboard

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

Open marinalunaterry opened this issue 5 years ago • 8 comments

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

marinalunaterry avatar May 09 '20 05:05 marinalunaterry

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.

PikalaxALT avatar May 09 '20 10:05 PikalaxALT

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.

BigBahss avatar Jun 09 '20 15:06 BigBahss

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

PikalaxALT avatar Jun 09 '20 15:06 PikalaxALT

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?

BigBahss avatar Jun 09 '20 16:06 BigBahss

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

EduApps-CDG avatar Oct 24 '20 19:10 EduApps-CDG

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 !!

lilystudent2016 avatar Jan 11 '21 14:01 lilystudent2016

Fixed in #37

rawr51919 avatar Jun 24 '22 17:06 rawr51919

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)

rawr51919 avatar Jun 26 '22 00:06 rawr51919