Dave Korn wrote:
> Because I do not agree with your suggestion.
You don't agree that this is the cygwin list, not the mingw list?
Some people are trying to solve an issue with cygwin's build of make by
discussing possible solutions. Those who have nothing to contribute to
this effort would
John W. Eaton wrote:
I mean, isn't free software all about getting something for nothing,
then complaining about it and expecting others to do yet more gratis
work for you?
Free software is about collaboration of a community consisting of
developers, users, documentation authors, testers, tran
Dave Korn wrote:
Every single day for the past month, we have had at least
seventy-four[*] identical duplicate redundant reports of this...
Have you considered that there just might be a significant message hidden
in this from your user community? As somebody who was involved in one of
these
Hi Corinna,
You wrote:
So, since millions of users have DOS and Mac lineending files, every
system in the world has to support them?
I'm not suggesting that any system "has to" do anything, as the author or
funder of a system you can decide what you want it to do. I'm trying to
persuade you t
Corinna Vinschen wrote:
[JA wrote:]
Thank you very much for this fix. It will make life easier for all of
us who struggle with a mix of native and Cygwin tools. It is very much
appreciated that as far as line endings are concerned the attitude
taken by Cygwin developers is not "use POSIX line en
Hi Corinna,
You wrote:
I've updated the version of sed to 4.1.5-2.
It reverts the default behaviour of sed back to treating CR/LF as
lineendings, in contrast to 4.1.5-1, which only treated the trailing LF
as lineending and the preceeding CR as the last character on the line.
Thank you very m
Christopher Faylor wrote:
I guess that means there is nothing more to discuss.
Agreed, except for the following.
On Mon, Jul 24, 2006 at 12:53:19PM -0700, Joachim Achtzehnter wrote:
Christopher Faylor wrote:
Well, you *could* expect a fix if you provided enough details.
Understood. The
Christopher Faylor wrote:
Well, you *could* expect a fix if you provided enough details.
Understood. The question is, can there still be value in reporting that a
program crashes, even with minimal but potentially still useful
information? I'm just asking and am genuinely interested in heari
Dave Korn wrote:
Which begs the question: given that you were working on such a large and
complex makefile system, and given that it had non-POSIX paths in a makefile,
and given that it wasn't broke and didn't need fixing ...
... why on EARTH did you deliberately go and upgrade to a new versio
Hi all,
Christopher Faylor wrote:
On Fri, Jul 21, 2006 at 06:03:43PM -0700, Joachim Achtzehnter wrote:
There was also some difference in newline handling which required another
set of sed changes, arghh!
Well with detailed bug reports like this and the previous "make provides an
err
mwoehlke wrote:
Michael Hirsch wrote:
Here is a sample Makefile that breaks with Gnu Make 3.81-1 under
Cygwin, but works fine with Gnu Make 3.80-1.
...
Was this a deliberate break with backwards compatibility? It means
that every single reference to a windows path needs to be wrapped in
cygpat
After updating my Cygwin installation make crashes with the following error
when building a very complex project:
4 [sig] make 1976 C:\cygwin\bin\make.exe: *** fatal error -
C:\cygwin\bin\make.exe: *** called with threadlist_ix -1
This is with make version 3.81-1. After downgrading to 3.
12 matches
Mail list logo
