public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Richard Earnshaw <rearnsha@arm.com>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: java/5487: arm-linux-gcj cross-compiler generates bad assembler-code
Date: Tue, 26 Mar 2002 05:46:00 -0000 [thread overview]
Message-ID: <20020326134604.17617.qmail@sources.redhat.com> (raw)
The following reply was made to PR java/5487; it has been noted by GNATS.
From: Richard Earnshaw <rearnsha@arm.com>
To: tromey@redhat.com
Cc: Richard.Earnshaw@arm.com, gcc-gnats@gcc.gnu.org
Subject: Re: java/5487: arm-linux-gcj cross-compiler generates bad
assembler-code
Date: Tue, 26 Mar 2002 13:41:34 +0000
tromey@redhat.com said:
> OTOH, rhug is sort of a special case. It is one of the important gcj
> applications that we want to build out of the box.
Except, of course, that it doesn't; particularly for a cross system.
~/gnusrc/rhug/configure --target=arm-elf --prefix=/home/rearnsha/gnu/egcs/a
rm-elf-install
...
checking for gcj... no
checking for gcjh... no
configure: error: no acceptable gcjh found in $PATH
cam-linux16:rhug [1006] $ arm-elf-gc
arm-elf-gcc arm-elf-gcj arm-elf-gcov
arm-elf-gccbug arm-elf-gcjh
It should be looking for the cross compiler, not a native one in a cross
build.
I'm sorry, I just don't have the time to spend tracking down this problem;
there's just too many prerequisites that are in the way. If someone can
produce an isolated test-case, which doesn't require pre-installing a load
of other packages, then I'll look into it further.
R.
next reply other threads:[~2002-03-26 13:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-26 5:46 Richard Earnshaw [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-01-01 18:26 neroden
2002-03-25 12:36 Tom Tromey
2002-03-25 3:46 Richard Earnshaw
2002-03-23 19:36 Tom Tromey
2002-03-23 9:47 rearnsha
2002-01-25 1:46 jsantala
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=20020326134604.17617.qmail@sources.redhat.com \
--to=rearnsha@arm.com \
--cc=gcc-prs@gcc.gnu.org \
--cc=nobody@gcc.gnu.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).