I could be mistaken, but my impression is that crypto code seems to often screw up the build process. I'm not sure if this is because the crypto code is restricted due to a need for the environment variable USA_RESIDENT to be set to "YES", or because crypto sources and crypto licensing seems to have a history of instability. Somtimes I feel like going back to FreeBSD 3.x because when I ran it I didn't have to worry about OpenSSL, OpenSSH, /dev/random, PAM, etc. and whether they were going to break the build process. The whole system seemed cleaner and contained less extraneous garbage.

Regards,

Glendon Gross

HiTech Creations Support wrote:
We have been working with Martin concerning a problem we are having with
MySQL.  He had us install source from RELENG_4 and then patch the kernel.

The patches to the kernel are fine and we can build the kernel, however we
cannot do a "make buildworld" due to errors in openssh.

Here are the particulars:
We started with STABLE4.6 and I did a CVSup using the following supfile.
*default host=cvsup10.FreeBSD.org
*default base=/usr
*default prefix=/usr
*default release=cvs tag=RELENG_4
*default delete use-rel-suffix
src-all
src-crypto
src-eBones
src-secure

I did a build and install of /usr/src/include and /usr/src/share/mk

During the 'make buildworld' the following errors occurred:
mkdep -f
epend -a   -I/usr/src/lib/libpam/modules/pam_ssh/../../../../crypto/openssh
/usr/src/lib/libpam/modules/pam_ssh/pam_ssh.c
/usr/src/lib/libpam/modules/pam_ssh/pam_ssh.c:61: openssl/dsa.h: No such
file or directory.
/usr/src/lib/libpam/modules/pam_ssh/pam_ssh.c:62: openssl/evp.h: No such
file or directory
In file included from /usr/src/lib/libpam/moduels/pam_ssh/pam_ssh.c:64:
/usr/src/lib/libpam/modules/pam_ssh/../../../../crypto/openssh/key.h:29:
openssl/rsa.h: No such file or directory
/usr/src/lib/libpam/modules/pam_ssh/../../../../crypto/openssh/key.h:30:
openssl/dsa.h: No such file or directory

I am in a pretty desparate situation as we need to get this server back
online as it is a production server.



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-stable" in the body of the message



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-stable" in the body of the message

Reply via email to