11-csw-cygwin-wrapper-with-no-deplibs.patch

[Charles Wilson]

Sometimes, a wrapper script is generated for an executable that, itself, 
does not link against an uninstalled library.  It appears that this can 
happen if you are building a project where
   (1) there is a library
   (2) there is an executable that does not, itself, link against that 
library

In this case, notinst_deplibs is empty, and when the wrapper script is 
loaded by libtool during ./libtool mode=install, there is a check for 
"is notinst_deplibs empty".  In this case, it is, so libtool reports an 
error.

I don't think it is wrong to have a wrapper script for an exe that 
*technically* doesn't need it.  But instead of checking for 
notinst_deplib nonempty as a proxy for "did wrapper script get sourced 
into my environment properly" a different var should be used.

For more info, see

http://www.cygwin.com/ml/cygwin/2004-10/msg01321.html

and

http://www.cygwin.com/ml/cygwin/2004-10/msg01347.html

Attached patch (by Peter Ekberg) has no regressions on cygwin.

--
Chuck
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: 11-csw-cygwin-wrapper-with-no-deplibs.changelog
URL: <http://cygwin.com/pipermail/cygwin/attachments/20041030/19912659/attachment.ksh>
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: 11-csw-cygwin-wrapper-with-no-deplibs.patch
URL: <http://cygwin.com/pipermail/cygwin/attachments/20041030/19912659/attachment-0001.ksh>
-------------- next part --------------
--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/