Richard Henderson <richard.hender...@linaro.org> writes: > On 04/19/2018 03:58 AM, Alex Bennée wrote: >> What would be really >> helpful is if the respective maintainers could encode their EXACT >> STEPS for building their cross compilers into some docker recipes. > > I've just re-built my alphaev67 cross-environment and recorded everything. > > Since the script begins with rebuilding glibc, it assumes you *already* have a > cross-compiler. If you don't have that, then you start in the middle of the > script with the GCC build. But in that case you must have the sysroot.tar.gz > that the first half just created.
Could you send me the sysroot.tar.gz? > > Starting without that seed tarball is hard, as previously mentioned. For > better supported platforms than alpha you can typically pull the same files > from e.g. debian packages or a gentoo stage3 tarball. Hmm I was hoping I could use --without-sysroot to build a gcc just for building glibc and then re-build gcc once glibc was boot-strapped. But that doesn't seem to work... Maybe for alpha we just have to accept there is a blob of sysroot to get the build going? Of course we should probably host that blob on qemu's servers somewhere... > While I've used git gcc/binutils/glibc, because I had them handy, of course > everything would work equally well using release tarballs for each project. > > Let me know if you have any questions re cross-tools. > > > r~ -- Alex Bennée
