It might be a bit dated, but we'll see what happens. Doing the first run of gcc now.
]]>A Sparc64 chroot isn't possible. The closest thing would be to run a chroot-like environment in QEMU.
A cross toolchain should be preferred, although I have no idea on how to set it up.
Yeah. I'm building a toolchain atm. As long as the PKGBUILDs know that I'm cross compiling, I should be okay. There will be a bit of hand-cranking needed since not all sources use autotools. Not really looking forward to cross-compiling openssl, and the kernel will take a bit of screwing around to work right, but, meh, that's part of the fun, right? There's only 100-ish packages for a base install, so just getting to a functional system won't be too bad.
I'm going to experiment with an auto-build system when I have the system running. I'm very comfortable with bash scripting and am learning c++, so I have some good ideas. I work as a sysadmin too, so I could even give some of the meatier servers at work an extra job to do. That is, if all goes well
]]>Either way, if you want to use makepkg, that means you'll pretty much need to have an Arch sparc64 setup (at least, if you want dependency resolving etc.). A toolchain isn't enough, you need dependencies as well.
]]>Is this possible? If not, what kind of work/patching would be necessary to make it happen?
]]>