Date: Thu, 27 Jan 2011 06:25:00 GMT From: Chris Tandiono <christandiono@tbp.berkeley.edu> To: freebsd-gnats-submit@FreeBSD.org Subject: ports/154325: security/cryptopp fails to build Message-ID: <201101270625.p0R6P0AE088012@red.freebsd.org> Resent-Message-ID: <201101270630.p0R6U7cA075973@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
>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:
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201101270625.p0R6P0AE088012>