[Lunar-bugs] [Lunar Linux 0000209]: gcc-4.1.2 compiled with java language
Lunar bug reports list
lunar-bugs at lunar-linux.org
Thu Feb 28 08:07:31 CET 2008
The following issue has been CLOSED
======================================================================
http://bugs.lunar-linux.org/view.php?id=209
======================================================================
Reported By: Stumbles
Assigned To: sofar
======================================================================
Project: Lunar Linux
Issue ID: 209
Category: lunar
Reproducibility: always
Severity: major
Priority: high
Status: closed
Moonbase Version: 20070317
Core Tools: Theedge
Core Tools Version: 20070317
Resolution: fixed
Fixed in Version:
======================================================================
Date Submitted: 03-18-2007 02:23 CET
Last Modified: 02-28-2008 08:07 CET
======================================================================
Summary: gcc-4.1.2 compiled with java language
Description:
upgrading to gcc-4.1.2 and the build goes fine until just after calling
"lrm --upgrade gcc" and removing the gcc module when the BUILD fails. Yes
I did select java for one of the languages. At first glance it seems to be
a problem with ccache, the important bit that fails;
Removed module: gcc
make[1]: Entering directory `/usr/src/gcc-4.1.2/BUILD'
/bin/sh ../mkinstalldirs /usr /usr
make[2]: Entering directory `/usr/src/gcc-4.1.2/BUILD/fastjar'
if gcc -DHAVE_CONFIG_H -I. -I../../fastjar -I. -I. -I../../fastjar
-I../../fastjar/../include -DWITH_SHIFT_DOWN -W -Wall -pedantic
-Wstrict-prototypes -Wmissing-prototypes -Wwrite-strings -O2
-march=athlon64 -pipe -O2 -march=athlon64 -pipe -MT fastjar-jartool.o -MD
-MP -MF ".deps/fastjar-jartool.Tpo" -c -o fastjar-jartool.o `test -f
'jartool.c' || echo '../../fastjar/'`jartool.c; \
then mv -f ".deps/fastjar-jartool.Tpo" ".deps/fastjar-jartool.Po";
else rm -f ".deps/fastjar-jartool.Tpo"; exit 1; fi
ccache: invalid option -- D
ccache, a compiler cache. Version 2.4
Copyright Andrew Tridgell, 2002
Usage:
ccache [options]
ccache compiler [compile options]
compiler [compile options] (via symbolic link)
Options:
-s show statistics summary
-z zero statistics
-c run a cache cleanup
-C clear the cache completely
-F <maxfiles> set maximum files in cache
-M <maxsize> set maximum size of cache (use G, M or K)
-h this help page
-V print version number
make[2]: *** [fastjar-jartool.o] Error 1
make[2]: Leaving directory `/usr/src/gcc-4.1.2/BUILD/fastjar'
make[1]: *** [install-fastjar] Error 2
make[1]: Leaving directory `/usr/src/gcc-4.1.2/BUILD'
make: *** [install] Error 2
======================================================================
----------------------------------------------------------------------
Stumbles - 03-18-07 03:23
----------------------------------------------------------------------
After restoring gcc3, gave this another whirl. This time just fortran and
objc were chosen and ccache still used and the install was successful.
So now where is the gcc4/jaav pulling the "D" ccache option from?
----------------------------------------------------------------------
Stumbles - 03-18-07 14:28
----------------------------------------------------------------------
Well, reran the lin, this time with all languages selected and ccache
disabled. It still borks but you will find this interesting;
Removed module: gcc
make[1]: Entering directory `/usr/src/gcc-4.1.2/BUILD'
/bin/sh ../mkinstalldirs /usr /usr
make[2]: Entering directory `/usr/src/gcc-4.1.2/BUILD/fastjar'
if gcc -DHAVE_CONFIG_H -I. -I../../fastjar -I. -I. -I../../fastjar
-I../../fastjar/../include -DWITH_SHIFT_DOWN -W -Wall -pedantic
-Wstrict-prototypes -Wmissing-prototypes -Wwrite-strings -O2
-march=athlon64 -pipe -O2 -march=athlon64 -pipe -MT fastjar-jartool.o -MD
-MP -MF ".deps/fastjar-jartool.Tpo" -c -o fastjar-jartool.o `test -f
'jartool.c' || echo '../../fastjar/'`jartool.c; \
then mv -f ".deps/fastjar-jartool.Tpo" ".deps/fastjar-jartool.Po";
else rm -f ".deps/fastjar-jartool.Tpo"; exit 1; fi
/var/lib/lunar/compilers/gcc: line 9: exec: -D: invalid option
exec: usage: exec [-cl] [-a name] file [redirection ...]
make[2]: *** [fastjar-jartool.o] Error 1
make[2]: Leaving directory `/usr/src/gcc-4.1.2/BUILD/fastjar'
make[1]: *** [install-fastjar] Error 2
make[1]: Leaving directory `/usr/src/gcc-4.1.2/BUILD'
make: *** [install] Error 2
Creating /var/log/lunar/compile/gcc-4.1.2.bz2
----------------------------------------------------------------------
Stumbles - 03-18-07 16:44
----------------------------------------------------------------------
After some more testing. Having j2sdk or sun-jre and selecting gcc4 java
language will cause the gcc4 install to error out with the same errors as
originally noted.
----------------------------------------------------------------------
sofar - 03-18-07 19:55
----------------------------------------------------------------------
try setting WRAPPER usage to off in the compiler optimizations
----------------------------------------------------------------------
Stumbles - 03-18-07 20:57
----------------------------------------------------------------------
Disabling GCC_WRAPPERS had no effect.
Removed module: gcc
make[1]: Entering directory `/usr/src/gcc-4.1.2/BUILD'
/bin/sh ../mkinstalldirs /usr /usr
make[2]: Entering directory `/usr/src/gcc-4.1.2/BUILD/fastjar'
if gcc -DHAVE_CONFIG_H -I. -I../../fastjar -I. -I. -I../../fastjar
-I../../fastjar/../include -DWITH_SHIFT_DOWN -W -Wall -pedantic
-Wstrict-prototypes -Wmissing-prototypes -Wwrite-strings -O2
-march=athlon64 -pipe -O2 -march=athlon64 -pipe -MT fastjar-jartool.o -MD
-MP -MF ".deps/fastjar-jartool.Tpo" -c -o fastjar-jartool.o `test -f
'jartool.c' || echo '../../fastjar/'`jartool.c; \
then mv -f ".deps/fastjar-jartool.Tpo" ".deps/fastjar-jartool.Po";
else rm -f ".deps/fastjar-jartool.Tpo"; exit 1; fi
/bin/sh: gcc: command not found
make[2]: *** [fastjar-jartool.o] Error 1
make[2]: Leaving directory `/usr/src/gcc-4.1.2/BUILD/fastjar'
make[1]: *** [install-fastjar] Error 2
make[1]: Leaving directory `/usr/src/gcc-4.1.2/BUILD'
make: *** [install] Error 2
----------------------------------------------------------------------
sofar - 03-21-07 16:56
----------------------------------------------------------------------
Samuel, please take a look at this.
----------------------------------------------------------------------
El_Angelo - 05-22-07 11:26
----------------------------------------------------------------------
i don't use the java compiler... don't see how i could even fix this...
----------------------------------------------------------------------
dveatch - 11-26-07 14:56
----------------------------------------------------------------------
It seems gcc-4.2.2 or something in our tools has fixed this issue so when
we bump gcc this BR can be closed.
----------------------------------------------------------------------
Moe - 11-26-07 15:34
----------------------------------------------------------------------
GCC has been bumped to 4.2.2 .. and as Dennis noted, the bug is fixed.
Issue History
Date Modified Username Field Change
======================================================================
03-18-07 02:23 Stumbles New Issue
03-18-07 02:23 Stumbles Status new => assigned
03-18-07 02:23 Stumbles Assigned To => sofar
03-18-07 02:23 Stumbles File Added: gcc-4.1.2.bz2
03-18-07 02:23 Stumbles Moonbase Version => 20070317
03-18-07 02:23 Stumbles Core Tools => Theedge
03-18-07 02:23 Stumbles Core Tools Version => 20070317
03-18-07 03:23 Stumbles Note Added: 0000430
03-18-07 14:28 Stumbles Note Added: 0000435
03-18-07 16:44 Stumbles Note Added: 0000436
03-18-07 19:55 sofar Note Added: 0000438
03-18-07 20:57 Stumbles Note Added: 0000439
03-21-07 16:55 sofar Assigned To sofar => El_Angelo
03-21-07 16:56 sofar Note Added: 0000449
05-22-07 11:25 El_Angelo Assigned To El_Angelo => sofar
05-22-07 11:26 El_Angelo Note Added: 0000531
11-26-07 14:56 dveatch Note Added: 0000710
11-26-07 15:34 Moe Status assigned => resolved
11-26-07 15:34 Moe Resolution open => fixed
11-26-07 15:34 Moe Note Added: 0000711
02-28-08 08:07 ratler Status resolved => closed
======================================================================
More information about the Lunar-bugs
mailing list