Christopher Faylor
2012-11-12 19:15:52 UTC
[moving cygwin-specific newlib discussion here]
cygwin-w32api-headers-2.0.999-1.trunk.20121016 header package on
Fedora, and I can build and run Cygwin fine after the change from
yesterday. Do the latest headers from the distro differ?
I initially was using the x86_64 headers from:
mingw64-x86_64-headers-3.0b_svn5373-1.tar.bz2
extracted on Linux.
I had to make a few changes to get that working, which was surprising.
I have switched to mingw64-i686-headers-3.0b_svn5373-1.tar.bz2 but I
haven't checked to see if that meant I could back out my changes. I'd
be surprised if it did.
I thought it would be best to be using the headers that we actually
release rather than whatever someone decided to package for my
development system.
I've ported my configure changes over from the git branch to make it
easier to point to arbitrary windows headers and libraries when
configuring. That allows me to ignore the headers that are installed
for my cross-compiler, which are actually, as it turns out, out-of-date.
I have a perl script now which sets up /usr/local/i686-w64-mingw32 with
the headers and libraries needed to build Cygwin (and hopefully
setup.exe) from the Cygwin distro.
I've attached the script. Except for the last few lines, it should work
nearly anywhere, as long as you have a login account on sourceware.org.
cgf
*I've had to make a number of changes to Cygwin to get it to build with
the latest released version of the mingw64 headers.
What changes? I'm using thethe latest released version of the mingw64 headers.
cygwin-w32api-headers-2.0.999-1.trunk.20121016 header package on
Fedora, and I can build and run Cygwin fine after the change from
yesterday. Do the latest headers from the distro differ?
mingw64-x86_64-headers-3.0b_svn5373-1.tar.bz2
extracted on Linux.
I had to make a few changes to get that working, which was surprising.
I have switched to mingw64-i686-headers-3.0b_svn5373-1.tar.bz2 but I
haven't checked to see if that meant I could back out my changes. I'd
be surprised if it did.
I thought it would be best to be using the headers that we actually
release rather than whatever someone decided to package for my
development system.
I've ported my configure changes over from the git branch to make it
easier to point to arbitrary windows headers and libraries when
configuring. That allows me to ignore the headers that are installed
for my cross-compiler, which are actually, as it turns out, out-of-date.
I have a perl script now which sets up /usr/local/i686-w64-mingw32 with
the headers and libraries needed to build Cygwin (and hopefully
setup.exe) from the Cygwin distro.
I've attached the script. Except for the last few lines, it should work
nearly anywhere, as long as you have a login account on sourceware.org.
cgf