Ludovic Courtès writes:
> Hi Marius,
>
> Marius Bakke skribis:
>
>> Ludovic Courtès writes:
>
> [...]
>
>>> 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’ (?).
Hi Marius,
Marius Bakke skribis:
> Ludovic Courtès writes:
[...]
>> 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?
>
> Unfo
Ludovic Courtès writes:
> Hi Danny,
>
> Danny Milosavljevic 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,
Hi Danny,
Danny Milosavljevic 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
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"))
Hi Tobias,
On Tue, 28 May 2019 18:07:02 +0200
Tobias Platen wrote:
> Im trying to cross compile basic GNU software such as bash and coreutils
> for powerpc.
>
> When building mpfr the build fails using the message above. I guess I
> have to specify the include paths for glibc to the configure s
Hello,
Im trying to cross compile basic GNU software such as bash and coreutils
for powerpc.
When building mpfr the build fails using the message above. I guess I
have to specify the include paths for glibc to the configure script,
since headers won't be found in /usr/include
Tobias
configure:
