From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 24722 invoked by alias); 15 Jan 2008 18:42:07 -0000 Received: (qmail 24712 invoked by uid 22791); 15 Jan 2008 18:42:06 -0000 X-Spam-Check-By: sourceware.org Received: from smtp-out.google.com (HELO smtp-out.google.com) (216.239.33.17) by sourceware.org (qpsmtpd/0.31) with ESMTP; Tue, 15 Jan 2008 18:41:46 +0000 Received: from zps38.corp.google.com (zps38.corp.google.com [172.25.146.38]) by smtp-out.google.com with ESMTP id m0FIfcjq015346 for ; Tue, 15 Jan 2008 18:41:39 GMT Received: from wa-out-1112.google.com (wahk40.prod.google.com [10.114.237.40]) by zps38.corp.google.com with ESMTP id m0FIdsaV017852 for ; Tue, 15 Jan 2008 10:41:37 -0800 Received: by wa-out-1112.google.com with SMTP id k40so5777114wah.25 for ; Tue, 15 Jan 2008 10:41:37 -0800 (PST) Received: by 10.115.58.1 with SMTP id l1mr2553093wak.110.1200422497582; Tue, 15 Jan 2008 10:41:37 -0800 (PST) Received: by 10.115.107.7 with HTTP; Tue, 15 Jan 2008 10:41:37 -0800 (PST) Message-ID: Date: Tue, 15 Jan 2008 18:42:00 -0000 From: "Doug Evans" To: "Jim Blandy" Subject: Re: gdbserver + libiberty? Cc: gdb@sourceware.org In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <20080115172615.232D61C7245@localhost> X-IsSubscribed: yes Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org X-SW-Source: 2008-01/txt/msg00111.txt.bz2 On Jan 15, 2008 10:07 AM, Jim Blandy wrote: > > dje at google.com (Doug Evans) writes: > > Hi. Is there any reason to not link gdbserver with libiberty? > > I'm working on a patch where that would be useful. > > gdbserver would need to be linked with a libiberty compiled for the > target, obviously. This part I'm not clear on. I found this in gdb/configure.ac: # We only build gdbserver automatically in a native configuration. if test "$gdb_native" = "yes"; then AC_MSG_CHECKING(whether gdbserver is supported on this host) if test "x$build_gdbserver" = xyes; then AC_MSG_RESULT(yes) AC_CONFIG_SUBDIRS(gdbserver) else AC_MSG_RESULT(no) fi fi I couldn't find any docs on building gdbserver for cross targets (i.e --host != --target), got any pointers? It's only useful for targets that otherwise can be build natively (AIUIp. Would gdbserver ever be built with CC_FOR_TARGET whereas gdb got built with CC? I can't find any code to handle this in gdb or the top level configury. And if not would gdbserver ever need a different libiberty than the one gdb is linked with?