Date: Sun, 20 May 2007 12:20:18 +0200 From: Henrik Brix Andersen <henrik@brixandersen.dk> To: freebsd-current@freebsd.org Subject: Re: HEADS UP: OpenSSL problems after GCC 4.2 upgrade Message-ID: <20070520102018.GA41098@tirith.brixandersen.dk> In-Reply-To: <20070520082913.GX23313@hoeg.nl> References: <20070520022722.1f5a0cda@kan.dnsalias.net> <20070520082913.GX23313@hoeg.nl>
index | next in thread | previous in thread | raw e-mail
[-- Attachment #1 --] On Sun, May 20, 2007 at 10:29:13AM +0200, Ed Schouten wrote: > Hello Alexander, > > * Alexander Kabaev <kabaev@gmail.com> wrote: > > there were several reports of OpenSSL being broken when compiled with > > GCC 4.2. It turns out OpenSSL uses function casting feature that was > > aggressively de-supported by GCC 4.2 and GCC goes as far as inserting > > invalid instructions ON PURPOSE to discourage the practice. > > Is that the reason why portsnap returns SIGILL's on my box after the > upgrade? Most likely, yes. Check /var/log/messages. Regards, Brix -- Henrik Brix Andersen <henrik@brixandersen.dk> [-- Attachment #2 --] -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (FreeBSD) Comment: GnuPG signed iD8DBQFGUCDiv+Q4flTiePgRAttWAJ9E2woLKjaDQF1TlKRozTgvJ6PN7gCdGn2T y55W6psZ0x27Liw9qoSHPiQ= =wKdp -----END PGP SIGNATURE-----help
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20070520102018.GA41098>