public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: "H.J. Lu" <hjl@lucon.org>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: java/5688: cross compiler build fails in libjava
Date: Sun, 02 Jun 2002 12:26:00 -0000 [thread overview]
Message-ID: <20020602192603.28260.qmail@sources.redhat.com> (raw)
The following reply was made to PR java/5688; it has been noted by GNATS.
From: "H.J. Lu" <hjl@lucon.org>
To: gcc-gnats@gcc.gnu.org, gcc-prs@gcc.gnu.org, pb@nexus.co.uk,
gcc-bugs@gcc.gnu.org, nobody@gcc.gnu.org,
java-prs@gcc.gnu.org?Subject=Re:, java/5688:@lucon.org,
cross@lucon.org, co@lucon.org
Cc:
Subject: Re: java/5688: cross compiler build fails in libjava
Date: Sun, 02 Jun 2002 12:18:11 -0700
http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=5688
Is anyone working on this bug? I guess the first thing should be done is
to change
if test -n "${with_cross_host}"; then
# We are being configured with a cross compiler. AC_REPLACE_FUNCS
# may not work correctly, because the compiler may not be able to
# link executables.
# We assume newlib. This lets us hard-code the functions we know
# we'll have.
AC_DEFINE(HAVE_MEMMOVE)
.....
to something similar in the toplevel configure.in which checks if newlib
is used
before blindly assuming we are compiling for newlib.
next reply other threads:[~2002-06-02 19:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-02 12:26 H.J. Lu [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-06-02 16:26 Tom Tromey
2002-02-14 9:46 Tom Tromey
2002-02-14 4:26 pb
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=20020602192603.28260.qmail@sources.redhat.com \
--to=hjl@lucon.org \
--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).