public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: "H. J. Lu" <hjl@lucon.org>
To: Geert Bosch <bosch@gnat.com>
Cc: Mark Mitchell <mark@codesourcery.com>,
	Zdenek Dvorak <rakdver@atrey.karlin.mff.cuni.cz>,
	gcc mailing list <gcc@gcc.gnu.org>
Subject: Re: Build problem on ia64 (reverting patch on 3.4 branch)
Date: Thu, 23 Sep 2004 20:13:00 -0000	[thread overview]
Message-ID: <20040923184202.GB4807@lucon.org> (raw)
In-Reply-To: <2187C89A-0D8C-11D9-9684-000A959A128E@gnat.com>

On Thu, Sep 23, 2004 at 02:12:29PM -0400, Geert Bosch wrote:
> 
> On Sep 22, 2004, at 11:51, H. J. Lu wrote:
> >http://gcc.gnu.org/bugzilla/show_bug.cgi?id=17464
> 
> Apparently, a similar failure occurs with Ada (make gnatlib_and_tools)
> on the GCC 3.4 branch. In my opinion a patch that:
>   1) requires updating the system linker, and
>   2) has such a high potential for bootstrap/build problems

Please try

http://gcc.gnu.org/ml/gcc-patches/2004-09/msg02413.html

> should not go on a stable branch like the gcc-3_4-branch. If we have
> so many problems building our own tools, likely people will run in
> related issues on their own projects to. This is not a safe patch!
> As far as I understand the new ABI, there should still be backward
> compatibility, so there would be no pressing need for gcc-3_4 to
> implement this new ABI.
> 
> Because of the above concerns I'd like to request that this patch
> be reverted on the 3.4 branch.

The problem is nothing new. If you make the system libgcc_s.so.1
unavailable to the newly built gcc, many things will fail. See

http://gcc.gnu.org/ml/gcc/2004-09/msg00209.html


H.J.

  reply	other threads:[~2004-09-23 18:42 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-22 13:20 Build problem on ia64 Zdenek Dvorak
2004-09-22 13:39 ` Paolo Carlini
2004-09-22 16:33 ` H. J. Lu
2004-09-23 20:04   ` Build problem on ia64 (reverting patch on 3.4 branch) Geert Bosch
2004-09-23 20:13     ` H. J. Lu [this message]
2004-09-23 21:40       ` Geert Bosch
2004-09-24  0:05         ` H. J. Lu
2004-09-24  0:09           ` H. J. Lu
2004-09-24 20:20             ` Geert Bosch
2004-09-24 20:36               ` H. J. Lu

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=20040923184202.GB4807@lucon.org \
    --to=hjl@lucon.org \
    --cc=bosch@gnat.com \
    --cc=gcc@gcc.gnu.org \
    --cc=mark@codesourcery.com \
    --cc=rakdver@atrey.karlin.mff.cuni.cz \
    /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).