Re: Fucked up gnustep-make

[Richard Frith-Macdonald]

On 13 Feb 2007, at 20:24, Chris Vetter wrote:

> Hi,
>
>    gs_cv_make_version=`make --version | head -1 | sed -e 's/^[^0-9] 
> *//'`
>
>   :0> make --version
>   make: illegal option -- -
>   usage: make [-BPSXeiknqrstv] [-C directory] [-D variable]
>           [-d flags] [-E variable] [-f makefile] [-I directory]
>           [-j max_jobs] [-m directory] [-V variable]
>           [variable=value] [target ...]
>
>
> NOT everyone is using LinSux.
>
> And yes, I know SVN isn't supposed to be stable.
> But that doesn't mean a developer shouldn't use some care when  
> uploading new code.
>
> Stunts like that doesn't help GNUstep.

I suspect that comments like that do a lot to put developers off  
working on GNUstep, doing immeasurably more harm than breakage of  
code in svn-trunk.
The implied notion that a change must be tested on all platforms  
before submission to svn-trunk in order to qualify as demonstrating  
'some care' is frankly ridiculous and insulting.

The best way to report a bug is politely, and with helpful detail  
about where it actually occurred and on what system it was running etc..

Now, anyone using gnustep-make must be using gnu-make, which supports  
the --version flag.  So the question is why your system barfed?  It  
must have been running some other make somehow.

I'm not familiar with the most recent changes to gnustep-make, so I  
don't actually know where your problem is coming from.  Is this the  
configure script?  If so, I guess the configure script needs to check  
that it has gnu-make before trying to use it.
Any chance you could submit a patch to fix it?