From: Tom Rix <trix@redhat.com>
To: binutils@sources.redhat.com, hjl@gnu.org
Subject: [patch] Fix bfd config problem on aix
Date: Tue, 28 Aug 2001 15:32:00 -0000 [thread overview]
Message-ID: <3B8C1C07.DB85AE47@redhat.com> (raw)
The rs6000coff64_vec needs to always be compiled in for powerpc-*-aix targets
because AIX mixes 32 and 64 objects its big archive format.
This reverts part of an earlier patch.
--
Tom Rix
GCC Engineer
trix@redhat.com
256.704.9201
Index: ChangeLog
===================================================================
RCS file: /cvs/src/src/bfd/ChangeLog,v
retrieving revision 1.1010
diff -c -p -r1.1010 ChangeLog
*** ChangeLog 2001/08/27 18:04:37 1.1010
--- ChangeLog 2001/08/28 22:16:30
***************
*** 1158,1166 ****
2001-06-02 H.J. Lu <hjl@gnu.org>
! * config.bfd (powerpc-*-aix*, powerpc-*-beos*, rs6000-*-*): Add
! rs6000coff64_vec only if BFD64 is defined.
! (powerpc64-*-aix*): Enable only if BFD64 is defined.
2001-06-02 H.J. Lu <hjl@gnu.org>
--- 1163,1169 ----
2001-06-02 H.J. Lu <hjl@gnu.org>
! * config.bfd (powerpc64-*-aix*): Enable only if BFD64 is defined.
2001-06-02 H.J. Lu <hjl@gnu.org>
Index: config.bfd
===================================================================
RCS file: /cvs/src/src/bfd/config.bfd,v
retrieving revision 1.63
diff -c -p -r1.63 config.bfd
*** config.bfd 2001/08/27 10:22:03 1.63
--- config.bfd 2001/08/28 22:16:30
*************** case "${targ}" in
*** 727,733 ****
powerpc-*-aix* | powerpc-*-beos* | rs6000-*-*)
targ_defvec=rs6000coff_vec
! targ64_selvecs="rs6000coff64_vec"
;;
#ifdef BFD64
powerpc64-*-aix*)
--- 727,733 ----
powerpc-*-aix* | powerpc-*-beos* | rs6000-*-*)
targ_defvec=rs6000coff_vec
! targ_selvecs="rs6000coff64_vec"
;;
#ifdef BFD64
powerpc64-*-aix*)
next reply other threads:[~2001-08-28 15:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-28 15:32 Tom Rix [this message]
2001-08-28 15:41 ` H . J . Lu
2001-08-28 22:14 ` Alan Modra
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=3B8C1C07.DB85AE47@redhat.com \
--to=trix@redhat.com \
--cc=binutils@sources.redhat.com \
--cc=hjl@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).