On Mon, 19 Nov 2007, Neil Williams wrote:
> Santiago Vila wrote:
> > Would it work if both --build and --host are always used and only CC
> > is redefined ifneq ($(DEB_HOST_GNU_TYPE),$(DEB_BUILD_GNU_TYPE)) ?
>
> No. That would cause the native build to have --host defined which means
> that even native builds would look for a cross compiler.
So what? It means on i386 the compiler to use would be
i486-linux-gnu-gcc-4.1, which is the same as the native compiler.
What harm would do that?
> See the autotools-dev README.Debian - --build is needed for both, --host
> must only be specified when cross building.
This is what README.Debian says:
> BTW, autoconf 2.52+ should enter cross-compiling mode if --host is
> specified. It will build in cross-compiling mode even if build and
> host type are the same (this information comes directly from autoconf
> upstream). This goes against what is in the docs of autoconf 2.59,
> and it may be a bug somewhere.
So, if it is a bug in autoconf, let us fix it in autoconf.
In either case, I fail to see the difference between a "cross-compilation"
to the native architecture and a native compilation.
BTW: The CC setting comes from policy 10.1, Binaries:
For the C programming language, this means the following compilation
parameters should be used:
CC = gcc
CFLAGS = -O2 -g -Wall # sane warning options vary between programs
LDFLAGS = # none
INSTALL = install -s # (or use strip on the files in debian/tmp)
Should we drop such CC = gcc from policy? It think it is useful because
it allows Debian packages to be built on foreign OSes with gcc automatically.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
