This is the mail archive of the
mailing list for the Cygwin project.
RE: libwin32-perl-0.191 (ready for upload and testing)
- From: "Rafael Kitover" <rkitover at hotmail dot com>
- To: "'Gerrit P. Haase'" <gp at familiehaase dot de>,"'Gerrit @ cygwin-apps'" <cygwin-apps at cygwin dot com>
- Date: Tue, 30 Dec 2003 15:27:33 -0800
- Subject: RE: libwin32-perl-0.191 (ready for upload and testing)
Thanks so much for testing my package! What a mess :)
I'll take care of these issues:
* empty /etc/postinstall (also package should probably not list
directories unless they are actually created).
* change install path to:
usr/lib/perl5/site_perl/5.8.2/... and remove unnecessary files that get
* remove binaries and Makefiles from patch (except for new binaries,
like .ico, .bmp and such.)
* As soon as I figure out how to sanely do multi source -> one package
bundling and patching, I'll also split out Win32::GUI and the patch for
it. I sent a patch to the win32-gui-hackers list as well.
* fix "conf" in build script
* check the hangup with CYGWIN=case:strict or unset it in the hint file
>From: Gerrit P. Haase [mailto:email@example.com]
>Sent: Tuesday, December 30, 2003 1:19 PM
>To: Gerrit @ cygwin-apps
>Cc: Rafael Kitover
>Subject: Re: libwin32-perl-0.191 (ready for upload and testing)
>>> 4. The build option the second time runs until this error stops the
>>> gcc -c -DPERL_USE_SAFE_PUTENV -fno-strict-aliasing -pipe
>>> -DUSEIMPORTLIB -O2 -DVERSION=\"0.09\" -DXS_VERSION=\"0.09\"
>>> "-I/usr/lib/perl5/5.8.2/cygwin-thread-multi-64int/CORE" Net.c
>>> Net.xs:9:22: lmUseFlg.h: No such file or directory
>>> Net.xs:10:22: lmAccess.h: No such file or directory
>>> Net.xs:11:22: lmAPIBuf.h: No such file or directory
>>> Net.xs:15:22: lmServer.h: No such file or directory
>>> Net.xs: In function `allocUserInfoX':
>>> Net.xs:555: error: `USER_INFO_3' undeclared (first use in this
>>> [...more errors...]
>> Unless you use CYGWIN=check_case:strict in your environment this
>> to work:
>Oops, the patch isn't needed, the only reason it didn't work was the
>strict case checking in my environment.
>This should be mentioned in the README (if not already done). Hmm,
>maybe I should actually read the README, but hey, there is no README
>in the source package before you start to configure and build...
>[...going to read the README...]
>After patching the source and reading the README I found that it isn't
>Maybe it is possible to set the case checking dynamically from the