Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Felix Lee <felix.1@canids.net>
To: dan clark <dlc@ncube.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: cross compiler host vs build
Date: Thu, 29 Jan 2004 03:45:00 -0000	[thread overview]
Message-ID: <20040129034507.D5314180D@grayscale.canids> (raw)
In-Reply-To: <Pine.LNX.4.44.0401281659260.12228-100000@atom.ncube.com>  on Wed, 28 Jan 2004 18:00:36 PST from dan clark <dlc@ncube.com>

dan clark <dlc@ncube.com>:
> The configure script in 6.0 checks if the host != target to decide if a
> cross compiler should be used.

no, it doesn't.  is_cross_compiler is a badly named variable.  it
means you're building a cross development gdb, and it doesn't
have anything to do with whether you're using a cross compiler to
build gdb.  (the variable name makes more sense when you have an
integrated gdb/gcc source tree.)

there are different tests elsewhere for build != host.

(note, configure is a file generated by autoconf.  patches should
be made to configure.in.)

I don't really see a reason for the variable is_cross_compiler
to exist.  the comment says
    # Define is_cross_compiler to save on calls to 'test'.
but it's usually used like this
    if test x${is_cross_compiler} != xno ; then
so it's not reducing the number of tests much.  I think directly
testing host = target would be clearer.
--


  reply	other threads:[~2004-01-29  3:45 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-29  2:00 dan clark
2004-01-29  3:45 ` Felix Lee [this message]
2004-01-29 17:00   ` with-headers should be 'build' != 'host' dan clark
2004-01-29 18:12     ` Daniel Jacobowitz
2004-01-29 21:41       ` Ian Lance Taylor
2004-01-29 22:25         ` Felix Lee
2004-01-29 18:41     ` Felix Lee

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=20040129034507.D5314180D@grayscale.canids \
    --to=felix.1@canids.net \
    --cc=dlc@ncube.com \
    --cc=gdb-patches@sources.redhat.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