This is the mail archive of the
gdb-patches@sources.redhat.com
mailing list for the GDB project.
Re: cross compiler host vs build
- From: Felix Lee <felix dot 1 at canids dot net>
- To: dan clark <dlc at ncube dot com>
- Cc: gdb-patches at sources dot redhat dot com
- Date: Wed, 28 Jan 2004 19:45:07 -0800
- Subject: Re: cross compiler host vs build
- References: <Pine.LNX.4.44.0401281659260.12228-100000@atom.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.
--