From: Gerald Pfeifer <pfeifer@dbai.tuwien.ac.at>
To: Alexandre Oliva <aoliva@redhat.com>
Cc: Gabriel Dos Reis <gdr@integrable-solutions.net>,
gcc@gcc.gnu.org, java@gcc.gnu.org, Joe Buck <jbuck@synopsys.com>,
Eric Botcazou <ebotcazou@libertysurf.fr>,
"H. J. Lu" <hjl@lucon.org>
Subject: libjava build still fails on sparc-sun-solaris2.9
Date: Fri, 25 Apr 2003 14:45:00 -0000 [thread overview]
Message-ID: <Pine.BSF.4.53.0304251601280.37103@naos.dbai.tuwien.ac.at> (raw)
In-Reply-To: <oradehax51.fsf@localhost.localdomain>
Alexandre, thanks for the quick response!
Unfortunately, we missed GCC 3.2.3, but I did some testing, and the
problem also occurs on the 3.3 branch, and there it's not too late.
On Wed, 23 Apr 2003, Alexandre Oliva wrote:
>> | I first reported a variant of this problem in
>> | http://gcc.gnu.org/ml/gcc/2002-06/threads.html#00284
>> | but didn't notice it on the 3.2 branch until now, because I had Java
>> | disabled on the slow Solaris boxes. :-(
> The one thing that is getting me confused is the long list of object
> files in the link command. libtool could use -z allextract instead of
> extracting the object files itself. Currently, for some reason,
> libtool would use it when using Sun CC, or gcc as a C or Java linker,
> but not when using gcc as a C++ linker (I haven't investigated why it
> thinks we're doing C++ instead of Java).
>
> Gerald, could you please test whether this patch fixes the problem?
Unfortunately, it does not seem to make a difference on
sparc-sun-solaris2.9.
I put up the build log at <http://www.pfeifer.com/gerald/tmp/buildlog.gz>
and if you check that, even _with_ your patch, we have that long command-
line.
Gerald
PS: If it appears useful to you, I probably can arrange a guest account
for you on that machine.
prev parent reply other threads:[~2003-04-25 14:07 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-17 16:56 3.2.3-pre tarball 2: libjava build still fails on sparc-sun-solaris2.8 Joe Buck
2003-04-17 18:15 ` H. J. Lu
2003-04-17 22:16 ` Joe Buck
2003-04-18 16:26 ` Eric Botcazou
2003-04-18 17:18 ` Joe Buck
2003-04-18 17:25 ` Gabriel Dos Reis
2003-04-19 7:42 ` Eric Botcazou
2003-04-21 16:57 ` Joe Buck
2003-04-21 3:36 ` Gerald Pfeifer
2003-04-21 13:54 ` Gabriel Dos Reis
2003-04-23 19:03 ` Alexandre Oliva
2003-04-23 19:24 ` Joe Buck
2003-04-23 23:35 ` Alexandre Oliva
2003-04-24 16:15 ` Michael S. Zick
2003-04-25 14:45 ` Gerald Pfeifer [this message]
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.BSF.4.53.0304251601280.37103@naos.dbai.tuwien.ac.at \
--to=pfeifer@dbai.tuwien.ac.at \
--cc=aoliva@redhat.com \
--cc=ebotcazou@libertysurf.fr \
--cc=gcc@gcc.gnu.org \
--cc=gdr@integrable-solutions.net \
--cc=hjl@lucon.org \
--cc=java@gcc.gnu.org \
--cc=jbuck@synopsys.com \
/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).