[Other] [HELP] libgcc.a not found

[InvisibleMountain]

I'm fairly certain I've followed the instructions on install.md exactly. However, when I run

./install.sh ..pokeemerald

, I get the result

cp: cannot stat 'libgcc.a': No such file or directory

. What's causing this and how can I fix it?

 

[Lunos]

I'm fairly certain I've followed the instructions on install.md exactly. However, when I run

./install.sh ..pokeemerald

, I get the result

cp: cannot stat 'libgcc.a': No such file or directory

. What's causing this and how can I fix it?

Did you build agbcc by using ./build.sh first?
Also, are you sure that's the actual error?
A picture of your terminal could be helpful.

 

[InvisibleMountain]

Yes, I did exactly what was said in the install.md instructions. Here is what the error looks like:

 

[Lunos]

Yes, I did exactly what was said in the install.md instructions. Here is what the error looks like:

A-ha, that picture attached in your post does show the actual error. Your terminal isn't finding your installation of devkitPro/devkitARM.
Did you install devkitPro at all? Since you're on Linux, you'll need to install devkitPro Pacman.

 

[InvisibleMountain]

You were right, I had to install it from docker. But there's another problem now. When I build, I get an error saying that there is no rule to make target '/base_tools'. I thought I could get around it by renaming the makefile into base_tools, but then I get an error saying there is no rule to make target 'clean'. I tried copying the makefile and renaming one into base_tools, but that just returned to the first error. Am I missing something here? What can I do?

 

[Lunos]

When I build, I get an error saying that there is no rule to make target '/base_tools'.

Your shell/terminal is still not recognizing your installation of devkitPro/devkitARM.

I thought I could get around it by renaming the makefile into base_tools, but then I get an error saying there is no rule to make target 'clean'. I tried copying the makefile and renaming one into base_tools, but that just returned to the first error. Am I missing something here? What can I do?

"base_tools" is just a script that tells the repository where each tool from devkitPro that is needed can be found, so yeah, doing any change to the makefile is pointless.

I wish I could help you more, but I'm not exactly a Linux user myself, so I'm not sure how things work there beyond the basic setup to get the decomps building, which has never given me any troubles, personally.

EDIT: One thing I could suggest you to try, is to use echo $DEVKITPRO and/or echo $DEVKITARM on your terminal.
If the paths to devkitpro and devkitARM show up normally, I'm out of ideas.
If they don't show up though, then the solution is simple. You'll have to introduce these commands one by one, reopen the Terminal and try to build agbcc again.

export DEVKITPRO=/opt/devkitpro
echo "export DEVKITPRO=$DEVKITPRO" >> ~/.bashrc
export DEVKITARM=$DEVKITPRO/devkitARM
echo "export DEVKITARM=$DEVKITARM" >> ~/.bashrc

 

[InvisibleMountain]

Both devkitpro and devkitARM show their paths properly (I think).

I thought it might have something to do with the makefile, so I changed the "include" part and it seems to have brought me a little farther, but there are new errors. By the way, I really appreciate you helping me thus far. Sometimes I'm unsure if I express my thanks clearly enough over the Internet.

 

[Lunos]

Both devkitpro and devkitARM show their paths properly (I think).

I thought it might have something to do with the makefile, so I changed the "include" part and it seems to have brought me a little farther, but there are new errors. By the way, I really appreciate you helping me thus far. Sometimes I'm unsure if I express my thanks clearly enough over the Internet.

At this point, the only thing I could suggest you is to ask for help in Pret's Discord server, as there's a high chance you can receive proper help there.
You can find an invitation in the README of any of their projects, including Pokeemerald's.

 

[InvisibleMountain]

Alright, thank you!