From: Daniel Jacobowitz <drow@false.org>
To: Jie Zhang <jzhang918@gmail.com>
Cc: gdb@sources.redhat.com
Subject: Re: An issue in configure.ac of gdbserver
Date: Fri, 30 Dec 2005 02:40:00 -0000 [thread overview]
Message-ID: <20051230024019.GB26004@nevyn.them.org> (raw)
In-Reply-To: <6f48278f0512282138i3c2a193fqdd4cf23182e75d2f@mail.gmail.com>
On Thu, Dec 29, 2005 at 01:38:29PM +0800, Jie Zhang wrote:
> Hi,
>
> This piece of code in configure.ac of gdbserver does not work as
> intended, since gcc only gives an warning if it does not accept
> -rdynamic.
>
> LDFLAGS="$LDFLAGS -rdynamic"
> AC_TRY_LINK([], [], [RDYNAMIC=-rdynamic], [RDYNAMIC=])
> AC_SUBST(RDYNAMIC)
Is this a problem? For one thing, usually dejagnu reports gcc warnings
as fatal; the test would fail if the option generated a warning. For
another, the option should be used unless it causes gcc to fail;
using it even when GCC doesn't support it should be harmless.
--
Daniel Jacobowitz
CodeSourcery, LLC
next prev parent reply other threads:[~2005-12-30 2:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-29 5:38 Jie Zhang
2005-12-30 2:40 ` Daniel Jacobowitz [this message]
2005-12-30 6:31 ` Jie Zhang
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=20051230024019.GB26004@nevyn.them.org \
--to=drow@false.org \
--cc=gdb@sources.redhat.com \
--cc=jzhang918@gmail.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).