Solving the "relink exe's" libtool problem[take4]

Charles Wilson cwilson@ece.gatech.edu
Tue Jan 21 08:41:00 GMT 2003


[dropped automake-patches from the CC: list; this discuession has long 
since ceased involving automake]

This version addresses the two issues raised by Bruce: using the shell 
that is appropriate for the platform, as determined during configure 
(since that is how the libtool variable $SHELL is assigned), and using a 
static string constant instead of dynamically allocating storage -- 
since we know before compile time what the value of the string will be 
(/bin/sh or /bin/bash or whatever).

I really feel like we're in nitpick mode here.  If there are no 
*substantive* objections, can we check THIS version in?  And then clean 
up the additional nitpicks, if any, as additional patches?

The only difference between this patch and the previous one is in the 
main() function, and the patch as a whole has been regenerated against 
current CVS.

--Chuck


-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: libtool-relinkexe4.changelog
URL: <http://cygwin.com/pipermail/cygwin/attachments/20030121/40410ecf/attachment.ksh>
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: libtool-relinkexe4.patch
URL: <http://cygwin.com/pipermail/cygwin/attachments/20030121/40410ecf/attachment-0001.ksh>
-------------- next part --------------
--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/


More information about the Cygwin mailing list