Hey

If someone has been paying attention on the recent CVS-commits, they've seen
that I committed an 'ltmain.sh' file generated by libtoolize 1.4.3 the other
day, and that I reverted the file back to the previous status today.

The reason for the upgraded file would be an attempt to correct the problems
experienced by the cygwin people.

The reason for the revert, is that all of a sudden ltmain.sh generated a
'libtool' script that used a SED variable that was never set to anything. I
added a check for 'sed' and set SED in the configure script (to the path of
the found sed command) and on my Linux system this works. However, all the
other test systems we autobuild on fail miserably on this. My Solaris 2.7
machine does not at all get the SED variable set in the libtool script even
though I upgraded to autoconf 2.57 and everything.

I guess libtool 1.4.3 requires some specific version of some other tool(s),
but at this point I've decided that I won't go chasing down them. If anyone
knows, I'll be interested, if not, I'll just postpone this operation and take
on these problems another day...

-- 
 Daniel Stenberg -- curl, cURL, Curl, CURL. Groks URLs.
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf