[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: the gnustep wreckage. Part 2: ProjectCenter

From: Riccardo
Subject: Re: the gnustep wreckage. Part 2: ProjectCenter
Date: Sat, 20 Nov 2004 16:50:45 +0100

hey jer.

On Friday, November 19, 2004, at 11:02 PM, Jeremy Tregunna wrote:

I'm only going to address this one point, directly, and make a sweeping comment regarding your other problems.

Firstly, make generally appears in /usr/bin true, however, on most systems /usr/bin/make is not GNU make, which is what GNUstep needs. It may be called 'gmake' and live in /usr/local/bin, /foo/bar or whatever. One should never assume a given program is available on every system.

This is what I meant with this comment. SOrry if it has been mistaken.

PC currently writes in your project /usr/pkg/bin/gmake for example

if I get that file though CVS on linux, I don't need that but /usr/bin/make just to run this project, if now I commit, it gets uselessly changed in CVS (besides being boring, since this change currently requires a restart of PC...)

I gave a fast sweep of bugs I can't currently explain or pin down. They are reproducible but "only on my box". I tossed them here and it seems indeed that other people had similar problems but they never spoke up! If I had something semi-scientifical I would but file a bug report. If I had a patch I would put it on savannah too, as I did other times with problems I could solve myself and for which I found a general solution.

For example I found out which lines cause a problem in gdnc on NetBSD 1.6 after painful testing and debugging. This enabled RFM to further pinpoint the problem. But a general solution that works and doesn't break other code is something more difficult to get.

I know that just reporting problems is not "enough" but it is something, at least people are aware of it. It is the first step. Others had problems like me but they didn't complain...


reply via email to

[Prev in Thread] Current Thread [Next in Thread]