Re: [gentoo-dev] java and jikes

[Peter Ruskin <aoyu93@dsl.pipex.com>]

On Friday 18 Oct 2002 00:45, Karl Trygve Kalleberg wrote:
> On Wed, 16 Oct 2002, Peter Ruskin wrote:
> > # emerge jikes
> > Calculating dependencies ...done!
> >
> > >>> emerge dev-java/jikes-1.17 to /
> > >>> md5 ;-) jikes-1.17.tar.bz2
> > >>> Unpacking source...
> > >>> Unpacking jikes-1.17.tar.bz2
> > >>> Source unpacked.
> >
> > configure: WARNING: If you wanted to set the --build type, don't
> > use --host.
> >     If a cross compiler is detected then cross compile mode will be
> > used.
> > checking for a BSD-compatible install... /bin/install -c
> > checking whether build environment is sane... yes
> > checking for gawk... gawk
> > checking whether make sets ${MAKE}... yes
> > checking for i686-pc-linux-gnu-strip... no
> > checking for strip... strip
> > checking whether to enable maintainer-specific portions of
> > Makefiles... no
> > checking build system type... i686-pc-linux-gnu
> > checking host system type... i686-pc-linux-gnu
> > checking for i686-pc-linux-gnu-g++... i686-pc-linux-gnu-g++
> > checking for C++ compiler default output... configure: error: C++
> > compiler cannot create executables
> >
> > !!! ERROR: The ebuild did not complete successfully.
> > !!! Function src_compile, Line 22, Exitcode 77
> > !!! configure problem
> >
> > This is strange - no other app yet has had trouble with g++.  I had
> > jikes-1.16 already and `emerge -u world` wanted to upgrade to 1.17.
> > When that failed I unmerged 1.16 and retried 1.17 and now I have no
> > jikes.
>
> emerge "=dev-java/jikes-1.16"
>
> If that works, you've hit upon a nasty one. Please use
> bugs.gentoo.org to file a complaint about this. If at all possible,
> include the config.log found in somewhere in the
> /var/tmp/portage/jikes-1.17/work/jikes-1.17 tree (probably in that
> exact directory).

Thanks.  No, that didn't work.  It was looking for 
/usr/bin/i686-pc-linux-gnu-g++, which had disappeared while I had been 
experimenting with bug #9016.  After I unmerged gcc-2.95 and emerged 
gcc-3.2 it was OK.  Sorry for the false alarm.
>
> > On re-emerging sun-jdk and blackdown-jdk I ended up with an empty
> > /etc/env.d/java folder.  At the end of a re-emerge the appropriate
> > file is created in /etc/env.d/java and then deleted when previous
> > version is cleaned.  I had to unmerge and emerge each in order to
> > have `java-config` work.
>
> This is a known bug in Portage. Sorry.

Yes, still there in 2.0.40 too :-(
>
>
> Kind regards,
>
> Karl T

-- 
Gentoo Linux 1.4 (Portage 2.0.40).  KDE: 3.0.4  Qt: 3.0.5
AMD Athlon(tm) XP 1600+ 512MB.	Kernel: 2.4.19-win4lin.	GCC 3.2
Linux user #275590 (http://counter.li.org/).  up 11:32.