On Sun, 4 Oct 1998, Chrissy Lloyd wrote:

> The install document of both scsh and squid, which I am trying to compile tell
> me to just run 
> 
> ../configure     for scsh
> and
> ../configure --prefix=/usr/local/squid     for squid
> 
> They give
> 
> configure: error: missing argument to --
> and
> eval: =--prefix=/usr/local/squid: not found
> configure: error: missing argument to --

If that's not a typo--you want to be in the directory that
"configure" is in, and then type "./configure", not "../configure".
The reason you don't just type "configure" is that the current
directory isn't in your path, which is as it should be (long story).

Are you familiar with the package system? There are packages for
both scsh and squid. Take a look at
<ftp://ftp.netbsd.org/pub/NetBSD/packages/pkgsrc/README>. What's not
clear from the readme is that you are supposed to be able to build
-current packages with a 1.3.2 tree, although that hasn't been
extensively field tested. To do that, the first package you install
should be "pkgtools/pkg_install". Once you get past that, it's way
better than doing it the hard way, you'll see. :)

For example, I just typed ``cd shells/scsh ; make configure''. That
caused scsh-0.5.1.tag.gz to download, applied numerous patches that
someone else probably worked hard on, and then ran configure. I see
from this that the supplied configure script is OK.

There's nothing wrong with what you're doing, of course. Very often,
source sets will compile out of the box for NetBSD. It promises to be
a learning experience for you, either way. Let us know how it goes.