From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 19874 invoked by alias); 2 Nov 2009 23:08:53 -0000 Received: (qmail 19863 invoked by uid 22791); 2 Nov 2009 23:08:52 -0000 X-SWARE-Spam-Status: No, hits=-2.5 required=5.0 tests=AWL,BAYES_00 X-Spam-Check-By: sourceware.org Received: from rock.gnat.com (HELO rock.gnat.com) (205.232.38.15) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Mon, 02 Nov 2009 23:08:48 +0000 Received: from localhost (localhost.localdomain [127.0.0.1]) by filtered-rock.gnat.com (Postfix) with ESMTP id DF6052BAC99; Mon, 2 Nov 2009 18:08:46 -0500 (EST) Received: from rock.gnat.com ([127.0.0.1]) by localhost (rock.gnat.com [127.0.0.1]) (amavisd-new, port 10024) with LMTP id AKXs7UD0I2ah; Mon, 2 Nov 2009 18:08:46 -0500 (EST) Received: from joel.gnat.com (localhost.localdomain [127.0.0.1]) by rock.gnat.com (Postfix) with ESMTP id 59C6B2BAC63; Mon, 2 Nov 2009 18:08:46 -0500 (EST) Received: by joel.gnat.com (Postfix, from userid 1000) id CFB1BF5905; Mon, 2 Nov 2009 15:08:40 -0800 (PST) Date: Mon, 02 Nov 2009 23:08:00 -0000 From: Joel Brobecker To: Nathan Sidwell Cc: gdb-patches@sourceware.org Subject: Re: x86-64 gdbserver config Message-ID: <20091102230840.GC4557@adacore.com> References: <4AEED5B3.7020107@codesourcery.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4AEED5B3.7020107@codesourcery.com> User-Agent: Mutt/1.5.18 (2008-05-17) Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org X-SW-Source: 2009-11/txt/msg00035.txt.bz2 Hello Nathan, > This patch allows building an x86-64 gdbserver for a multilibbed > i686-pc-linux-gnu target. One cannot tell from the target triplet that > x86-64 source files are needed -- one must invoke the compiler and > examine the __x86_64__ #define. For instance, the CC_FOR_TARGET may be > 'my-gcc -m64'. I am trying to understand the situation under which this patch would be used. Is it when using a cross compiler or can it be when using a native compiler? Or both? I'm a little confused, because I was under the impression that the target was either specified using configure --target=, or deduced using "config.guess". Either way, I would have thought that the user is responsible for configuring gdbserver as needed. This is something that we do already when building GDB for sparc64. However, I just noticed today that on pc/solaris, config.guess actually returns different values dependending on whether our GCC was configured as i386-sun-solaris2.8 or x86_64-sun-solaris2.8... I don't think the same sort of trick is really applicable to GNU/Linux, though. Anyway, just trying to think aloud for now... -- Joel