From owner-freebsd-stable@FreeBSD.ORG Mon Mar 15 02:50:35 2004 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 529F616A4CE for ; Mon, 15 Mar 2004 02:50:35 -0800 (PST) Received: from tigra.ip.net.ua (tigra.ip.net.ua [82.193.96.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id C807A43D4C for ; Mon, 15 Mar 2004 02:50:33 -0800 (PST) (envelope-from ru@ip.net.ua) Received: from heffalump.ip.net.ua (heffalump.ip.net.ua [82.193.96.213]) by tigra.ip.net.ua (8.12.10/8.12.9) with ESMTP id i2FAseee013861 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 15 Mar 2004 12:54:44 +0200 (EET) (envelope-from ru@ip.net.ua) Received: (from ru@localhost) by heffalump.ip.net.ua (8.12.11/8.12.11) id i2FAoSPK044905; Mon, 15 Mar 2004 12:50:28 +0200 (EET) (envelope-from ru) Date: Mon, 15 Mar 2004 12:50:28 +0200 From: Ruslan Ermilov To: Dave Hayes Message-ID: <20040315105028.GB44718@ip.net.ua> References: <200403151036.i2FAaNuZ097037@hokkshideh2.jetcafe.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="9zSXsLTf0vkW971A" Content-Disposition: inline In-Reply-To: <200403151036.i2FAaNuZ097037@hokkshideh2.jetcafe.org> User-Agent: Mutt/1.5.6i X-Spam-Checker-Version: SpamAssassin 2.55 (1.174.2.19-2003-05-19-exp) cc: Jarkko Santala cc: stable@freebsd.org Subject: Re: 4.8p16 buildworld fails with NO_OPENSSL X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 15 Mar 2004 10:50:35 -0000 --9zSXsLTf0vkW971A Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Mar 15, 2004 at 02:36:23AM -0800, Dave Hayes wrote: > Ruslan Ermilov writes: > > But in the above, you attempted to compile secure/usr.bin/telnet, > > not usr.bin/telnet. If you still see a breakage with the latter, > > come back to me. >=20 > Actually, if you check my original message, I did both. To be anally=20 > clear: I attempted a compile of usr.bin/telnet which was documented > in my original message. >=20 > I'll paste it again: >=20 > # cd /usr/src/usr.bin/telnet > # make > Warning: Object directory not changed from original /usr/src/usr.bin/teln= et > cc -O2 -pipe -DKLUDGELINEMODE -DUSE_TERMIO -DENV_HACK -DOPIE =20 > -I/usr/src/usr.bin/telnet/../../lib -I/usr/src/usr.bin/telnet/../../lib/l= ibteln > et/ -DINET6 -DIPSEC -o telnet commands.o main.o network.o ring.o sys_= bsd.o=20 > telnet.o terminal.o utilities.o -ltermcap /usr/src/usr.bin/telnet/../../l= ib/lib > telnet/libtelnet.a -lipsec > cc: /usr/src/usr.bin/telnet/../../lib/libtelnet/libtelnet.a: No such file= or=20 > directory > *** Error code 1 >=20 > As an aside: are people not using "NO_OPENSSL=3Dtrue"? I've seen more > than a few bug incidents with this being defined. Is there some > data I'm missing on this subject?=20 >=20 Generally, yes. The mixture of crypto-related knobs and a number of different telnet's in RELENG_4 is so complex, so that handling each individual combination became a nightmare, so it was reengineered in 5.x -- we now have a single telnet entry point in the source tree, that handles all cases properly (well, it should). Building RELENG_4 (and RELENG_4_8) worlds with only NO_OPENSSL will not build the non-crypto version -- usr.bin/Makefile will not descend into it. If you don't need crypto, just define NOCRYPT and rebuild world (it also implies NO_OPENSSL). It will have some side effect of not building bdes(1), compared to only specifying NO_OPENSSL, but do you really need it? If not, replace NO_OPENSSL with NOCRYPT, and get on with life. Cheers, --=20 Ruslan Ermilov FreeBSD committer ru@FreeBSD.org --9zSXsLTf0vkW971A Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (FreeBSD) iD8DBQFAVYp0Ukv4P6juNwoRApIOAJ4slIn6VQsdqkaiCNZLqqhw/ZrJYQCfTJ5C ctmMsPkvLBGxa+Ge0Sw8mRQ= =d4iY -----END PGP SIGNATURE----- --9zSXsLTf0vkW971A--