[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: GUB problem
From: |
Phil Holmes |
Subject: |
Re: GUB problem |
Date: |
Mon, 15 Aug 2016 14:18:29 +0100 |
----- Original Message -----
From: "Masamichi Hosoda" <address@hidden>
To: <address@hidden>; <address@hidden>
Cc: <address@hidden>
Sent: Monday, August 15, 2016 1:57 PM
Subject: Re: GUB problem
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
In my environment (Ubuntu 14.04 LTS 64 bit), the error does not occur.
Would you tell me the environment which the error occurs?
Ubuntu 14.04 LTS 32 bit.
FYI I had to make a small change to the GMP spec to accommodate 32 bit - my
patch shows what I had to do.
Anyway, this error means that
cross-compiler gcc (for freebsd-64) tries to open "librestrict.so".
"librestrict.so" is for host OS (perhaps Linux)
instead of for target OS (freebsd-64).
If I understand correctly,
cross-compiler gcc does not need to open "librestrict.so".
I don't know why cross-compiler gcc tries to open "librestrict.so".
Moreover, at least a few weeks ago, the error did not occur.
My recent pull request does not change gcc.
I wonder why cross-compiler gcc began to open "librestrict.so".
Perhaps your fix to librestrict made something work that was not previously,
and so an error is now detected?
--
Phil Holmes
0001-Fix-GMP-for-32-bit.patch
Description: Binary data
- GUB problem, Phil Holmes, 2016/08/14
- Re: GUB problem, David Kastrup, 2016/08/14
- Re: GUB problem, Phil Holmes, 2016/08/14
- Re: GUB problem, David Kastrup, 2016/08/14
- Re: GUB problem, Masamichi Hosoda, 2016/08/15
- Re: GUB problem,
Phil Holmes <=
- Re: GUB problem, Masamichi Hosoda, 2016/08/15
- Re: GUB problem, Phil Holmes, 2016/08/15
- Re: GUB problem, Masamichi Hosoda, 2016/08/16
- Re: GUB problem, Phil Holmes, 2016/08/24
- Re: GUB problem, Masamichi Hosoda, 2016/08/24
- Re: GUB problem, Phil Holmes, 2016/08/24
- Re: GUB problem, Masamichi Hosoda, 2016/08/26
- Re: GUB problem, Phil Holmes, 2016/08/26
- Re: GUB problem, Masamichi Hosoda, 2016/08/26
- Re: GUB problem, Phil Holmes, 2016/08/28