[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Crosscompiling C++ for powerpc64le fails

From: Ludovic Courtès
Subject: Re: Crosscompiling C++ for powerpc64le fails
Date: Fri, 31 May 2019 23:54:32 +0200
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/26.2 (gnu/linux)

Hi Danny,

Danny Milosavljevic <address@hidden> skribis:

> I've investigated a bit more:
> Guix's gcc-4.7 passes
>   (string-append "--with-native-system-header-dir=" libc "/include")
>   where libc is (assoc-ref %build-inputs "libc")
> .
> However, further down, there is
>                 `(let* ((libc        (assoc-ref %build-inputs "libc"))
>                        (libc-native (or (assoc-ref %build-inputs 
> "libc-native")
>                                         libc)))
> which makes me think that "--with-native-system-header-dir=" should use
> libc-native if the latter is present.
> It would be possible to pass "--with-headers=" to gcc which would make it copy
> the specified directory into the gcc installation directory and everything
> would work without weird workarounds.

You’re probably right, it would be worth giving it a try.

The weird thing is that:

  guix build mpfr --target=arm-linux-gnueabihf

works fine on current master, which uses GCC 5.5 for cross-compilation.

The issue that Tobias reports reminds me of the CPATH vs. C_INCLUDE_PATH
issue that was causing troubles with newer GCCs, and that I think Marius
addressed in ‘core-updates’ (?).  Marius, does that ring a bell?


reply via email to

[Prev in Thread] Current Thread [Next in Thread]