public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: "H. J. Lu" <hjl@lucon.org>
To: Paolo Bonzini <bonzini@gnu.org>
Cc: Andrew Haley <aph-gcc@littlepinkcloud.COM>,
		Matthias Klose <doko@ubuntu.com>,
	gcc-patches@gcc.gnu.org, 	java-patches@gcc.gnu.org,
	libtool-patches@gnu.org
Subject: Re: PATCH: PR libjava/32078: Update libtool in classpath
Date: Tue, 29 May 2007 15:26:00 -0000	[thread overview]
Message-ID: <20070529151552.GA13457@lucon.org> (raw)
In-Reply-To: <465C4185.7050604@gnu.org>

On Tue, May 29, 2007 at 05:06:45PM +0200, Paolo Bonzini wrote:
> 
> >>>>Certainly.  Any compile-and-link tests won't work.
> >>>I'm sorry, I missed the "and link" part of your question.  Configury
> >>>tests of this kind really aren't going to work.  For things like tests
> >>>for PIC, it's pointless: gcj supports the same options as gcc.
> >>Then, does anybody know the very reason why all those tests are run 
> >>repeatedly for each language?
> >
> >I will guess. It is because the C/C++/Java/Fortran/.. compilers may
> >not come from the same gcc version or based on gcc at all.
> 
> Okay, so we have a problem.  Because the patch you are proposing will 
> not be accepted in any way by upstream. :-(

Bulding an XXX language run-time library is a very special case. You
can't build an XXX language run-time library, assuming the XXX language
compiler is fully functional.  If upstream libtool can support it, it
is great. Otherwise, we have to do one of these 4:

1. Drop Java.
2. Drop libtool for libjava.
3. Hack libtool for libjava.
4. Hack libjava configure to work around the libtool problem.

I proposed #3 with a simple and straightforward work around. We may
have to keep it around forever.


H.J.

  parent reply	other threads:[~2007-05-29 15:16 UTC|newest]

Thread overview: 46+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-27 18:25 H. J. Lu
2007-05-27 18:53 ` H. J. Lu
     [not found] ` <20070527182317.GA21785@lucon.org>
2007-05-29 10:25   ` Andrew Haley
2007-05-29 10:46     ` Andreas Schwab
2007-05-29 10:48       ` Andrew Haley
2007-05-29 13:10         ` Paolo Bonzini
2007-05-29 12:17   ` Matthias Klose
2007-05-29 13:43     ` H. J. Lu
2007-05-29 13:44       ` Paolo Bonzini
2007-05-29 13:47         ` H. J. Lu
2007-05-29 13:55           ` Paolo Bonzini
2007-05-29 14:25             ` Andrew Haley
2007-05-29 14:36               ` H. J. Lu
2007-05-29 14:40                 ` Andrew Haley
2007-05-29 14:41                   ` H. J. Lu
2007-05-29 14:43                     ` Andrew Haley
2007-05-29 14:49                       ` Andrew Haley
2007-05-29 15:09                         ` Paolo Bonzini
2007-05-29 15:19                           ` H. J. Lu
2007-05-29 15:19                             ` Paolo Bonzini
2007-05-29 15:25                               ` Andrew Haley
2007-05-29 15:36                                 ` H. J. Lu
2007-05-29 15:26                               ` H. J. Lu [this message]
2007-05-29 15:44                                 ` Andrew Haley
2007-05-29 17:16                                   ` Maciej W. Rozycki
2007-05-29 14:46                     ` Paolo Bonzini
2007-05-29 14:54                       ` Andrew Haley
2007-05-29 14:59                       ` Paolo Bonzini
2007-05-29 16:32         ` Andreas Schwab
2007-05-29 16:41           ` H. J. Lu
2007-05-29 17:21             ` Andreas Schwab
2007-05-29 17:36               ` H. J. Lu
2007-05-29 17:54                 ` Andreas Schwab
2007-05-29 18:29                   ` H. J. Lu
2007-05-29 18:35                     ` Tom Tromey
2007-05-29 23:14                       ` H. J. Lu
2007-05-30  8:22                         ` Paolo Bonzini
2007-05-30 17:46                         ` Tom Tromey
2007-05-30 18:03                           ` H. J. Lu
2007-05-30 18:19                             ` Tom Tromey
2007-05-31  9:37                               ` Paolo Bonzini
2007-05-31 15:26                                 ` Tom Tromey
2007-05-30 20:01                             ` Peter O'Gorman
2007-05-30 22:37                               ` H. J. Lu
2007-05-29 17:05 Charles Wilson
2007-05-29 17:07 ` Charles Wilson

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=20070529151552.GA13457@lucon.org \
    --to=hjl@lucon.org \
    --cc=aph-gcc@littlepinkcloud.COM \
    --cc=bonzini@gnu.org \
    --cc=doko@ubuntu.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=java-patches@gcc.gnu.org \
    --cc=libtool-patches@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).