| 1 |
On Wed, 16 Oct 2002, Peter Ruskin wrote: |
| 2 |
|
| 3 |
> # emerge jikes |
| 4 |
> Calculating dependencies ...done! |
| 5 |
> >>> emerge dev-java/jikes-1.17 to / |
| 6 |
> >>> md5 ;-) jikes-1.17.tar.bz2 |
| 7 |
> >>> Unpacking source... |
| 8 |
> >>> Unpacking jikes-1.17.tar.bz2 |
| 9 |
> >>> Source unpacked. |
| 10 |
> configure: WARNING: If you wanted to set the --build type, don't use |
| 11 |
> --host. |
| 12 |
> If a cross compiler is detected then cross compile mode will be |
| 13 |
> used. |
| 14 |
> checking for a BSD-compatible install... /bin/install -c |
| 15 |
> checking whether build environment is sane... yes |
| 16 |
> checking for gawk... gawk |
| 17 |
> checking whether make sets ${MAKE}... yes |
| 18 |
> checking for i686-pc-linux-gnu-strip... no |
| 19 |
> checking for strip... strip |
| 20 |
> checking whether to enable maintainer-specific portions of Makefiles... |
| 21 |
> no |
| 22 |
> checking build system type... i686-pc-linux-gnu |
| 23 |
> checking host system type... i686-pc-linux-gnu |
| 24 |
> checking for i686-pc-linux-gnu-g++... i686-pc-linux-gnu-g++ |
| 25 |
> checking for C++ compiler default output... configure: error: C++ |
| 26 |
> compiler cannot create executables |
| 27 |
> |
| 28 |
> !!! ERROR: The ebuild did not complete successfully. |
| 29 |
> !!! Function src_compile, Line 22, Exitcode 77 |
| 30 |
> !!! configure problem |
| 31 |
> |
| 32 |
> This is strange - no other app yet has had trouble with g++. I had |
| 33 |
> jikes-1.16 already and `emerge -u world` wanted to upgrade to 1.17. |
| 34 |
> When that failed I unmerged 1.16 and retried 1.17 and now I have no |
| 35 |
> jikes. |
| 36 |
|
| 37 |
emerge "=dev-java/jikes-1.16" |
| 38 |
|
| 39 |
If that works, you've hit upon a nasty one. Please use bugs.gentoo.org to |
| 40 |
file a complaint about this. If at all possible, include the config.log |
| 41 |
found in somewhere in the /var/tmp/portage/jikes-1.17/work/jikes-1.17 |
| 42 |
tree (probably in that exact directory). |
| 43 |
|
| 44 |
> On re-emerging sun-jdk and blackdown-jdk I ended up with an empty |
| 45 |
> /etc/env.d/java folder. At the end of a re-emerge the appropriate file |
| 46 |
> is created in /etc/env.d/java and then deleted when previous version is |
| 47 |
> cleaned. I had to unmerge and emerge each in order to have |
| 48 |
> `java-config` work. |
| 49 |
|
| 50 |
This is a known bug in Portage. Sorry. |
| 51 |
|
| 52 |
|
| 53 |
Kind regards, |
| 54 |
|
| 55 |
Karl T |
Archives