emerge system/gettext error

[lukaz]

hi there

I try to install gentoo (stage1) now the second time this week. the 1st time i missed some use-flags and also did not set the compiler-options well. therfor I am on the second go. but i ran both times in dificultnes with gettext. fist time i've gogled and found a solucion but cannot find anything helpfull this time and i also cannot remember how i've fixed it last time - it was late at night the error msg I came across by "emerge system" look like this (typed it from screen):

error: C++ preprocessor "/lib/cpp" fails sanity check
see 'config.log' for more details
configure: error: /bin/sh './configure' failed for autoconf-lib-link
ERROR: sys-devel/gettext-0.12.1 failed
Function econf, line 365, Exitcode 1
econf failed

the problem looks like this one here:
http://forums.gentoo.org/viewtopic.php?t=187866
or here:
http://article.gmane.org/gmane.linux.gentoo.user/82292
or here:
http://www.okoun.cz/boards/gentoo
or similar here:
http://forums.gentoo.org/viewtopic.php?t=188235
or similar here:
http://forums.gentoo.org/viewtopic.php?t=155307



i could not find the file: config.log and if i try to "emerge gettext" it will also fail with the same msg. also the setting accept_keywords="~x86"/accept_keywords="x86" this or that way did not help.

thx for any help.lukaz.

[moocha]

It's a long shot, but is the file system that contains /var/tmp mounted with the noexec option by any chance?

[lukaz]

ther are just the root and the boot fs and both are mounted like:

mount /dev/hdax /mnt/blabla and after some otha cmds chroot..... /bin/bash

so, i dont think so. but if I change the "accept_keywords" value do i have to make a export that it takes a effect?

lukaz

[DaveAtFraud]

Not sure where the thread http://forums.gentoo.org/viewtopic.php?t=155307 started but this is identical to the problem I have been posting about in 155307. I can pretty much rule out any issues with odd mount options and such since "everything" involved seems to work fine from the command line; emerge just continues to hurl when it gets to the /lib/cpp sanity checks. Everything is in quotes since that means everything that I could find that seems to be involved. Obviously, I'm missing something.

[DaveAtFraud]

I may have finally found the right Google question to as: "sanity /lib/cpp". One of the links was to a LFS posting regarding the same error. It can be caused by cpp not being able to find the kernel headers. I won't have a chance to try anything with this for another three or four hours (work sure has a way of intruding on fun). Traditionally, the kernel source is in /usr/src or there will be links there but I'm not sure what Gentoo does at this stage of an install.

[moocha]

Do not, ever link /usr/include/linux into the kernel source tree. emerge sys-kernel/linux-headers instead. Search the forum for glibc horror stories if you're curious as to why .

[DaveAtFraud]

Do not, ever link /usr/include/linux into the kernel source tree. emerge sys-kernel/linux-headers instead. Search the forum for glibc horror stories if you're curious as to why .

I'll buy that. Thanks for answering my remaining question which was how to get the kernel headers onto the box Gentooishly.

I do want to poke around on the box before doing the suggested emerge. It should be interesting to find out if the headers are there but for some reason cpp isn't finding them or if they aren't there at all. Same question for the stage1 tar ball.

Follow-up: The headers are there and, I guess, where they're supposed to be. Apparently, following the documentation puts them in /usr/include/linux. The next question is, why isn't configure finding them?

Second follow-up: OK. This is really weird. After deciding that the kernel headers were already on the system and where they were supposed to be I was left with the possibility that they weren't being found. I noticed that what both bootstrap.sh and emerge system spit back at me as to the configure options ended with "-srcdir=" so I tried to set that using CFLAGS. That didn't work but I also got a diagnostic that the configure step for bootstrap.sh didn't like the "-mcpu=i686" flag. I changed this to "-march=i686" and now bootstrap.sh is happily grinding away (previously it "finished" in less than a minute).

I'll re-dump the stage 1 tar ball when I get a chance but I'm pretty sure the "-mcpu=i686" was a default value in make.conf. Its either that or it was something obviously wrong and I blindly changed it to i686 thinking it was the -march option. Doh!

[lukaz]

oh, silly mistake

i've bootstraped the short way with -f (fetch only) but never compiled.

but it seams i'm not the only one

good luck the ones with the real probs.lukaz.

[tomk]

Moved to Duplicate Threads, please see this FAQ:

http://forums.gentoo.org/viewtopic.php?t=294108