From owner-freebsd-current@FreeBSD.ORG Sun May 20 10:26:14 2007 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id A820316A421 for ; Sun, 20 May 2007 10:26:14 +0000 (UTC) (envelope-from dudu@dudu.ro) Received: from mu-out-0910.google.com (mu-out-0910.google.com [209.85.134.187]) by mx1.freebsd.org (Postfix) with ESMTP id 44FB013C45A for ; Sun, 20 May 2007 10:26:14 +0000 (UTC) (envelope-from dudu@dudu.ro) Received: by mu-out-0910.google.com with SMTP id w8so823990mue for ; Sun, 20 May 2007 03:26:13 -0700 (PDT) Received: by 10.82.113.6 with SMTP id l6mr6357680buc.1179656772761; Sun, 20 May 2007 03:26:12 -0700 (PDT) Received: by 10.82.148.14 with HTTP; Sun, 20 May 2007 03:26:12 -0700 (PDT) Message-ID: Date: Sun, 20 May 2007 13:26:12 +0300 From: "Vlad GALU" To: freebsd-current@freebsd.org In-Reply-To: <20070520102018.GA41098@tirith.brixandersen.dk> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <20070520022722.1f5a0cda@kan.dnsalias.net> <20070520082913.GX23313@hoeg.nl> <20070520102018.GA41098@tirith.brixandersen.dk> Subject: Re: HEADS UP: OpenSSL problems after GCC 4.2 upgrade X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 20 May 2007 10:26:14 -0000 On 5/20/07, Henrik Brix Andersen wrote: > On Sun, May 20, 2007 at 10:29:13AM +0200, Ed Schouten wrote: > > Hello Alexander, > > > > * Alexander Kabaev 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. There might be a PEBKAC here, but after applying the patch (cleanly) and rebuilding/reinstalling everything under /usr/src/secure, OpenVPN still crashes with SIGILL. > > Regards, > Brix > -- > Henrik Brix Andersen > > -- If it's there, and you can see it, it's real. If it's not there, and you can see it, it's virtual. If it's there, and you can't see it, it's transparent. If it's not there, and you can't see it, you erased it.