On Mon, Dec 22, 2008 at 01:30, Jeff Cranmer <jcranme...@earthlink.net> wrote:
> On Sunday 21 December 2008 11:52:11 am Jeff Cranmer wrote:
>> On Sunday 21 December 2008 11:11:59 am Justin wrote:
>> > Jeff Cranmer schrieb:
>> > > I have a problem with my gentoo system
>> > >
>> > > I am trying to update, and I get a C preprocessor "/lib/cpp" fails
>> > > sanity check error on a number of packages.
>> > >
>> > > After a bit of searching, the solution that I come across most often is
>> > > to recompile glibc and gcc. Unfortunately, when I try to compile
>> > > glibc, I get the same sanity check error. Catch 22.
>> > >
>> > > Can anyone help me get around this 'insanity'?
>> > >
>> > > Thanks
>> > >
>> > > Jeff
>> >
>> > Can you provide some more information please? Logs etc?
>>
>> Here is the end of the output.
>>
>> checking whether we are using the GNU C compiler... yes
>> checking whether x86_64-pc-linux-gnu-gcc accepts -g... yes
>> checking for x86_64-pc-linux-gnu-gcc option to accept ISO C89...
>> unsupported checking how to run the C preprocessor... /lib/cpp
>> configure: error: C preprocessor "/lib/cpp" fails sanity check
>> See `config.log' for more details.
>> *
>> * ERROR: sys-libs/glibc-2.9_p20081201 failed.
>> * Call stack:
>> * ebuild.sh, line 49: Called src_compile
>> * environment, line 3457: Called eblit-run 'src_compile'
>> * environment, line 1115: Called eblit-glibc-src_compile
>> * src_compile.eblit, line 179: Called src_compile
>> * environment, line 3457: Called eblit-run 'src_compile'
>> * environment, line 1115: Called eblit-glibc-src_compile
>> * src_compile.eblit, line 187: Called toolchain-glibc_src_compile
>> * src_compile.eblit, line 120: Called
>> glibc_do_configure 'src_compile'
>> * src_compile.eblit, line 97: Called die
>> * The specific snippet of code:
>> * "${S}"/configure ${myconf} || die "failed to configure glibc"
>> * The die message:
>> * failed to configure glibc
>> *
>> * If you need support, post the topmost build error, and the call stack if
>> relevant.
>> * A complete build log is located
>> at '/var/tmp/portage/sys-libs/glibc-2.9_p20081201/temp/build.log'.
>> * The ebuild environment file is located
>> at '/var/tmp/portage/sys-libs/glibc-2.9_p20081201/temp/environment'.
>> *
>>
>> * Messages for package sys-libs/glibc-2.9_p20081201:
>>
>> *
>> * ERROR: sys-libs/glibc-2.9_p20081201 failed.
>> * Call stack:
>> * ebuild.sh, line 49: Called src_compile
>> * environment, line 3457: Called eblit-run 'src_compile'
>> * environment, line 1115: Called eblit-glibc-src_compile
>> * src_compile.eblit, line 179: Called src_compile
>> * environment, line 3457: Called eblit-run 'src_compile'
>> * environment, line 1115: Called eblit-glibc-src_compile
>> * src_compile.eblit, line 187: Called toolchain-glibc_src_compile
>> * src_compile.eblit, line 120: Called
>> glibc_do_configure 'src_compile'
>> * src_compile.eblit, line 97: Called die
>> * The specific snippet of code:
>> * "${S}"/configure ${myconf} || die "failed to configure glibc"
>> * The die message:
>> * failed to configure glibc
>> *
>> * If you need support, post the topmost build error, and the call stack if
>> relevant.
>> * A complete build log is located
>> at '/var/tmp/portage/sys-libs/glibc-2.9_p20081201/temp/build.log'.
>> * The ebuild environment file is located
>> at '/var/tmp/portage/sys-libs/glibc-2.9_p20081201/temp/environment'.
>>
>> I've attached the build.log, but can't find config.log. Where is this
>> normally located?
>>
>> Jeff
>
> After finding this link with a possible solution,
> http://www.linux-solved.com/post/gnu-stubs-32-h-No-such-file-or-directory-multilib-SOLVED-564.html
>
> I downloaded binaries of glibc and gcc
>
> I emerged gcc from a binary successfully, but when I tried to install the
> glibc binary, it failed because the binary I found was rev 2.6.1, and the
> present version is glibc-2.9_p20081201, so emerge would not allow the
> downgrade.
>
> The error was
> * Sanity check to keep you from breaking your system:
> * Downgrading glibc is not supported and a sure way to destruction
> *
> * ERROR: sys-libs/glibc-2.6.1 failed.
> * Call stack:
> * ebuild.sh, line 49: Called pkg_setup
> * environment, line 3275: Called die
> * The specific snippet of code:
> * die "aborting to save your system";
> * The die message:
> * aborting to save your system
> *
> * If you need support, post the topmost build error, and the call stack if
> relevant.
> * A complete build log is located
> at '/var/tmp/portage/sys-libs/glibc-2.6.1/temp/build.log'.
> * The ebuild environment file is located
> at '/var/tmp/portage/sys-libs/glibc-2.6.1/temp/environment'.
>
> I then tried emerge binutils glibc gcc after running source /etc/profile and
> env-update.
>
> binutils emerged successfully, but glibc still failed with the same sanity
> check error.
>
> Does anyone know where I can get the latest binary for an amd64 system, or
> otherwise get around this issue?
Hmm, if you have a separate machine with the same architecture, you
can build those binary packages yourself, just man emerge and take a
look at the buildpkg section. Alternatively, you can cross compile
binary packages[1].
Or, why not just use a stage tarball?
HTH.
Joe
[1] http://www.gentoo.org/proj/en/base/embedded/cross-development.xml
