Hi, Efraim Flashner <efr...@flashner.co.il> skribis:
> On Thu, Apr 07, 2016 at 04:07:25PM +0300, Manolis Ragkousis wrote: >> Hey Ludo, >> >> I have reproduced the problem on the latest master targeting i686-linux >> and arm-linux-gnueabihf. >> >> The problem is that those libraries will fail to build when glibc is not >> present. Also if target os is none, this problem will not appear because >> the libs will not get built at all. >> >> You can reproduce it with ./pre-inst-env guix build -e '((@@(gnu >> packages cross-base) cross-gcc) "arm-linux-gnueabihf")' >> >> This does not happen when targeting mips. >> >> I have added an explanation to the patch and a link to this thread. >> >> Manolis > > This patch was instrumental in building aarch64 bootstrap tarballs. > Without it, when building the cross-gcc compiler from x86_64 to aarch64 > it would fail to compile when trying to build libitm. Searching around > the internet suggested that this was only when building a cross-compiler > that targeted C++ and not only C. > > I understand that it's too late to push this to core-updates, but we > should push it to core-updates-next. Sorry for the delay again. Since it touches the cross toolchain and not the main toolchain (Manolis, could you double-check that this is correct, by making sure that “./pre-inst-env guix build coreutils -d” is the same both before and after the patch?), it’s still OK to push to ‘core-updates’. Manolis: OK to push? Thanks for the heads-up, Efraim! Ludo’.
