Open shoober420 opened 3 weeks ago
We already have avr, arm, riscv binutils packages https://packages.msys2.org/search?q=binutils
I already had binutils
, mingw-w64-x86_64-binutils
, mingw-w64-cross-binutils
, mingw-w64-i686-binutils
, mingw-w64-ucrt-x86_64-binutils
, mingw-w64-clang-x86_64-binutils
, and mingw-w64-clang-i686-binutils
installed. I went ahead and installed mingw-w64-clang-x86_64-avr-toolchain
, mingw-w64-x86_64-avr-toolchain
, and mingw-w64-ucrt-x86_64-avr-toolchain
but continue to get the same error. Installing those toolchains will install mingw-w64-clang-x86_64-avr-binutils
, mingw-w64-x86_64-avr-binutils
, mingw-w64-ucrt-x86_64-avr-binutils
, and other required package dependencies. Im not using an ARM, RISCV, POWERPC, or M68K processor so I skipped those packages. I think binutils-mips-linux-gnu
is its own seperate package, and is required if another package asks for it. The "zelda64recomp" PKGBUILD is asking for it specifically (https://aur.archlinux.org/packages/zelda64recomp).
sounds like fun, I guess this is not just mips, but gcc as well?
I made my own PKGBUILD, and created a mingw-w64-mips-linux-gnu-binutils
package.
When running make init
, I now get this build error.
make init rm -f -r rm -f -r build/n64-us/assets rm -f -r assets/text/*.h rm -f -r .extracted-assets.json rm -f -r build/n64-us rm -f -r asm data extracted make -C tools clean make[1]: Entering directory '/home/RavenWolf-/mm/tools' rm -f vtxdis make -C ZAPD clean make[2]: Entering directory '/home/RavenWolf-/mm/tools/ZAPD' rm -rf build ZAPD.out make -C lib/libgfxd clean make[3]: Entering directory '/home/RavenWolf_-/mm/tools/ZAPD/lib/libgfxd' rm -f gfxd.o uc_f3d.o uc_f3db.o uc_f3dex.o uc_f3dexb.o ucf3dex2.o libgfxd.a make[3]: Leaving directory '/home/RavenWolf-/mm/tools/ZAPD/lib/libgfxd' make -C ZAPDUtils clean make[3]: Entering directory '/home/RavenWolf-/mm/tools/ZAPD/ZAPDUtils' rm -rf build ZAPDUtils.a make[3]: Leaving directory '/home/RavenWolf-/mm/tools/ZAPD/ZAPDUtils' make -C ExporterTest clean make[3]: Entering directory '/home/RavenWolf-/mm/tools/ZAPD/ExporterTest' rm -rf build ExporterTest.a make[3]: Leaving directory '/home/RavenWolf-/mm/tools/ZAPD/ExporterTest' make[2]: Leaving directory '/home/RavenWolf-/mm/tools/ZAPD' make -C fado clean make[2]: Entering directory '/home/RavenWolf-/mm/tools/fado' rm -f -r build fado.elf make[2]: Leaving directory '/home/RavenWolf-/mm/tools/fado' make -C buildtools clean make[2]: Entering directory '/home/RavenWolf-/mm/tools/buildtools' rm -f mkdmadata mkldscript relocprereq make[2]: Leaving directory '/home/RavenWolf-/mm/tools/buildtools' make[1]: Leaving directory '/home/RavenWolf-/mm/tools' make venv make[1]: Entering directory '/home/RavenWolf-/mm' test -d .venv || python3 -m venv .venv || { rm -rf .venv; false; } .venv/Scripts/python3 -m pip install -U pip /bin/bash: line 1: .venv/Scripts/python3: No such file or directory make[1]: [Makefile:368: venv] Error 127 make[1]: Leaving directory '/home/RavenWolf_-/mm' make: [Makefile:392: init] Error 2
It looks like MSYS2 needs python-virtualenv
package.
Even when manually downloading python-virtualenv
(https://archlinux.org/packages/extra/any/python-virtualenv/download/), along with python-distlib python-filelock python-platformdirs
and installing using pacman -U python-virtualenv-20.26.2-1-any.pkg.tar.zst python-filelock-3.13.3-2-any.pkg.tar.zst python-platformdirs-4.2.0-3-any.pkg.tar.zst python-platformdirs-4.2.0-3-any.pkg.tar.zst
, I get the same error as above.
I made an issue about creating a python-virtualenv
package here.
Package name
mingw-w64-mips-linux-gnu-binutils
Brief description of package
A set of programs to assemble and manipulate binary and object files for the MIPS target.
Needed to build Zelda64Recomp (https://github.com/Zelda64Recomp/Zelda64Recomp/blob/dev/BUILDING.md) and Zelda64Decomp (https://github.com/zeldaret/mm)
URL for package's homepage
https://aur.archlinux.org/packages/mips-linux-gnu-binutils
Provide a basic test case to validate the package's functionality.
https://github.com/zeldaret/mm
MINGW environments where you need the package
Are you willing to submit a PR?
Yes