Re: Cygwin patches from Charles

[Charles Wilson]

Bob Friesenhahn wrote:

> A while back (probably in June), Charles Wilson posted some
> significant Cygwin patches to the libtool-patches list which avoid an
> unnecessary re-link when installing under Cygwin and to introduce a
> binary executable wrapper.  I have not had time to get to these.  I am
> afraid that unless these patches are applied, they will become too
> rotten to cleanly apply (if not already).  You seem to have immense
> energy at the moment.  Do you have time to look at these patches?

The largish patch you are concerned about was the wrapperexe patch, 
which was #4 of 4 in the recent spate of patches I [re]sent to the list. 
 It was (cleanly) applied to HEAD yesterday.  I think that means that 
current CVS libtool has all of the functionality needed for cygwin.  I 
do not know about the 1.5 branch, but since that branch appears to be a 
dead duck it doesn't much matter I suppose.

The only extant problem on cygwin that I am aware of is the inability to 
build outside the sourcedir from a freshly bootstrapped CVS checkout -- 
but it's possible that Gary's 34-gary-default-libtoolize-auxdir.patch 
(posted today) fixed that.  I haven't had a chance to try yet.

Oh -- and one other: non-deterministic behavior in the test suite.  On a 
clean build, I'll run the test suite and most tests pass but a few will 
fail.  (e.g. mdemo-static fails, and the next four tests in that "group" 
are skipped).  But then, upon re-running the affected group of tests 
manually, they will often succeed.  This is not a new problem, and 
appears to only occur in the testsuite itself -- I haven't seen any 
similar non-deterministic bootstrapping behavior ("fails, fails, 
works!") in actual packages intended for distribution.  As I said, not a 
showstopper and not a new problem.

--
Chuck