public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "r dot emrich at de dot tecosim dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug java/21206] gcj seems not to pass the option to ld correctly
Date: Thu, 23 Feb 2006 16:17:00 -0000 [thread overview]
Message-ID: <20060223161708.10049.qmail@sourceware.org> (raw)
In-Reply-To: <bug-21206-10071@http.gcc.gnu.org/bugzilla/>
------- Comment #11 from r dot emrich at de dot tecosim dot com 2006-02-23 16:17 -------
Subject: Re: gcj seems not to pass the option to ld correctly
Andrew Haley schrieb:
> Rainer Emrich writes:
> > -----BEGIN PGP SIGNED MESSAGE-----
> > Hash: SHA1
> >
> > Andrew Haley schrieb:
> > > Rainer Emrich writes:
> > > > The config.log in libjava has two entries for libiconv:
> > > > LIBICONV
> > > > which is
> > > > LIBICONV='/appl/shared/gnu/Linux/ia64-unknown-linux-gnu/lib/libiconv.so
> > > > -Wl,-rpath -Wl,/appl/shared/gnu/Linux/ia64-unknown-linux-gnu/lib'
> > > > in my case.
> > > >
> > > > The second is
> > > > LTLIBICONV
> > > > which is
> > > > LTLIBICONV='-L/appl/shared/gnu/Linux/ia64-unknown-linux-gnu/lib -liconv
> > > > -R/appl/shared/gnu/Linux/ia64-unknown-linux-gnu/lib'
> > > > in my case.
> > > >
> > > > I changed the libgcj.spec file manually to the second. That seems to work.
> > > > So, my conclusion is to change the libgcj.spec.in.
> > > > The following line:
> > > > *lib: -lgcj -lm @LIBICONV@ @GCSPEC@ @THREADSPEC@ @ZLIBSPEC@ @SYSTEMSPEC@
> > > > %(libgcc) %(liborig)
> > > > should be changed to
> > > > *lib: -lgcj -lm @LTLIBICONV@ @GCSPEC@ @THREADSPEC@ @ZLIBSPEC@ @SYSTEMSPEC@
> > > > %(libgcc) %(liborig)
> > > >
> > > > Any comments?
> > >
> > > Looks right to me. BTW, what failure caused you to find this?
>
> > See the following messages:
> >
> > http://gcc.gnu.org/ml/gcc/2006-02/msg00415.html
> > http://gcc.gnu.org/ml/gcc/2006-02/msg00482.html
>
> Yes, I agree with your reasoning. AFAIK Mark Mitchell has to approve
> this as it's for the release, but it's OK by me if it passes
> bootstrap.
>
> I don't see this problem on my system because LIBICONV and LTLIBICONV
> are both null. AFAIK that's because iconv is in libc.
>
> Andrew.
Bootstrap passed at my site for ia64-unknown-linux-gnu.
Testsuite run for libjaava gives:
=== libjava Summary ===
# of expected passes 4009
# of unexpected failures 1
# of expected failures 10
# of untested testcases 8
Rainer
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=21206
next prev parent reply other threads:[~2006-02-23 16:17 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-21206-10071@http.gcc.gnu.org/bugzilla/>
2006-02-23 11:04 ` r dot emrich at de dot tecosim dot com
2006-02-23 13:39 ` aph at redhat dot com
2006-02-23 14:46 ` r dot emrich at de dot tecosim dot com
2006-02-23 15:41 ` aph at redhat dot com
2006-02-23 16:17 ` r dot emrich at de dot tecosim dot com [this message]
2006-02-24 1:05 ` wilson at gcc dot gnu dot org
2006-02-24 15:05 ` Ralf dot Wildenhues at gmx dot de
2006-02-25 8:15 ` shanwill44 at yahoo dot com
2007-11-14 23:04 ` pinskia at gcc dot gnu dot org
2007-11-14 23:17 ` tom_francen at midtechcorp dot com
2007-11-14 23:46 ` wilson at tuliptree dot org
2007-11-15 13:46 ` tom_francen at midtechcorp dot com
2009-08-17 15:16 ` org dot gnu dot gcc dot bugzilla at pooryorick dot com
2009-11-07 12:24 ` pierre42d at 9online dot fr
[not found] <bug-21206-4@http.gcc.gnu.org/bugzilla/>
2011-01-10 18:46 ` rwild at gcc dot gnu.org
2011-01-10 19:05 ` rwild at gcc dot gnu.org
2011-01-29 12:04 ` rwild at gcc dot gnu.org
2011-02-04 5:52 ` rwild at gcc dot gnu.org
2005-04-25 9:14 [Bug bootstrap/21206] New: " shanwill44 at yahoo dot com
2005-04-25 13:31 ` [Bug java/21206] " pinskia at gcc dot gnu dot org
2005-04-25 13:33 ` pinskia at gcc dot gnu dot org
2005-04-26 0:11 ` shanwill44 at yahoo dot com
2005-07-13 19:44 ` pinskia at gcc dot gnu dot org
2005-07-13 19:44 ` pinskia at gcc dot gnu dot org
2005-07-13 19:47 ` pinskia at gcc dot gnu dot org
2005-07-13 19:52 ` pinskia at gcc dot gnu dot org
2005-07-26 23:32 ` wilson at gcc dot gnu dot org
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=20060223161708.10049.qmail@sourceware.org \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@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).