Christopher Faylor wrote:
How about figuring out what the "for some reason" is that makes sed 4.1.5
(theoretically) fail?
The thread regarding sed 1.4.5 and libtool:
http://www.cygwin.com/ml/cygwin/2006-02/msg00846.html
Wouldn't it be best to first return to sed 4.1.4 before debugging why
upgrading to sed 4.1.5 is problematic? It's left Cygwin installs in a
broken state for C++ compiles since February.
I can look into the problem with sed 4.1.5 as well, but I'd like to see
Cygwin stay in a working state as much as possible.
--
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/