Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 25 Sep 2008 18:52:28 +0200
From:      Mel <fbsd.questions@rachie.is-a-geek.net>
To:        freebsd-questions@freebsd.org
Cc:        Andrew Falanga <af300wsm@gmail.com>
Subject:   Re: Can't build all in /usr/src/crypto/openssh
Message-ID:  <200809251852.29479.fbsd.questions@rachie.is-a-geek.net>
In-Reply-To: <340a29540809250933g1f76d098y87806ea439c8bfad@mail.gmail.com>
References:  <340a29540809250833u27f7c3d6o5f3bcfe9932056d0@mail.gmail.com> <200809251749.04425.fbsd.questions@rachie.is-a-geek.net> <340a29540809250933g1f76d098y87806ea439c8bfad@mail.gmail.com>

next in thread | previous in thread | raw e-mail | index | archive | help
On Thursday 25 September 2008 18:33:52 Andrew Falanga wrote:
> On Thu, Sep 25, 2008 at 9:49 AM, Mel
>
> <fbsd.questions@rachie.is-a-geek.net> wrote:
> > On Thursday 25 September 2008 17:33:56 Andrew Falanga wrote:
> >> Hi,
> >>
> >> I've just updated my sources for 6.2-RELEASE.  It took me from p11 to
> >> p12.  The changes were quite minor.  Only changes were to UPDATING
> >> (obviously), channels.c in the openssh directory and a newvers.sh file
> >> in /usr/src/conf.  So, instead of rebuilding world, since the UPDATING
> >> notes say that the changes only affect sshd, I'm following the
> >> instructions in the handbook for section, "23.4.14.1. Do I need to
> >> re-make the world for every change?."  The instructions state, "... go
> >> to the appropriate sub-directories and make all install."  However,
> >> when I do this I get, "make: don't know how to make all.  Stop."
> >>
> >> So, what do I tell it to do?  Especially, considering that the
> >> Makefile.in in this directory (/usr/src/crypto/openssh), appears to
> >> have a default rule of "all."
> >
> > Openssh/ssl is distributed accross the source tree. crypto/openssh only
> > contains the imported sources, not the files that FreeBSD actually uses
> > to build them.
> > cd /usr/src/secure && make all install should work for you (but will also
> > rebuild openssl and sendmail).
> Because this will rebuild OpenSSL, would it be advisable to rebuild
> the world or is this sufficient?

Bad choice of words on my part. It won't rebuild openssl, if you still 
have /usr/obj/usr/src/* from last time. But it will go through the motions to 
see if stuff needs to be rebuilt. It will only rebuild libssh and anything 
that uses libssh:
# find . -name 'Makefile' -exec grep channels.c {} \+
./secure/lib/libssh/Makefile:   canohost.c channels.c cipher.c cipher-acss.c 
cipher-aes.c \

# find . -name 'Makefile' -exec grep -l 'DPADD.*LIBSSH' {} \+
./lib/libpam/modules/pam_ssh/Makefile
./secure/libexec/sftp-server/Makefile
./secure/libexec/ssh-keysign/Makefile
./secure/usr.bin/scp/Makefile
./secure/usr.bin/sftp/Makefile
./secure/usr.bin/ssh/Makefile
./secure/usr.bin/ssh-add/Makefile
./secure/usr.bin/ssh-agent/Makefile
./secure/usr.bin/ssh-keygen/Makefile
./secure/usr.bin/ssh-keyscan/Makefile
./secure/usr.sbin/sshd/Makefile

The pam module is the only one outside secure that depends on libssh.

-- 
Mel

Problem with today's modular software: they start with the modules
    and never get to the software part.



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200809251852.29479.fbsd.questions>