| Summary: | sys-apps/groff-1.18.1-r4 fails to build due to insisting on using colorgcc | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | giggles1 <bevdv> |
| Component: | [OLD] Core system | Assignee: | Gentoo's Team for Core System packages <base-system> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | a.grahn, esigra, pappy |
| Priority: | High | ||
| Version: | unspecified | ||
| Hardware: | x86 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Attachments: | config.log from groff build | ||
|
Description
giggles1
2004-01-06 12:38:26 UTC
It could be something hanging around in your environment. Does `env | grep cc` show you anything related to colorcc? No I already checked that: please python2.3 # env | grep cc MANPATH=/usr/share/man:/usr/local/share/man:/usr/share/gcc-data/i686-pc-linux-gnu/3.3/man:/opt/intel/compiler70/man:/usr/X11R6/man:/opt/blackdown-jdk-1.4.1/man:/usr/qt/3/doc/man PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/opt/bin:/usr/i686-pc-linux-gnu/gcc-bin/3.3:/opt/intel/compiler70/ia32/bin:/opt/Acrobat5:/usr/X11R6/bin:/opt/blackdown-jdk-1.4.1/bin:/opt/blackdown-jdk-1.4.1/jre/bin:/usr/qt/3/bin:/usr/kde/3.2/sbin:/usr/kde/3.2/bin:/usr/qt/2/bin INFOPATH=/usr/share/info:/usr/share/gcc-data/i686-pc-linux-gnu/3.3/info CC=gcc Maybe it didn't unmerge properly? how about trying "find / -name colorcc" as root and posting the output. Nothing except the old config dir under /etc: please python2.3 # find / -name colorgcc /etc/colorgcc /usr/portage/dev-util/colorgcc Seriously when this happened once before (http://bugs.gentoo.org/show_bug.cgi?id=30261) with another package, I found colorgcc hard coded in some python files that portage seemed to use. At the time, reinstalling python solved the problem, but here it has not.. gcc-config -l looks normal? I guess you're down to find / | xargs grep -l colorcc if all else fails. That'll take some time. That seems to choke in the /dev directory. I tried doing subdirs of root individually, but it also chokes (and locks up my keyboard) while doing /lib. Nothing showed up under /usr, /etc, or /var. Hmmm, ok. Can you attach the config.log from the attempt at compiling groff as a text/plain please? Created attachment 23275 [details]
config.log from groff build
I think this problem is after the groff build proper... some post inst thing. Going into the build dir and typing "make" by hand finishes just fine. Backing up from the error a bit further:
make[2]: Leaving directory `/usr/local/portage/portage/groff-1.18.1-r4/work/groff-1.18.1'
make[1]: Leaving directory `/usr/local/portage/portage/groff-1.18.1-r4/work/groff-1.18.1'
imake -DUseInstalled -I/usr/X11R6/lib/X11/config
In file included from /usr/X11R6/lib/X11/config/Imake.tmpl:104,
from Imakefile.c:36:
/usr/X11R6/lib/X11/config/linux.cf:323: warning: "BuildLibGlxWithoutPIC" redefined
In file included from /usr/X11R6/lib/X11/config/site.def:44,
from /usr/X11R6/lib/X11/config/Imake.tmpl:45,
from Imakefile.c:36:
/usr/X11R6/lib/X11/config/host.def:69: warning: this is the location of the previous definition
In file included from /usr/X11R6/lib/X11/config/X11.tmpl:1669,
from /usr/X11R6/lib/X11/config/Imake.tmpl:2012,
from Imakefile.c:36:
/usr/X11R6/lib/X11/config/lnxLib.tmpl:54: warning: "SharedGLReqs" redefined
/usr/X11R6/lib/X11/config/lnxLib.tmpl:26: warning: this is the location of the previous definition
gccmakedep -- -I./lib/Xt -I. -I/usr/X11R6/include -Dlinux -D__i386__ -D_POSIX_C_SOURCE=199309L -D_POSIX_SOURCE -D_XOPEN_SOURCE -D_BSD_SOURCE -D_SVID_SOURCE -DFUNCPROTO=15 -DNARROWPROTO -DFONTPATH=\"/usr/share/groff/`cat /usr/local/portage/portage/groff-1.18.1-r4/work/groff-1.18.1/VERSION``sed -e 's/^0$//' -e 's/^[1-9].*$/.&/' /usr/local/portage/portage/groff-1.18.1-r4/work/groff-1.18.1/REVISION`/font:/usr/share/groff/site-font:/usr/lib/font\" -- /usr/local/portage/portage/groff-1.18.1-r4/work/groff-1.18.1/src/xditview/xditview.c /usr/local/portage/portage/groff-1.18.1-r4/work/groff-1.18.1/src/xditview/Dvi.c /usr/local/portage/portage/groff-1.18.1-r4/work/groff-1.18.1/src/xditview/draw.c /usr/local/portage/portage/groff-1.18.1-r4/work/groff-1.18.1/src/xditview/font.c /usr/local/portage/portage/groff-1.18.1-r4/work/groff-1.18.1/src/xditview/lex.c /usr/local/portage/portage/groff-1.18.1-r4/work/groff-1.18.1/src/xditview/page.c /usr/local/portage/portage/groff-1.18.1-r4/work/groff-1.18.1/src/xditview/parse.c /usr/local/portage/portage/groff-1.18.1-r4/work/groff-1.18.1/src/xditview/XFontName.c /usr/local/portage/portage/groff-1.18.1-r4/work/groff-1.18.1/src/xditview/DviChar.c /usr/local/portage/portage/groff-1.18.1-r4/work/groff-1.18.1/src/xditview/device.c /usr/local/portage/portage/groff-1.18.1-r4/work/groff-1.18.1/src/xditview/xtotroff.c /usr/local/portage/portage/groff-1.18.1-r4/work/groff-1.18.1/src/xditview/XFontName.c /usr/local/portage/portage/groff-1.18.1-r4/work/groff-1.18.1/src/xditview/DviChar.c
colorgcc -O2 -fno-strength-reduce -fno-strict-aliasing -I./lib/Xt -I. -I/usr/X11R6/include -Dlinux -D__i386__ -D_POSIX_C_SOURCE=199309L -D_POSIX_SOURCE -D_XOPEN_SOURCE -D_BSD_SOURCE -D_SVID_SOURCE -DFUNCPROTO=15 -DNARROWPROTO -DFONTPATH=\"/usr/share/groff/`cat /usr/local/portage/portage/groff-1.18.1-r4/work/groff-1.18.1/VERSION``sed -e 's/^0$//' -e 's/^[1-9].*$/.&/' /usr/local/portage/portage/groff-1.18.1-r4/work/groff-1.18.1/REVISION`/font:/usr/share/groff/site-font:/usr/lib/font\" -c -o xditview.o xditview.c
/bin/sh: line 1: colorgcc: command not found
make: *** [xditview.o] Error 127
!!! ERROR: sys-apps/groff-1.18.1-r4 failed.
!!! Function src_compile, Line 93, Exitcode 2
!!! (no error message)
So, it seems to be doing something after groff is built? Given the ref to imake I assume its this part at the end of src_compile:
# Only build X stuff if we have X installed, but do
# not depend on it, else we get circular deps.
if [ -n "`use X`" ] && [ -x /usr/X11R6/bin/xmkmf ]
then
cd ${S}/src/xditview
xmkmf || die
make depend all || die
fi
I think your comment got overwritten, sorry. Yah, there it is, under src/xditview: please xditview # grep colorgcc * Makefile: CC = colorgcc Makefile: AS = colorgcc -c -x assembler Makefile: PREPROCESSCMD = colorgcc -E $(STD_CPP_DEFINES) Makefile: LD = colorgcc -nostdlib Makefile: MODCC = colorgcc Makefile: MODAS = colorgcc -c -x assembler Makefile: MODLD = colorgcc -nostdlib Makefile.bak: CC = colorgcc Makefile.bak: AS = colorgcc -c -x assembler Makefile.bak: PREPROCESSCMD = colorgcc -E $(STD_CPP_DEFINES) Makefile.bak: LD = colorgcc -nostdlib Makefile.bak: MODCC = colorgcc Makefile.bak: MODAS = colorgcc -c -x assembler Makefile.bak: MODLD = colorgcc -nostdlib I assume I can just USE="-X" and have this thing build, but it would be nice to know how it is getting there in the first place. hi, can you do the following commands please and get me the output:
grep -r "CC" /etc
grep -ri "colorgcc" /etc
find /usr/bin -name "*gcc*" -exec ls -ali {} \; 2>&1 | grep colorgcc
and watch out for broken links to colorgcc
the building might be inheriting the colorgcc from a left-over definition in the environment when colorgcc was emerged and installed itself to be the active gcc.
so this should be a colorgcc issue mainly.
but i can tell you more if you can paste me the output of the commands and find something
thank you very much :-)
This has long since fixed itself. After upgrading to portage-2.0.51-r2, emerge groff requires gcc-4.0. No problems after downgrading to portage-2.0.50. Re-updating portage lets the error occur again. This DEPEND problem makes world updates impossible since last portage update! root@localhost:/etc # emerge -p -d groff These are the packages that I would merge, in order: Calculating dependencies Parent: None Depstring: sys-apps/groff Candidates: ['sys-apps/groff'] ebuild: sys-apps/groff-1.18.1-r4 binpkg: None - Parent: ebuild / sys-apps/groff-1.18.1-r4 merge Depstring: virtual/libc >=sys-apps/texinfo-4.0 !bootstrap? ( sys-devel/patch ) !bootstrap? ( sys-devel/patch ) !bootstrap? ( sys-devel/patch ) virtual/libc >=sys-apps/texinfo-4.0 Candidates: ['>=sys-devel/gcc-4.0'] emerge: there are no ebuilds to satisfy ">=sys-devel/gcc-4.0". -- Alex that is a completely unrelated bug, don't post it here search bugzilla for it, it's been reported long ago short answer, edit the files in /var/db/pkg/sys-devel/gcc-2*/ |
