From: Andrew Haley <aph-gcc@littlepinkcloud.COM>
To: Paolo Bonzini <bonzini@gnu.org>
Cc: "H. J. Lu" <hjl@lucon.org>, 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:16:00 -0000 [thread overview]
Message-ID: <18012.16930.147277.271416@zebedee.pink> (raw)
In-Reply-To: <465C4185.7050604@gnu.org>
Paolo Bonzini writes:
>
> >>>> 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. :-(
How come we are doing this *now*? Why was it not a problem before,
and what has changed?
Andrew.
next prev parent reply other threads:[~2007-05-29 15:09 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-27 18:22 H. J. Lu
2007-05-27 18:25 ` H. J. Lu
2007-05-27 18:25 ` H. J. Lu
2007-05-29 9:47 ` Andrew Haley
2007-05-29 9:58 ` Andreas Schwab
2007-05-29 10:25 ` Andrew Haley
2007-05-29 12:17 ` Paolo Bonzini
2007-05-29 10:46 ` Matthias Klose
2007-05-29 13:10 ` H. J. Lu
2007-05-29 13:40 ` Paolo Bonzini
2007-05-29 13:43 ` H. J. Lu
2007-05-29 13:47 ` Paolo Bonzini
2007-05-29 14:06 ` Andrew Haley
2007-05-29 14:25 ` H. J. Lu
2007-05-29 14:27 ` Andrew Haley
2007-05-29 14:36 ` H. J. Lu
2007-05-29 14:40 ` Andrew Haley
2007-05-29 14:43 ` Andrew Haley
2007-05-29 14:59 ` Paolo Bonzini
2007-05-29 15:06 ` H. J. Lu
2007-05-29 15:09 ` Paolo Bonzini
2007-05-29 15:16 ` Andrew Haley [this message]
2007-05-29 15:19 ` H. J. Lu
2007-05-29 15:19 ` H. J. Lu
2007-05-29 15:44 ` Andrew Haley
2007-05-29 17:07 ` Maciej W. Rozycki
2007-05-29 14:41 ` Paolo Bonzini
2007-05-29 14:41 ` Paolo Bonzini
2007-05-29 14:49 ` Andrew Haley
2007-05-29 15:58 ` Andreas Schwab
2007-05-29 16:16 ` H. J. Lu
2007-05-29 17:16 ` Andreas Schwab
2007-05-29 17:37 ` H. J. Lu
2007-05-29 17:41 ` Andreas Schwab
2007-05-29 17:54 ` H. J. Lu
2007-05-29 17:55 ` Tom Tromey
2007-05-30 6:13 ` H. J. Lu
2007-05-30 15:55 ` Paolo Bonzini
2007-05-30 17:23 ` Tom Tromey
2007-05-30 17:42 ` H. J. Lu
2007-05-30 17:49 ` Tom Tromey
2007-05-31 14:48 ` Paolo Bonzini
2007-05-31 21:00 ` Tom Tromey
2007-05-30 21:13 ` Peter O'Gorman
2007-05-31 6:39 ` H. J. Lu
2007-05-29 16:24 Charles Wilson
2007-05-29 16:32 ` 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=18012.16930.147277.271416@zebedee.pink \
--to=aph-gcc@littlepinkcloud.com \
--cc=bonzini@gnu.org \
--cc=doko@ubuntu.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=hjl@lucon.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).