RE: How do I replace the built-in OpenSSL with a source tarball ?
Maybe remove the existing package first? And try to use a pkg if you can for the new one. -Original Message- From: owner-freebsd-questi...@freebsd.org [mailto:owner-freebsd-questi...@freebsd.org] On Behalf Of George Sanders Sent: Wednesday, October 28, 2009 10:58 AM To: freebsd-questions@freebsd.org Subject: How do I replace the built-in OpenSSL with a source tarball ? I would like to: - upgrade the built-in OpenSSL that comes with FreeBSD (in my case, 6.4-RELEASE) - replace it with OpenSSL that I build myself from the source tarball If I do this with a plain old: ./config ; make ; make install OpenSSL does indeed build and install, but it installs in an alternate location and does not overwrite the FreeBSD built-in. Ok, should be easy to fix - I will simply use an: --prefix config directive and point it to /usr: --prefix=/usr However, that does not work - running: /usr/local/ssl/bin/openssl version shows me that this binary has not changed. Ok, no problem, I will simply use: --prefix=/usr/local instead ... but that also does not work. No matter what I do, I cannot get the OpenSSL source tarball to overwrite my built-in OpenSSL in FreeBSD - I always end up having two binaries in two different locations. Can someone tell me how to just cleanly replace the built-in OpenSSL with the source tarball ? Thanks. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org font size=1 div style='border:none;border-bottom:double windowtext 2.25pt;padding:0in 0in 1.0pt 0in' /div This email is intended to be reviewed by only the intended recipient and may contain information that is privileged and/or confidential. If you are not the intended recipient, you are hereby notified that any review, use, dissemination, disclosure or copying of this email and its attachments, if any, is strictly prohibited. If you have received this email in error, please immediately notify the sender by return email and delete this email from your system. /font ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: How do I replace the built-in OpenSSL with a source tarball ?
- Original Message From: Gary Gatten ggat...@waddell.com To: George Sanders gosand1...@yahoo.com; freebsd-questions@freebsd.org Sent: Wed, October 28, 2009 11:01:35 AM Subject: RE: How do I replace the built-in OpenSSL with a source tarball ? Maybe remove the existing package first? And try to use a pkg if you can for the new one. Yes, but I still won't know how to put the new version in _exactly the same place_ as the one I just removed. For complex reasons of space and tools (embedded system, etc.) I do indeed need to use the source tarball. So I'd like to know what configure directive to feed to it to properly and _exactly_ replace the existing FreeBSD default OpenSSL... Thanks. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: How do I replace the built-in OpenSSL with a source tarball ?
On Wed, 28 Oct 2009 08:57:52 -0700 (PDT) George Sanders gosand1...@yahoo.com replied: I would like to: - upgrade the built-in OpenSSL that comes with FreeBSD (in my case, 6.4-RELEASE) - replace it with OpenSSL that I build myself from the source tarball If I do this with a plain old: ./config ; make ; make install OpenSSL does indeed build and install, but it installs in an alternate location and does not overwrite the FreeBSD built-in. Ok, should be easy to fix - I will simply use an: --prefix config directive and point it to /usr: --prefix=/usr However, that does not work - running: /usr/local/ssl/bin/openssl version shows me that this binary has not changed. Ok, no problem, I will simply use: --prefix=/usr/local instead ... but that also does not work. No matter what I do, I cannot get the OpenSSL source tarball to overwrite my built-in OpenSSL in FreeBSD - I always end up having two binaries in two different locations. Can someone tell me how to just cleanly replace the built-in OpenSSL with the source tarball ? I use this in my /etc/make.conf file: WITH_OPENSSL_PORT=yes -- Jerry ges...@yahoo.com |=== |=== |=== |=== | (null cookie; hope that's ok) ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: How do I replace the built-in OpenSSL with a source tarball ?
George Sanders wrote: - Original Message From: Gary Gatten ggat...@waddell.com To: George Sanders gosand1...@yahoo.com; freebsd-questions@freebsd.org Sent: Wed, October 28, 2009 11:01:35 AM Subject: RE: How do I replace the built-in OpenSSL with a source tarball ? Maybe remove the existing package first? And try to use a pkg if you can for the new one. Yes, but I still won't know how to put the new version in _exactly the same place_ as the one I just removed. For complex reasons of space and tools (embedded system, etc.) I do indeed need to use the source tarball. So I'd like to know what configure directive to feed to it to properly and _exactly_ replace the existing FreeBSD default OpenSSL... Thanks. Well the base openssl is held in /usr/src/crypto/openssl but the makefile is in /usr/src/secure/usr.bin/openssl so I'd look at those. I'm in no way knowledgeable about openssl or how its integrated into freebsd though, this is just from a quick look at the sources. Vince ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: How do I replace the built-in OpenSSL with a source tarball ?
On Wed, Oct 28, 2009 at 09:14:22AM -0700, George Sanders wrote: Yes, but I still won't know how to put the new version in _exactly the same place_ as the one I just removed. For complex reasons of space and tools (embedded system, etc.) I do indeed need to use the source tarball. So I'd like to know what configure directive to feed to it to properly and _exactly_ replace the existing FreeBSD default OpenSSL... Not knowing anything more about ones complex reasons, I suggest giving serious consideration as to replacing the contents of /usr/src/crypto/openssl/ with OpenSSL's distribution sources and see what happens when one makes from /usr/src/secure/usr.bin/openssl/ But before doing that I think serious consideration should be made as to making what ever embedded customizations one needs to the stock FreeBSD distribution files. Make your changes then generate patch files as an archive of the differences. Or better yet create your own custom fork in CVS, but I don't know how one would do that and still be able to sync with the official sources. IIRC there are plans to move the official FreeBSD sources to Subversion, which might complicate things. Have noticed in recent months cvsup often must replace rather than update files because checksums do not match. Guessing that has something to do with svn. http://svn.freebsd.org/ In years past I built a custom embedded FreeBSD out of FreeBSD 4.4 using only a custom Makefile outside of the /usr/src tree to drive the whole process. My built started with a clean checkout from my local CVS image of the official distribution. Don't recall making any code changes that couldn't be handled as compile defines from the Makefiles. Built into a chroot space, including selected ports. Then working from a list of utilities that I wanted in my reduced FreeBSD a script extracted library dependencies to create another list. Finally a new directory tree was created of the new system of only the files I wanted and their dependencies. My system including kernel was under 10 MB. Plus another 10 or 15 MB for Apache, and another 10 MB or so for Perl. Kept a 500 MHz P3 busy for a while. :-) -- David Kelly N4HHE, dke...@hiwaay.net Whom computers would destroy, they must first drive mad. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
