I have two boxes, one has gcc 3.1.1, other gcc 3.2. The kaffe in portage and in CVS fails to compile on both. build log in URL.
This is suspicious: gcc -DHAVE_CONFIG_H -I. -I. -I../../config -I../../include -I../kaffevm -I./../kaffevm -DKAFFEH -DKVER='"1.0.7-rc1"' -I/var/tmp/portage/kaffe-1.0.7_rc1-r1/work/kaffe-1.0.7-rc1/./kaffe/kaffevm -I/var/tmp/portage/kaffe-1.0.7_rc1-r1/work/kaffe-1.0.7-rc1/./kaffe/kaffevm/systems/unix-jthreads -I../../config -I../../include -I/usr/local/include -march=i686 -O3 -pipe -Wall -Wstrict-prototypes -c inflate.c cc1: warning: changing search order for system directory "/usr/local/include" cc1: warning: as it has already been specified as a non-system directory Why does it include /usr/local/include ? Have you installed your compiler in /usr/local/include ? Do you use our gcc-3.2, or one of your own design ? If the latter, please test with our gcc-3.2
I've had a few of the other developers try to reproduce this one, and nobody seem to be able to. It would appear that your glibc-installation may be defective. Either your glibc header files in /usr/include are bogus, or you have some C-like header files in /usr/local/include that are included for some reason. You could try using qpkg -mc glibc-<yourinstalledversion> to see if all the installed files have correct mtimes and md5sums. If not, I'd advise you to reinstall glibc. If that doesn't help, try figuring out which files are included by using gcc's -E option: gcc -DHAVE_CONFIG_H -I. -I. -I../../config -I../../include -I../kaffevm -I./../kaffevm -DKAFFEH -DKVER='"1.0.7-rc1"' -I/var/tmp/portage/kaffe-1.0.7_rc1-r1/work/kaffe-1.0.7-rc1/./kaffe/kaffevm -I/var/tmp/portage/kaffe-1.0.7_rc1-r1/work/kaffe-1.0.7-rc1/./kaffe/kaffevm/systems/unix-jthreads -I../../config -I../../include -I/usr/local/include -march=i686 -O3 -pipe -Wall -Wstrict-prototypes -E jar.c from the directory /var/tmp/portage/kaffe-1.0.7_rc1-r1/work/kaffe-1.0.7-rc1/kaffe/kaffeh As nobody else seem to be able to reproduce this bug, I'm closing it for now. If you figure out what causes it, please don't hesitate to reopen this bug.
Ah, I solved it (kinda). If there is /usr/local/include/, even without any files in it, kaffe ebuild fails. Also see this thread from kaffe@kaffe.org: http://www.kaffe.org/pipermail/kaffe/2002-August/008827.html
karl, i'll reopen this. and apply mandrake's confugure.in patch for /usr/local/include. there's also a new version of kaffe i'll update. matt
okay i've underestimated this one.. might take me a while. :)
I'll punt this to you Matt. If I get the time this weekend, I'll fix it myself, but don't count on it.
This workaround seems to work for me: mv /usr/local/include /usr/local/include- emerge kaffe mv /usr/local/include- /usr/local/include
I don't think that is a workarond we're ready to go for in the ebuild:)
kaffe-1.1.0 is now available for testing; I've not particularily tested that the /usr/local/include problem is fixed, but from cursory inspection it appears to be. Please give it a whirl (remember USE="~x86"), and reopen this bug if the problem persists.