This is the mail archive of the
binutils@sourceware.cygnus.com
mailing list for the binutils project.
Re: [PATCH RFA] bfd/configure.in, bfd/configure
- To: kevinb at cygnus dot com
- Subject: Re: [PATCH RFA] bfd/configure.in, bfd/configure
- From: Ian Lance Taylor <ian at zembu dot com>
- Date: 17 Feb 2000 12:12:42 -0500
- CC: binutils at sourceware dot cygnus dot com
- References: <Pine.LNX.4.10.10002172046460.1544-100000@mullet.itr.unisa.edu.au> <1000217104204.ZM5172@ocotillo.lan>
Date: Thu, 17 Feb 2000 03:42:04 -0700
From: Kevin Buettner <kevinb@cygnus.com>
Right you are. I fixed it in my tree. Here's a revised patch:
Index: configure.in
===================================================================
RCS file: /cvs/src/src/bfd/configure.in,v
retrieving revision 1.12
diff -u -p -r1.12 configure.in
--- configure.in 2000/01/10 18:50:16 1.12
+++ configure.in 2000/02/17 10:40:29
@@ -260,6 +260,12 @@ changequote([,])dnl
COREFILE=netbsd-core.lo
;;
rs6000-*-lynx*) COREFILE=lynx-core.lo ;;
+changequote(,)dnl
+ rs6000-*-aix4.[3-9]* | powerpc-*-aix4.[3-9]*)
+changequote([,])dnl
+ COREFILE=rs6000-core.lo
+ COREFLAG="$COREFLAG -DAIX_CORE_DUMPX_CORE"
+ ;;
rs6000-*-aix4*) COREFILE=rs6000-core.lo ;;
rs6000-*-*) COREFILE=rs6000-core.lo ;;
powerpc-*-*bsd*) COREFILE=netbsd-core.lo ;;
This is OK.
Consider: is there any preprocessor macro defined on AIX that you can
check for this, rather than relying on a configuration name match?
The file rs6000-core.c is only compiled on an AIX target, so it is OK
to check for AIX specific preprocessor macros, if there are any.
What should happen for aix5?
Ian