Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Andreas Schwab <schwab@linux-m68k.org>
To: Jan Kratochvil <jan.kratochvil@redhat.com>
Cc: "H.J. Lu" <hjl.tools@gmail.com>,  gdb-patches@sourceware.org
Subject: Re: [patch] Smaller gdb: -rdynamic -> -Wl,--dynamic-list
Date: Sun, 13 Jun 2010 20:17:00 -0000	[thread overview]
Message-ID: <m2ocfehem9.fsf@igel.home> (raw)
In-Reply-To: <m2sk4qhfh5.fsf@igel.home> (Andreas Schwab's message of "Sun, 13	Jun 2010 21:58:30 +0200")

Tested on ppc-linux.

Andreas.

2010-06-13  Andreas Schwab  <schwab@linux-m68k.org>

	* configure.ac: Check for RDYNAMIC also for cross builds.
	* configure: Regenerate.

--- configure.ac.~1.122.~	2010-06-12 23:13:19.000000000 +0200
+++ configure.ac	2010-06-13 22:09:54.000000000 +0200
@@ -1453,14 +1453,7 @@ aix*)
   ;;
 esac
 
-
-dnl For certain native configurations, we need to check whether thread
-dnl support can be built in or not.
-dnl
-dnl Note that we only want this if we are both native (host == target),
-dnl and not doing a canadian cross build (build == host).
-
-if test ${build} = ${host} -a ${host} = ${target} ; then
+if test "${gdb_native}" = yes; then
    if test "$GCC" = "yes" ; then
       # The dynamically loaded libthread_db needs access to symbols in the gdb
       # executable.  Older GNU ld supports --export-dynamic but --dynamic-list
@@ -1507,7 +1500,15 @@ if test ${build} = ${host} -a ${host} =
       LDFLAGS="$old_LDFLAGS"
       AC_MSG_RESULT($found)
    fi
+fi
 
+dnl For certain native configurations, we need to check whether thread
+dnl support can be built in or not.
+dnl
+dnl Note that we only want this if we are both native (host == target),
+dnl and not doing a canadian cross build (build == host).
+
+if test ${build} = ${host} -a ${host} = ${target} ; then
    case ${host_os} in
    hpux*)
       AC_MSG_CHECKING(for HPUX/OSF thread support)

-- 
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5
"And now for something completely different."


  reply	other threads:[~2010-06-13 20:17 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-13 13:27 Jan Kratochvil
2010-05-13 15:47 ` H.J. Lu
2010-05-16 21:08   ` Jan Kratochvil
2010-05-27 19:58     ` Tom Tromey
2010-05-28 23:11       ` Jan Kratochvil
2010-06-05  2:48         ` Doug Evans
2010-06-05 12:45           ` Jan Kratochvil
2010-06-08 15:23             ` Doug Evans
2010-06-08 16:08               ` Jan Kratochvil
2010-06-08 16:12                 ` Doug Evans
2010-06-08 17:37                   ` Jan Kratochvil
2012-01-12 19:28           ` [patch] -Wl,--dynamic-list: Test also PYTHON_LIBS, not just PYTHON_CFLAGS [Re: [patch] Smaller gdb: -rdynamic -> -Wl,--dynamic-list] Jan Kratochvil
2010-06-13 19:58     ` [patch] Smaller gdb: -rdynamic -> -Wl,--dynamic-list Andreas Schwab
2010-06-13 20:17       ` Andreas Schwab [this message]
2010-06-15 17:31         ` Tom Tromey
2010-06-15 19:09           ` Jan Kratochvil
2010-06-15 20:36           ` Jan Kratochvil
2010-06-21 18:26             ` Tom Tromey
2010-06-23 10:13               ` Jan Kratochvil

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=m2ocfehem9.fsf@igel.home \
    --to=schwab@linux-m68k.org \
    --cc=gdb-patches@sourceware.org \
    --cc=hjl.tools@gmail.com \
    --cc=jan.kratochvil@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