Re: [AD] 4.0.2 release

[Evert Glebbeek <eglebbk@xxxxxxxxxx>]

> > [snip]
> > ...
> > Installing lib/unix/liballeg.a to /home/eglebbk/lib
> > /bin/sh ./misc/mkdirs.sh /home/eglebbk/bin
> > Installing allegro-config to /home/eglebbk/bin
> > grep: illegal option -- q
> > Usage: grep -hblcnsviw pattern file . . .
> 
> That's pretty annoying because the configure machinery uses grep -q all
> over the place. Does an Unix guru know how to work around this problem ?

Not that I feel that I'm being addressed here, but this is what it says in 
the man page:

       -q, --quiet, --silent
              Quiet;  suppress  normal output.  The scanning will
              stop on the first match.  Also see the -s or  --no-
              messages option below.

and

       -s, --no-messages
              Suppress  error  messages  about   nonexistent   or
              unreadable  files.   Portability  note:  unlike GNU
              grep, traditional grep did not conform to  POSIX.2,
              because traditional grep lacked a -q option and its
              -s option behaved like GNU grep's -q option.  Shell
              scripts intended to be portable to traditional grep
              should avoid both -q and  -s  and  should  redirect
              output to /dev/null instead.

so I'm guessing we should change it as suggested above?
Alternatively, we could consider the way the guys that set up the system I 
tested on to be badly broken - which it is in many ways. :-)
-- 
Evert Glebbeek
e-mail: eglebbk@xxxxxxxxxx   ICQ: 48210348
www: http://www.science.uva.nl/~eglebbk/