Setup.exe build woes

Charles Wilson cygwin@cwilson.fastmail.fm
Tue May 24 13:52:00 GMT 2011


On 5/24/2011 5:33 AM, Corinna Vinschen wrote:
> On May 24 11:22, Corinna Vinschen wrote:
>> Why on earth does the configury pull in files from /usr/lib instead of
>> from /usr/lib/mingw?
> 
> I just found that this isn't configure, but libtool.  Adding an early
> "-L/usr/lib/mingw" fixes the problem, but where is the right place to
> add it?

Remember, the whole problem with gcc-3 -mno-cygwin is it can "leak" the
/usr/lib stuff into the mingw configuration.  Now, I know setup.exe
*used* to be buildable with gcc-3 without leaks, so what changed?

Probably this:
http://cygwin.com/ml/cygwin-announce/2011-04/msg00015.html

I didn't test the configuration where:
  -- you have the "new" gcc-mingw-* addon packages
  -- but you don't have the cross-compiled versions of the
     mingw libraries (zlib, bzip2, lzma, gpg-error, gcrypt)
  -- and you may or may not have "fixed" the (now-dangling)
     symlinks in /usr/i686-pc-mingw32/*

Now, that *third* point is a reference to this statement, in the
announcment above:
The second unfortunate aspect of this is it actually *breaks*
   "gcc-3 -mno-cygwin" !!!

See the announcement for 'CHOICE ONE' and 'CHOICE TWO' on how to fix.


Choice two recommends installing the new packages and the cross compiler
packages from cygutils.  Once you've done this, then you should be able
to build setup.exe using gcc-3 -mno-cygwin; that I HAVE tested.

I didn't check building setup.exe when CHOICE ONE (or neither)
mitigation strategy was used -- I only tested helloworld in those cases.


FYI, I have new versions of all of the packages at
cygutils.fruitbat.org, ready to upload to sourceware.com on the
scheduled date of June 1.  Again, see the announcement above for the
reason behind the scheduled delay between the two releases.

--
Chuck



More information about the Cygwin-apps mailing list