got 'configure', which does not create a Makefile, so what is thenext step? (WAS Re: tru64 patch)
Toni L. Harbaugh-Blackford
harbaugh at nciaxp.ncifcrf.gov
Fri Aug 30 03:58:05 EST 2002
On Thu, 29 Aug 2002, Wendy Palm wrote:
>
> if you ran autoconf, the next step is to run autoheader.
>
> then, you run configure with whatever options you need for your architecture.
> see the INSTALL file.
>
> for my machines, i use-
> ./configure --prefix=$INSTALLDIR \
> --with-pid-dir=$INSTALLDIR/etc \
> --with-ssl-dir=$INSTALLDIR/lib \
> --with-zlib=$INSTALLDIR/lib \
> --with-cflags="-I$INSTALLDIR/include" \
> --with-ldflags="-L$INSTALLDIR/lib" \
> --with-entropy-timeout=600 \
> --with-privsep-path=$INSTALLDIR/var/empty \
> --with-privsep-user=sshd
I did both 'autoconf' and 'autoheader', then I ran 'configure' with my settings.
But no Makefile is generated.
So you are saying that 'configure' *SHOULD* have created the Makefile?
-----------------------------------------------------------------------
Toni Harbaugh-Blackford harbaugh at nciaxp.ncifcrf.gov
AlphaServer 8400 System Administrator
SAIC/NCI Frederick Advanced Biomedical Computing Center
More information about the openssh-unix-dev
mailing list