From owner-freebsd-ports-bugs@FreeBSD.ORG Thu Jan 27 06:30:07 2011 Return-Path: Delivered-To: freebsd-ports-bugs@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D6DB9106564A for ; Thu, 27 Jan 2011 06:30:07 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 9910C8FC19 for ; Thu, 27 Jan 2011 06:30:07 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id p0R6U7YB075974 for ; Thu, 27 Jan 2011 06:30:07 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id p0R6U7cA075973; Thu, 27 Jan 2011 06:30:07 GMT (envelope-from gnats) Resent-Date: Thu, 27 Jan 2011 06:30:07 GMT Resent-Message-Id: <201101270630.p0R6U7cA075973@freefall.freebsd.org> Resent-From: FreeBSD-gnats-submit@FreeBSD.org (GNATS Filer) Resent-To: freebsd-ports-bugs@FreeBSD.org Resent-Reply-To: FreeBSD-gnats-submit@FreeBSD.org, Chris Tandiono Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E4A46106564A for ; Thu, 27 Jan 2011 06:25:01 +0000 (UTC) (envelope-from nobody@FreeBSD.org) Received: from red.freebsd.org (red.freebsd.org [IPv6:2001:4f8:fff6::22]) by mx1.freebsd.org (Postfix) with ESMTP id D32E28FC18 for ; Thu, 27 Jan 2011 06:25:01 +0000 (UTC) Received: from red.freebsd.org (localhost [127.0.0.1]) by red.freebsd.org (8.14.4/8.14.4) with ESMTP id p0R6P0qN088013 for ; Thu, 27 Jan 2011 06:25:00 GMT (envelope-from nobody@red.freebsd.org) Received: (from nobody@localhost) by red.freebsd.org (8.14.4/8.14.4/Submit) id p0R6P0AE088012; Thu, 27 Jan 2011 06:25:00 GMT (envelope-from nobody) Message-Id: <201101270625.p0R6P0AE088012@red.freebsd.org> Date: Thu, 27 Jan 2011 06:25:00 GMT From: Chris Tandiono To: freebsd-gnats-submit@FreeBSD.org X-Send-Pr-Version: www-3.1 Cc: Subject: ports/154325: security/cryptopp fails to build X-BeenThere: freebsd-ports-bugs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Ports bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 27 Jan 2011 06:30:07 -0000 >Number: 154325 >Category: ports >Synopsis: security/cryptopp fails to build >Confidential: no >Severity: non-critical >Priority: low >Responsible: freebsd-ports-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Thu Jan 27 06:30:07 UTC 2011 >Closed-Date: >Last-Modified: >Originator: Chris Tandiono >Release: 8.1-RELEASE-p2 >Organization: Tau Beta Pi CA-A >Environment: FreeBSD host.local 8.1-RELEASE FreeBSD 8.1-RELEASE #0: Mon Jul 19 02:55:53 UTC 2010 root@almeida.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC i386 >Description: security/cryptopp fails to build. It seems to be an intermittent problem affecting very few users with no apparent correlation. I get messages like: {standard input}: Assembler messages: {standard input}:343: Error: no such instruction: `palignr xmm5,xmm2,4' {standard input}:343: Error: no such instruction: `palignr xmm6,xmm3,4' {standard input}:349: Error: no such instruction: `palignr xmm7,xmm3,4' {standard input}:349: Error: no such instruction: `palignr xmm6,xmm2,4' {standard input}:349: Error: no such instruction: `palignr xmm5,xmm1,4' {standard input}:349: Error: no such instruction: `palignr xmm4,xmm0,4' >How-To-Repeat: Attempt to compile the latest cryptopp from ports. It is unknown what other factors are necessary to induce this bug. If it helps, the processor in question is a Xeon E5335 which does have support for the instruction. It also doesn't happen on a similarly-configured machine with a different processor, which somehow adds -DCRYPTOPP_DISABLE_SSSE3 to its CXXFLAGS. I'm using gcc 4.2.1 and FreeBSD 8.1-RELEASE-p2 on both machines. >Fix: I think adding -DCRYPTOPP_DISABLE_SSSE3 to CXXFLAGS ameliorates the problem, but it doesn't explain why the assembler would somehow end up getting instructions it can't assemble. Also, the processor definitely supports SSSE3. >Release-Note: >Audit-Trail: >Unformatted: