On Sat, 4 Oct 2003, Jeremy C. Reed wrote:

> I am using SH as "ksh -p", because this version of BSD/OS comes by default
> with an ENV set to ~/.shellrc. And it is sourced each time ksh is run, but
> it has syntax errors, because it uses bashisms based on $SHELL variable
> which is still defined as bash.
>
> The ksh also provides the "type" command too.

Ignore this. I can't use -p nor type even with ksh.
type: not found
type: not found
env: -p: No such file or directory

I will go back to using TYPE as which. Or maybe bmake should be built to
use ksh instead of sh?

Now using SH as ksh I get

/usr/pkgsrc/devel/libtool-base/work/.buildlink/bin/.gen-transform: syntax
error: `(' unexpected

 ./ltmain.sh i386--bsdos
./ltconfig: syntax error: `(' unexpected

/usr/pkgsrc/devel/libtool-base/work/.buildlink/bin/g++: syntax error: `('
unexpected

/bin/ksh ./libtool --mode=compile cc -DHAVE_CONFIG_H -I. -I. -I.
-I/usr/pkg/in
clude  -O2 -I/usr/pkg/include -c ltdl.c
./libtool: syntax error: `(' unexpected

./libtool: syntax error: `(' unexpected

... and many others.

I manually "unset ENV" before running bmake and all is well.

Is there a way in pkgsrc to unset ENV?

   Jeremy C. Reed
   http://bsd.reedmedia.net/