Bug 19547

Summary: 4.0-STABLE / SECURE make world fails on openssh/OPIE
Product: Base System Reporter: chris <chris>
Component: i386Assignee: freebsd-bugs (Nobody) <bugs>
Status: Closed FIXED    
Severity: Affects Only Me    
Priority: Normal    
Version: 4.0-STABLE   
Hardware: Any   
OS: Any   

Description chris 2000-06-27 18:20:00 UTC 
	I cvsup source every night or so to keep STABLE, using the
	international SECURE servers from cron like:

	30 2 * * *      /usr/local/bin/cvsup -L 1 -g -h cvsup.uk.freebsd.org /usr/share/examples/cvsup/4.x-secure-stable-supfile

	This has worked fine until about two weeks ago when something
	in crypto broke the build process:

	cc -O -pipe -DSKEY -I/usr/obj/usr/src/i386/usr/include -c /usr/src/secure/lib/libssh/../../../crypto/openssh/auth-skey.c -o auth-skey.o
	/usr/src/secure/lib/libssh/../../../crypto/openssh/auth-skey.c: In function `auth_skey_password':
	/usr/src/secure/lib/libssh/../../../crypto/openssh/auth-skey.c:20: warning: initialization makes pointer from integer without a cast
	/usr/src/secure/lib/libssh/../../../crypto/openssh/auth-skey.c: In function `skey_fake_keyinfo':
	/usr/src/secure/lib/libssh/../../../crypto/openssh/auth-skey.c:160: `OPIE_HASHNAME_MAX' undeclared (first use in this function)
	/usr/src/secure/lib/libssh/../../../crypto/openssh/auth-skey.c:160: (Each undeclared identifier is reported only once
	/usr/src/secure/lib/libssh/../../../crypto/openssh/auth-skey.c:160: for each function it appears in.)
	*** Error code 1
	

	I'm really surprised I'm the only one to be whining about
	this, but I haven't seen anyone else on hackers, stable,
	questions complaining. I've tried cvsupping from the
	overburdened "internat" server once and get the same thing.

How-To-Repeat: 
	I've removed /usr/src/crypto today, re-cvsupped, and get the
	same thing, same error, when I try and "make world".
Comment 1 chris 2000-07-17 21:31:10 UTC 
Problem appears to be related to the disappearance of the cvs-secure
(?) distro. I kept cvsupping the now-nonexistent distro, instead of
the new distro with the merged, now-safe-in-the-us crypto code. So of
course I never got the changes incorporated into my tree.

The fix was to stop trying to cvsup the 4.x-secure-stable-supfile and
to use the 4.x-stable-supfile.

Doh.
Comment 2 Sheldon Hearn freebsd_committer freebsd_triage 2000-07-18 09:27:24 UTC 
State Changed
From-To: open->closed

Chris has found the cause of his problem.