Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Pedro Alves <palves@redhat.com>
To: Yao Qi <yao@codesourcery.com>
Cc: Pedro Alves <palves@redhat.com>,
	Mircea Gherzan <mircea.gherzan@intel.com>,
	       tromey@redhat.com, gdb-patches@sourceware.org
Subject: Re: [PATCH v3] gdbserver: fix the standalone build
Date: Mon, 01 Jul 2013 15:39:00 -0000	[thread overview]
Message-ID: <51D1A293.6000901@redhat.com> (raw)
In-Reply-To: <51CE4252.7050305@codesourcery.com>

On 06/29/2013 03:11 AM, Yao Qi wrote:
> On 06/28/2013 08:22 PM, Pedro Alves wrote:
>> Doesn't GDB, and whatever other users of create-version.h, need the
>> same treatment first?
> 
> In GDB, the 'target_alias' and 'host_alias' can't be empty, and 
> create-version.sh only has two users, GDB and GDBserver.
> 
> GDB is configured from the top level.  On the top level, the FOO_alias 
> is set to @FOO_noncanonical@ (in Makefile.tpl).  The 
> 'target_noncanonical' is similar to 'version_target' we computed in 
> gdbserver/configure.ac.  See config/acx.m4,

...

> and macro ACX_NONCANONICAL_TARGET is invoked in configure.ac.

Hmm, gdb/testsuite/configure.ac is also using that, added here:

 http://www.sourceware.org/ml/gdb-patches/2006-06/msg00330.html

Sounds like we should be making gdbserver use that too, instead
of reinventing our own...

> 
> the gdb/configure is invoked by passing "--build=${build_alias} 
> --host=${host_alias} --target=${target_alias}" from the top level (see 
> rule configure-gdb in Makefile.in).

-- 
Pedro Alves


  reply	other threads:[~2013-07-01 15:39 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-28 12:05 Mircea Gherzan
2013-06-28 12:18 ` Pedro Alves
2013-06-28 12:18 ` Yao Qi
2013-06-28 12:43   ` Pedro Alves
2013-06-29  3:11     ` Yao Qi
2013-07-01 15:39       ` Pedro Alves [this message]
2013-07-03 15:04         ` Yao Qi
2013-07-03 15:11           ` Yao Qi
2013-07-03 15:19             ` Pedro Alves
2013-07-04  1:27               ` Yao Qi

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=51D1A293.6000901@redhat.com \
    --to=palves@redhat.com \
    --cc=gdb-patches@sourceware.org \
    --cc=mircea.gherzan@intel.com \
    --cc=tromey@redhat.com \
    --cc=yao@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