Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Joel Brobecker <brobecker@adacore.com>
To: Nathan Sidwell <nathan@codesourcery.com>
Cc: gdb-patches@sourceware.org
Subject: Re: x86-64 gdbserver config
Date: Mon, 02 Nov 2009 23:08:00 -0000	[thread overview]
Message-ID: <20091102230840.GC4557@adacore.com> (raw)
In-Reply-To: <4AEED5B3.7020107@codesourcery.com>

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


  reply	other threads:[~2009-11-02 23:08 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-02 12:51 Nathan Sidwell
2009-11-02 23:08 ` Joel Brobecker [this message]
2009-11-03  2:37   ` Daniel Jacobowitz
2009-11-03  3:39     ` Joel Brobecker
2009-11-03  3:55 ` Daniel Jacobowitz

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=20091102230840.GC4557@adacore.com \
    --to=brobecker@adacore.com \
    --cc=gdb-patches@sourceware.org \
    --cc=nathan@codesourcery.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