On Mon, Feb 24, 2003 at 10:32:28AM -0600, Jacques A. Vidrine wrote:
> On Mon, Feb 24, 2003 at 11:17:21AM -0500, Chuck Swiger wrote:
> > >/usr/obj/usr/src/i386/usr/lib/libssh.so: undefined reference to 
> > >`EVP_aes_128_cbc'
> > >/usr/obj/usr/src/i386/usr/lib/libssh.so: undefined reference to 
> > >`EVP_aes_192_cbc'
> > >/usr/obj/usr/src/i386/usr/lib/libssh.so: undefined reference to 
> > >`EVP_aes_256_cbc'
> > >/usr/obj/usr/src/i386/usr/lib/libssh.so: undefined reference to 
> > >`HMAC_CTX_cleanup'
> > >*** Error code 1
> > >Stop in /usr/src/secure/usr.bin/scp.
> > >*** Error code 1
> > >Stop in /usr/src/secure/usr.bin.
> > 
> > I discovered that the build would work fine under /bin/sh, but not under 
> > my normal shell, which is zsh.
> > 
> > It turns out that having a /usr/local/bin/openssl (from a port-build of 
> > openssh-0.9.6g) in the path was causing the problem.  Is a build failure 
> > resulting from an interaction with the user's $PATH regarded as a bug?
> 
> I dunno; I always clean my path before buildworld, but I don't see
> documentation to that effect.  If anyone has an opinion about it,
> Ruslan probably does :-) [cc'd]
> 
src/Makefile sets PATH=/sbin:/bin:/usr/sbin:/usr/bin before passing
buildworld further to src/Makefile.inc1, so I don't see how that
could be a problem.

Similarly for zsh(1): make(1) uses sh(1) internally, and to make it
use another shell, one needs to recompile make(1) with a different
DEFSHELL.  In any case, this feature isn't even in RELENG_4.


Cheers,
-- 
Ruslan Ermilov          Sysadmin and DBA,
[EMAIL PROTECTED]               Sunbay Software AG,
[EMAIL PROTECTED]               FreeBSD committer,
+380.652.512.251        Simferopol, Ukraine

http://www.FreeBSD.org  The Power To Serve
http://www.oracle.com   Enabling The Information Age

Attachment: pgp00000.pgp
Description: PGP signature

Reply via email to