This is the mail archive of the
cygwin-apps
mailing list for the Cygwin project.
Re: packaging & AMD64
- From: Corinna Vinschen <corinna-cygwin at cygwin dot com>
- To: "[ML] CygWin-Apps" <cygwin-apps at cygwin dot com>
- Date: Mon, 3 Oct 2005 11:24:45 +0200
- Subject: Re: packaging & AMD64
- References: <433D6894.4080609@lapo.it>
- Reply-to: cygwin-apps at cygwin dot com
On Sep 30 18:32, Lapo Luchini wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> I just noticed that "configure" doesn't recognize (as in: "cannot
> guess build type; you must specify one") my actual host, which runs
> WindowsXP x64.
>
> Updating config.guess in those pakcages (e.g. rsync) that still have a
> very old one changes from "cannot guess" to "x86_64-unknown-cygwin",
> which doesn't seem very right anyway: why "unknown" instead of "pc"?
> Moreover doesn't seems correct to have host system type recognized
> that way also: I don't want to produce packages that rely on the
> prefence of an AMD64 processor, while just updating the config guess
> let configure guess that "host" system type is "x86_64-unknown-cygwin"
> also.
>
> I'm pretty sure that if I specify --build=i686-pc-cygwin should
> compile things just like usual, and I think that it is the right thing
> to do.
> Is that so?
It seems that recognizing the "real" CPU instead of the "virtual" one
inside of a WOW64 system only irritates builds. For 1.5.19, I disabled
recognizing the real 64 bit CPU, prefering the system info given by
WOW64, which pretends to run on i686.
Corinna
--
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Project Co-Leader cygwin AT cygwin DOT com
Red Hat, Inc.