Strange error related to arm-none-eabi-nm.exe

[LOuroboros]

So, I was injecting the DPE in a clean ROM of Pokémon FireRed v1.0 to check some things out, and as the process was reaching its end, I got the following error twice:

While a test.gba ROM was generated successfully, I gave it a quick test run and the game freezes as I'm about to receive my starter in Oak's Lab.
I have Python v3.7.9 and a fresh install of Windows' version of devkitPro, meaning that by extension I'm using devkitARM r56. Dunno if that changes anything.

This was working fine the last time I tried it almost 2 months ago.

[mason101516]

Try applying cfru and check will the starter scene freeze again

[LOuroboros]

Try applying cfru and check will the starter scene freeze again

I still got the same error I mentioned before twice even when injecting the CFRU, but that did solve the freeze when picking a starter.

I kept playing a bit more and the game seems to be lagging whenever you try to navigate the start menu though.

Untitled5768.mp4

In any case, both projects should be usable in a standalone matter imo, so yeah.

[KrisYarno]

There seems to be a redundant file "libdep.dll.a" in the stated folder (C:\devkitPro\devkitARM\lib\bfd-plugins). I don't believe "libdep.dll.a" should exist as "libdep.dll" should be the file loaded as "libdep.dll.a" is not a shared library? That would explain the error I think. I deleted the "libdep.dll.a" so the folder only contained "libdep.dll" [removed the file ending in '.a']

That solved the error for me

Edit: Upon testing the game still freezes after receiving the starter pokemon. Not sure if the dll issue and the freezing are related?

[LOuroboros]

A valid workaround for this problem is to use an older build of devkitARM, such as r47.
Those builds are no longer distributed officially because its developers are dead set on pushing everyone to always use the latest versions of their tools though, so whoever wants to work around the errors that impede to use these injections until they're solved will have to either build devkitARM from its source code, or use an unofficial build instead.

There's a nice guy called Leseratte10 who hosts his builds of the different devkitPro tools right here.
Simply download, extract, go to C:\devkitPro\devkitARM, move all the folders in there somewhere safe for later restoration, and put the files of the r47 instead.
If the path to C:\devkitPro\devkitARM\bin and the path to Python v3.7 are present in the PATH Environment Variable, things will work.