Summary: | emerging gcc-3.2.2 fails during configure | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Veiko Kukk <veiko> |
Component: | New packages | Assignee: | Martin Schlemmer (RETIRED) <azarah> |
Status: | RESOLVED DUPLICATE | ||
Severity: | critical | ||
Priority: | High | ||
Version: | unspecified | ||
Hardware: | x86 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: | # set &> env.txt |
Description
Veiko Kukk
2003-03-09 12:26:21 UTC
# set &> env.txt and attach please. Created attachment 9196 [details]
# set &> env.txt
Try maybe: # unset LANG LC_ALL # emerge gcc long shot, but it have caused issues in the past. it didnt help. I also tried export LANG=C and export LC_ALL=C but same error occured. Ok. Please attach the config.log in: /var/tmp/portage/gcc-3.2.2/work/build /var/tmp/portage/gcc-3.2.2/work/build/libiberty Maybe we can figure out why its happening. there is no config.log in those directories. the only file which contains "configure" in its name is configure.status in /var/tmp/portage/gcc-3.2.2/work/build Libiberty should have one: ------------------ nosferatu root # ls /var/tmp/portage/gcc-3.2.2/work/build/libiberty/config.log /var/tmp/portage/gcc-3.2.2/work/build/libiberty/config.log nosferatu root # variable libiberty # pwd /var/tmp/portage/gcc-3.2.2/work/build/libiberty variable libiberty # ls variable libiberty # as you can see it's empty I found that the problem is in sed-4.0.5. I emerged supersed, unmerged sed-4.0.5 and made symlink ln -s /bin/ssed /usr/bin/sed . Then everything I have reported as failing to build builds normally! Why sed-4.0.5 is marked stable? As it makes so many problems! It could be one of your CFLAGS. Mind trying to recompile sed, each time dropping one of your CFLAGS, and see which one ? We can then filter that one in sed's ebuild .... started compiling sed with only '-march=i686', but it still fails, so I assume that it's completely useless to try other CFLAGS. could anybody explain me, why supersed works for me and sed causes so many problems? *** This bug has been marked as a duplicate of 17051 *** |