Re: Fwd: Problem with modern Postfix on 4.7
On Tue, May 23, 2006 at 11:02:38AM +0200, Matthias Andree wrote: > Scott Harrison <[EMAIL PROTECTED]> writes: > > > There was a suggestion on the web indicating that binutils is > > the problem and that that should be updated. However, I do not know the > > proper way to go about updating binutils. Can someone please tell me > > how to do it or point me to a resource that does? > > NOTE I haven't tried to understand all of your two posts. > > The easiest solution is probably to update FreeBSD 4.X using the > official ways described in the handbook, I'd suggest using 4.11, as 4.10 > is about to be discontinued, and kernel and base system security fixes > are only provided for 4.10 and 4.11 at this time. > > The ports tree has been requiring FreeBSD 4.8 at a minimum for a very > long time now, and I'd expect that even that it requires 4.11 soon > enough. > Or even better, upgrade to 6.x which is the current supported system. For those still on 4.x, please see http://www.freebsd.org/portmgr/policies_releng_4.html -erwin -- Erwin Lansing http://droso.org Security is like an onion. (o_ _o) It's made up of several layers \\\_\ /_///[EMAIL PROTECTED] And it makes you cry.<) (>[EMAIL PROTECTED] pgpIlTFLVCAB2.pgp Description: PGP signature
Re: Fwd: Problem with modern Postfix on 4.7
Scott Harrison <[EMAIL PROTECTED]> writes: > There was a suggestion on the web indicating that binutils is > the problem and that that should be updated. However, I do not know the > proper way to go about updating binutils. Can someone please tell me > how to do it or point me to a resource that does? NOTE I haven't tried to understand all of your two posts. The easiest solution is probably to update FreeBSD 4.X using the official ways described in the handbook, I'd suggest using 4.11, as 4.10 is about to be discontinued, and kernel and base system security fixes are only provided for 4.10 and 4.11 at this time. The ports tree has been requiring FreeBSD 4.8 at a minimum for a very long time now, and I'd expect that even that it requires 4.11 soon enough. -- Matthias Andree ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Fwd: Problem with modern Postfix on 4.7
Begin forwarded message: From: Scott Harrison <[EMAIL PROTECTED]> Date: May 23, 2006 4:31:46 GMT+02:00 To: freebsd-stable@freebsd.org Subject: Problem with modern Postfix on 4.7 Hello, I am not sure if this is the proper place to ask. Please redirect as necessary. I have a FreeBSD 4.7 box that I have updated the ports files. I have tried to recompile Postfix with SASL2 and TLS and now my smtpd is crashing with a SIGBUS when a TLS connection comes in. Prior to upgrading the ports files all was working properly. I recompiled the projects that Postfix needed and the binary seems to be ok: mobius# ldd /usr/local/libexec/postfix/smtpd /usr/local/libexec/postfix/smtpd: libsasl2.so.2 => /usr/local/lib/libsasl2.so.2 (0x280a) libpam.so.1 => /usr/lib/libpam.so.1 (0x280b5000) libcrypt.so.2 => /usr/lib/libcrypt.so.2 (0x280bf000) libssl.so.4 => /usr/local/lib/libssl.so.4 (0x280d8000) libcrypto.so.4 => /usr/local/lib/libcrypto.so.4 (0x28112000) libpcre.so.0 => /usr/local/lib/libpcre.so.0 (0x28228000) libc.so.4 => /usr/lib/libc.so.4 (0x2823e000) mobius# ls -l /usr/local/lib/libsasl2.so.2 /usr/lib/libpam.so.1 / usr/lib/libcrypt.so.2 /usr/local/lib/libssl.so.4 /usr/local/lib/ libcrypto.so.4 /usr/local/lib/libpcre.so.0 /usr/lib/libc.so.4 -r--r--r-- 1 root wheel 574916 Oct 9 2002 /usr/lib/libc.so.4 -r--r--r-- 1 root wheel28432 Oct 9 2002 /usr/lib/libcrypt.so.2 -r--r--r-- 1 root wheel38396 Oct 9 2002 /usr/lib/libpam.so.1 -r--r--r-- 1 root wheel 1339626 May 22 19:53 /usr/local/lib/ libcrypto.so.4 -rwxr-xr-x 1 root wheel87652 May 22 20:41 /usr/local/lib/ libpcre.so.0 -rwxr-xr-x 1 root wheel91881 May 22 20:15 /usr/local/lib/ libsasl2.so.2 -r--r--r-- 1 root wheel 264102 May 22 19:53 /usr/local/lib/ libssl.so.4 mobius# Is there some issue with updating the ports files? Any other suggestions? TIA, It turns out that the openssl port is not building properly, getting lots of lines like this: libssl.a(ssl_asn1.o): In function `d2i_SSL_SESSION': ssl_asn1.o(.text+0x9f9): undefined reference to `memcpy' ssl_asn1.o(.text+0xa78): undefined reference to `memcpy' ssl_asn1.o(.text+0xb40): undefined reference to `memcpy' ssl_asn1.o(.text+0xcda): undefined reference to `time' ssl_asn1.o(.text+0x1140): undefined reference to `memcpy' libssl.a(bio_ssl.o): In function `ssl_read': bio_ssl.o(.text+0x201): undefined reference to `time' libssl.a(bio_ssl.o): In function `ssl_write': bio_ssl.o(.text+0x361): undefined reference to `time' libssl.a(bio_ssl.o): In function `ssl_ctrl': bio_ssl.o(.text+0x6d6): undefined reference to `time' And running make test results in a problem: starting big number library test, could take a while... test BN_add test BN_sub test BN_lshift1 test BN_lshift (fixed) test BN_lshift test BN_rshift1 test BN_rshift test BN_sqr Bus error (core dumped) *** Error code 138 Stop in /usr/ports/security/openssl/work/openssl-0.9.8a/test. *** Error code 1 Stop in /usr/ports/security/openssl/work/openssl-0.9.8a. *** Error code 1 Stop in /usr/ports/security/openssl. There was a suggestion on the web indicating that binutils is the problem and that that should be updated. However, I do not know the proper way to go about updating binutils. Can someone please tell me how to do it or point me to a resource that does? TIA, -- Β·πππͺπ Β·π£πΊπ¦ππ©π― Scott Harrison ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
