From: Karl Trygve Kalleberg <karltk@prosalg.no>
To: Peter Ruskin <aoyu93@dsl.pipex.com>
Cc: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] java and jikes
Date: Fri, 18 Oct 2002 01:45:41 +0200 (MET DST) [thread overview]
Message-ID: <Pine.LNX.3.96.1021018014311.14368G-100000@pluto.prosalg.no> (raw)
In-Reply-To: <200210161845.04280.aoyu93@dsl.pipex.com>
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).
> 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.
Kind regards,
Karl T
next prev parent reply other threads:[~2002-10-17 23:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-16 17:45 [gentoo-dev] java and jikes Peter Ruskin
2002-10-17 23:45 ` Karl Trygve Kalleberg [this message]
2002-10-18 3:22 ` Peter Ruskin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Pine.LNX.3.96.1021018014311.14368G-100000@pluto.prosalg.no \
--to=karltk@prosalg.no \
--cc=aoyu93@dsl.pipex.com \
--cc=gentoo-dev@gentoo.org \
--cc=karltk@gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox