This is the mail archive of the cygwin-apps mailing list for the Cygwin project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: [PATCH] setup: port to 64-bit, part 1

Hi Cgf,
Hi Yaakov,

On Mar  3 00:46, Yaakov (Cygwin/X) wrote:
> This patch fixes the remaining issues, *except in autoload.c*, for a
> 64bit setup.exe.  Some notes:
> 1) This assumes that 64bit .ini will be named setup64.ini.
> 2) This also assumes that 64bit setup will only install 64bit packages
> (IOW only use setup64.ini, regardless of argv[0])
> 3) The resulting binary is still named setup.exe, but we'll want to
> provide this for download as e.g. setup64.exe.  It would be up to
> whomever (cgf?) to rename this upon uploading.  Alternatively, the
> buildsystem could be patched to change the executable name based on
> $host_cpu.
> 4) I could #ifndef much more legacy support code, but with the recent
> removal of legacy packages from sourceware, are we going to just
> remove all that from setup?
> 5) bootstrap still needs to be reworked to deal with a possible
> --host=x86_64-w64-mingw32.

If Yaakov applied the changes necessary to get the 64 bit setup running
for a start, would it be possible to let upset create a setup64.ini file
for the current cygwin/64bit/release test area?

Given the about 10 Billion packages Yaakov uploaded in the last couple
of days, it gets pretty tiresome to install the 64 bit packages by hand.


Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Maintainer                 cygwin AT cygwin DOT com
Red Hat

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]