From: "Kaveh R. Ghazi" <ghazi@caip.rutgers.edu>
To: brobecker@gnat.com
Cc: dj@redhat.com, gcc-patches@gcc.gnu.org, gdb-patches@sources.redhat.com
Subject: Re: Re: [RFA/PING] Fix libiberty compilation failure on systems running AiX 4.x
Date: Fri, 13 Jun 2003 01:48:00 -0000 [thread overview]
Message-ID: <200306130148.VAA12952@caip.rutgers.edu> (raw)
In-Reply-To: <20030613000346.GB947@gnat.com>
> It would be nice to have this looked at in the near future because it
> currently fails to build on AiX 4.x, and the GDB 6 release is getting
> nearer. I'd rather have this problem be fixed before we cut the GDB6
> branch.
> Thank you,
Sorry, this patch is wrong. It deactivates the code on all aix4*,
whereas the code is correct on 4.3.3 and later. It is only on 4.3.2
and prior that this code breaks.
Rather than hardwire aix version numbers, the correct fix is to use an
autoconf feature test. See this bug report:
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=10974
I (just a few days ago) installed this exact fix in gcc's libiberty.
What needs to happen is for this code to be copied into gdb and
binutils. I don't have access to these repos, which is why I copied
DJ on the install email. I should have explicitly mentioned that I
needed him to propagate it, sorry for not saying so.
DJ would you please sync this patch with the other libiberty repos?
http://gcc.gnu.org/ml/gcc-patches/2003-06/msg00767.html
Thanks,
--Kaveh
--
Kaveh R. Ghazi ghazi@caip.rutgers.edu
next prev parent reply other threads:[~2003-06-13 1:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-01 7:01 [RFA] " Joel Brobecker
2003-06-13 0:04 ` [RFA/PING] " Joel Brobecker
2003-06-13 1:48 ` Kaveh R. Ghazi [this message]
2003-06-13 1:51 ` DJ Delorie
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=200306130148.VAA12952@caip.rutgers.edu \
--to=ghazi@caip.rutgers.edu \
--cc=brobecker@gnat.com \
--cc=dj@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=gdb-patches@sources.redhat.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