lilypond-devel
[Top][All Lists]
Advanced

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

Re: GUB problem


From: David Kastrup
Subject: Re: GUB problem
Date: Sun, 14 Aug 2016 14:03:23 +0200
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/25.1.50 (gnu/linux)

"Phil Holmes" <address@hidden> writes:

> ----- Original Message ----- 
> From: "David Kastrup" <address@hidden>
> To: "Phil Holmes" <address@hidden>
> Cc: "Masamichi HOSODA" <address@hidden>; "Devel"
> <address@hidden>
> Sent: Sunday, August 14, 2016 12:04 PM
> Subject: Re: GUB problem
>
>
>> "Phil Holmes" <address@hidden> writes:
>>
>>> My GUB build failed again yesterday.  The log output is:
>>>
>>> checking for a BSD-compatible install... /usr/bin/install -c
>>> checking whether build environment is sane... yes
>>> checking for x86_64-freebsd6-strip... x86_64-freebsd6-strip
>>> checking for a thread-safe mkdir -p... /bin/mkdir -p
>>> checking for gawk... gawk
>>> checking whether make sets $(MAKE)... yes
>>> checking whether make supports nested variables... yes
>>> checking whether make supports nested variables... (cached) yes
>>> checking for x86_64-freebsd6-gcc... x86_64-freebsd6-gcc
>>> checking whether the C compiler works... no
>>> configure: error: in
>>> `/home/gub/NewGub/gub/target/freebsd-64/build/fontconfig-2.12.1':
>>> configure: error: C compiler cannot create executables
>>>
>>> Can anyone suggest what the error might be?
>>
>> config.log should be more informative here.
>
>
> It didn't seem to be to me, but it's attached.

configure:3706: checking whether the C compiler works
configure:3728: x86_64-freebsd6-gcc     conftest.c  >&5
x86_64-freebsd6-gcc: internal compiler error: Illegal instruction (program cc1)
librestrict:error:/home/gub/NewGub/gub/target/freebsd-64/root/usr/cross/bin/x86_64-freebsd6-gcc:
 tried to open () file 
/home/gub/NewGub/gub/target/tools/root/usr/lib/librestrict.so
librestrict:allowed:
  /home/gub/NewGub/gub/target/freebsd-64
  /tmp
  /dev/null
  /dev/urandom
  /proc/self

I suspect that Hosoda-san knows better than I how to address this: as
far as I understand the librestrict library tries making sure that the
cross-building environment does not access anything it shouldn't (which
is particularly important when the architecture of host and target
differ).

-- 
David Kastrup



reply via email to

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