On Tue, 23 Jan 2007, Bruce Korb wrote:
> Hugh Sasse wrote:
>
> > This resulted in two failures (below).
> >
> > (I've not noticed failure output being sent to a file. Is this
> > how you like them reported, or should I be doing something else?)
> (This is fine)
OK, thanks...
>
> > + test invocation_ct = 2 = invocation_ct = 2
> > + ./immediate help version=c
> > + fgrep USAGE:
> > grep: illegal option -- F
> > Usage: grep -hblcnsviw pattern file . . .
>
> Looks like "fgrep" got wrapped with a GNU tools wrapper.
> There is no "fgrep" in GNU, except as a wrapper that
> invokes "grep -F". Obviously, that wrapper snagged the
> Solaris "grep" and it doesn't grok "-F". You need to
> fiddle with your $PATH ordering.
Fixed path ordering but I get the same failures...
Here's my build script now:
<quote>
#!/bin/ksh
export SHELL=/bin/ksh
export CONFIG_SHELL=/bin/ksh
export
PATH=/bin:/usr/bin:/progs/SUNWspro/bin:/usr/ucb:/usr/sbin:/usr/ccs/bin:/etc:/usr/local/bin
VERSION=5.8.8
cd /scratch/hgs/autogen-${VERSION}
gmake clean
./configure && gmake && gmake check;
</quote>
[....]
> > + egrep -v ^# keyword.cfg
> > grep: illegal option -- E
>
> Same issue: there is no GNU "egrep", except as a wrapper
OK, here are quotes from my resulting config.log:
/bin/universe = unknown
PATH: /bin
PATH: /usr/bin
PATH: /progs/SUNWspro/bin
PATH: /usr/ucb
PATH: /usr/sbin
PATH: /usr/ccs/bin
PATH: /etc
PATH: /usr/local/bin
[...]
configure:3827: checking for a sed that does not truncate output
configure:3881: result: /usr/local/bin/sed
configure:3884: checking for grep that handles long lines and -e
configure:3958: result: /usr/local/bin/grep
configure:3963: checking for egrep
configure:4041: result: /usr/local/bin/grep -E
configure:4057: checking for ld used by gcc
configure:4124: result: /usr/local/bin/ld
configure:4133: checking if the linker (/usr/local/bin/ld) is GNU ld
configure:4148: result: yes
So, at present I believe that configure is looking for a grep with tighter
constraints that provided by the solaris tools:
bash-2.05$ which grep
/bin/grep
bash-2.05$ which egrep
/bin/egrep
bash-2.05$
So those being first on the path should have been found first
(right?), but configure wants something that
'handles long lines and -e"
Now, AFAICS your configure.in doesn't contain AC_PROG_EGREP
as per:
http://www.gnu.org/software/autoconf/manual/autoconf-2.57/html_chapter/autoconf_5.html#SEC40
so I'm not entirely clear as to why these are being picked up.
Hugh
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Autogen-users mailing list
Autogen-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/autogen-users
