From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 2389 invoked by alias); 30 Dec 2005 06:31:05 -0000 Received: (qmail 2216 invoked by uid 22791); 30 Dec 2005 06:31:05 -0000 X-Spam-Check-By: sourceware.org Received: from zproxy.gmail.com (HELO zproxy.gmail.com) (64.233.162.203) by sourceware.org (qpsmtpd/0.31) with ESMTP; Fri, 30 Dec 2005 06:31:03 +0000 Received: by zproxy.gmail.com with SMTP id 9so1835090nzo for ; Thu, 29 Dec 2005 22:31:01 -0800 (PST) Received: by 10.36.50.7 with SMTP id x7mr7287238nzx; Thu, 29 Dec 2005 22:31:01 -0800 (PST) Received: from ?192.168.1.108? ( [58.35.242.27]) by mx.gmail.com with ESMTP id j7sm49533nzd.2005.12.29.22.30.55; Thu, 29 Dec 2005 22:31:00 -0800 (PST) Message-ID: <43B4D41D.5000908@gmail.com> Date: Fri, 30 Dec 2005 06:31:00 -0000 From: Jie Zhang User-Agent: Mozilla Thunderbird 1.0.7 (X11/20051010) MIME-Version: 1.0 To: Daniel Jacobowitz CC: gdb@sources.redhat.com Subject: Re: An issue in configure.ac of gdbserver References: <6f48278f0512282138i3c2a193fqdd4cf23182e75d2f@mail.gmail.com> <20051230024019.GB26004@nevyn.them.org> In-Reply-To: <20051230024019.GB26004@nevyn.them.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org X-SW-Source: 2005-12/txt/msg00217.txt.bz2 Daniel Jacobowitz wrote: > 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. > I thought it's also trying to catch the warning. Thanks for explanation. Jie