1 |
On Friday 18 Oct 2002 00:45, Karl Trygve Kalleberg wrote: |
2 |
> On Wed, 16 Oct 2002, Peter Ruskin wrote: |
3 |
> > # emerge jikes |
4 |
> > Calculating dependencies ...done! |
5 |
> > |
6 |
> > >>> emerge dev-java/jikes-1.17 to / |
7 |
> > >>> md5 ;-) jikes-1.17.tar.bz2 |
8 |
> > >>> Unpacking source... |
9 |
> > >>> Unpacking jikes-1.17.tar.bz2 |
10 |
> > >>> Source unpacked. |
11 |
> > |
12 |
> > configure: WARNING: If you wanted to set the --build type, don't |
13 |
> > use --host. |
14 |
> > If a cross compiler is detected then cross compile mode will be |
15 |
> > used. |
16 |
> > checking for a BSD-compatible install... /bin/install -c |
17 |
> > checking whether build environment is sane... yes |
18 |
> > checking for gawk... gawk |
19 |
> > checking whether make sets ${MAKE}... yes |
20 |
> > checking for i686-pc-linux-gnu-strip... no |
21 |
> > checking for strip... strip |
22 |
> > checking whether to enable maintainer-specific portions of |
23 |
> > Makefiles... no |
24 |
> > checking build system type... i686-pc-linux-gnu |
25 |
> > checking host system type... i686-pc-linux-gnu |
26 |
> > checking for i686-pc-linux-gnu-g++... i686-pc-linux-gnu-g++ |
27 |
> > checking for C++ compiler default output... configure: error: C++ |
28 |
> > compiler cannot create executables |
29 |
> > |
30 |
> > !!! ERROR: The ebuild did not complete successfully. |
31 |
> > !!! Function src_compile, Line 22, Exitcode 77 |
32 |
> > !!! configure problem |
33 |
> > |
34 |
> > This is strange - no other app yet has had trouble with g++. I had |
35 |
> > jikes-1.16 already and `emerge -u world` wanted to upgrade to 1.17. |
36 |
> > When that failed I unmerged 1.16 and retried 1.17 and now I have no |
37 |
> > jikes. |
38 |
> |
39 |
> emerge "=dev-java/jikes-1.16" |
40 |
> |
41 |
> If that works, you've hit upon a nasty one. Please use |
42 |
> bugs.gentoo.org to file a complaint about this. If at all possible, |
43 |
> include the config.log found in somewhere in the |
44 |
> /var/tmp/portage/jikes-1.17/work/jikes-1.17 tree (probably in that |
45 |
> exact directory). |
46 |
|
47 |
Thanks. No, that didn't work. It was looking for |
48 |
/usr/bin/i686-pc-linux-gnu-g++, which had disappeared while I had been |
49 |
experimenting with bug #9016. After I unmerged gcc-2.95 and emerged |
50 |
gcc-3.2 it was OK. Sorry for the false alarm. |
51 |
> |
52 |
> > On re-emerging sun-jdk and blackdown-jdk I ended up with an empty |
53 |
> > /etc/env.d/java folder. At the end of a re-emerge the appropriate |
54 |
> > file is created in /etc/env.d/java and then deleted when previous |
55 |
> > version is cleaned. I had to unmerge and emerge each in order to |
56 |
> > have `java-config` work. |
57 |
> |
58 |
> This is a known bug in Portage. Sorry. |
59 |
|
60 |
Yes, still there in 2.0.40 too :-( |
61 |
> |
62 |
> |
63 |
> Kind regards, |
64 |
> |
65 |
> Karl T |
66 |
|
67 |
-- |
68 |
Gentoo Linux 1.4 (Portage 2.0.40). KDE: 3.0.4 Qt: 3.0.5 |
69 |
AMD Athlon(tm) XP 1600+ 512MB. Kernel: 2.4.19-win4lin. GCC 3.2 |
70 |
Linux user #275590 (http://counter.li.org/). up 11:32. |