From: "Martin M. Hunt" <hunt@redhat.com>
To: gdb-patches@sources.redhat.com
Subject: [RFA] fix AIX builds
Date: Thu, 20 Feb 2003 05:40:00 -0000 [thread overview]
Message-ID: <1045719632.1640.4.camel@Dragon> (raw)
[-- Attachment #1: Type: text/plain, Size: 548 bytes --]
AIX builds are failing because CONFIG_LDFLAGS is getting set to
-lpthdebug which results in the library being linked before all the
object files. The library needs to be after the object files and
CONFIG_LDFLAGS is for flags not libraries. This patch basically reverts
a previous one from a few months ago. There might be a better way to do
this but this seems to work OK for me.
2003-02-19 Martin M. Hunt <hunt@redhat.com>
* configure.in: Don't set CONFIG_LDFLAGS to -lpthdebug.
* config/powerpc/aix432.mh (NAT_CLIBS): Set to -lpthdebug.
[-- Attachment #2: p --]
[-- Type: text/x-patch, Size: 1054 bytes --]
Index: configure.in
===================================================================
RCS file: /cvs/src/src/gdb/configure.in,v
retrieving revision 1.124
diff -u -r1.124 configure.in
--- configure.in 17 Feb 2003 21:56:29 -0000 1.124
+++ configure.in 20 Feb 2003 05:35:58 -0000
@@ -875,7 +875,6 @@
if test $gdb_cv_have_aix_thread_debug = yes; then
CONFIG_SRCS="${CONFIG_SRCS} aix-thread.c"
CONFIG_LIB_OBS="${CONFIG_LIB_OBS} aix-thread.o"
- CONFIG_LDFLAGS="${CONFIG_LDFLAGS} -lpthdebug"
fi
;;
esac
Index: config/powerpc/aix432.mh
===================================================================
RCS file: /cvs/src/src/gdb/config/powerpc/aix432.mh,v
retrieving revision 1.3
diff -u -r1.3 aix432.mh
--- config/powerpc/aix432.mh 2 Dec 2002 15:44:22 -0000 1.3
+++ config/powerpc/aix432.mh 20 Feb 2003 05:35:58 -0000
@@ -17,3 +17,5 @@
# This switch may be needed for some vendor compilers.
# MH_LDFLAGS = -Wl,-bbigtoc
+# pthread debugging support
+NAT_CLIBS = -lpthdebug
next reply other threads:[~2003-02-20 5:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-20 5:40 Martin M. Hunt [this message]
2003-02-20 13:04 ` Andrew Cagney
2003-02-20 15:04 ` Kevin Buettner
2003-02-20 23:19 ` Joel Brobecker
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=1045719632.1640.4.camel@Dragon \
--to=hunt@redhat.com \
--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