From owner-freebsd-questions@FreeBSD.ORG Mon May 31 17:51:12 2010 Return-Path: Delivered-To: questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 876E71065679 for ; Mon, 31 May 2010 17:51:12 +0000 (UTC) (envelope-from lists@eitanadler.com) Received: from mail-gw0-f54.google.com (mail-gw0-f54.google.com [74.125.83.54]) by mx1.freebsd.org (Postfix) with ESMTP id 431698FC15 for ; Mon, 31 May 2010 17:51:11 +0000 (UTC) Received: by gwj23 with SMTP id 23so3185174gwj.13 for ; Mon, 31 May 2010 10:51:11 -0700 (PDT) Received: by 10.231.187.29 with SMTP id cu29mr6166326ibb.70.1275328271119; Mon, 31 May 2010 10:51:11 -0700 (PDT) MIME-Version: 1.0 Received: by 10.231.148.201 with HTTP; Mon, 31 May 2010 10:50:51 -0700 (PDT) In-Reply-To: <20100531171141.GA12623@slackbox.erewhon.net> References: <20100531171141.GA12623@slackbox.erewhon.net> From: Eitan Adler Date: Mon, 31 May 2010 20:50:51 +0300 Message-ID: To: Roland Smith Content-Type: text/plain; charset=UTF-8 Cc: questions@freebsd.org Subject: Re: multimedia/ffmpeg fails with internal compiler error X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 31 May 2010 17:51:12 -0000 On Mon, May 31, 2010 at 8:11 PM, Roland Smith wrote: > On Mon, May 31, 2010 at 05:16:50PM +0300, Eitan Adler wrote: >> Is this a >> a) PEBKAC > > Maybe. I don't know how many ports have actually been tested with gcc 4.6. I'm > guessing the ports build cluster uses the base system compiler or the required version. I've been using gcc46 for a while now and just remove certain ports in /etc/make.conf SSSE3=on "Enable ssse3 support (gcc 4.4+)" seems to mean that 4.4+ works. >> d) compiler problem (as the error seems to be saying) > > Could be. I recompiled it with gcc-4.4.5.20100518 without problems. So it > could be a bug specific to gcc 4.6. Maybe I will do as the error says and report the error ;) > e) hardware error. unlikely: I tested both my RAM and HDD recently. It is also the only port that has failed with this type of error. > Sometimes these errors are triggered by e.g. bad RAM. > > Does removing these cflags make any difference? turning off OPTIMIZED_CFLAGS (but leaving ssse3) does not help. -- Eitan Adler