From owner-freebsd-hackers@FreeBSD.ORG Wed Dec 7 12:17:58 2011 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id BA72B1065675 for ; Wed, 7 Dec 2011 12:17:58 +0000 (UTC) (envelope-from tevans.uk@googlemail.com) Received: from mail-vw0-f54.google.com (mail-vw0-f54.google.com [209.85.212.54]) by mx1.freebsd.org (Postfix) with ESMTP id 722788FC0A for ; Wed, 7 Dec 2011 12:17:58 +0000 (UTC) Received: by vbbfr13 with SMTP id fr13so628610vbb.13 for ; Wed, 07 Dec 2011 04:17:57 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=Yo+Ml7vRXERVuE5fVExauASZtOkYkP1FBqXGmQzohhI=; b=db5GlfQseNs1L2T9ytmf+dyZlPT8sOLnXo/iqijEXRbJYEYQ8zkrc6P7ALLsri/dGK beeYefoEJarl/0Ycp0mn29vukeftdWvJrs14quBvPJdlMRTDmb/IfEw4Y7jLRvHktBb6 bMFIX4ehnZ4eNJpUbP5qoho10AbHGIS83nw2o= MIME-Version: 1.0 Received: by 10.52.186.225 with SMTP id fn1mr10475785vdc.32.1323260277591; Wed, 07 Dec 2011 04:17:57 -0800 (PST) Received: by 10.52.172.240 with HTTP; Wed, 7 Dec 2011 04:17:57 -0800 (PST) In-Reply-To: <4EDF5253.5060201@herveybayaustralia.com.au> References: <4EDEB600.9000102@herveybayaustralia.com.au> <4EDF4703.1050705@herveybayaustralia.com.au> <4EDF5253.5060201@herveybayaustralia.com.au> Date: Wed, 7 Dec 2011 12:17:57 +0000 Message-ID: From: Tom Evans To: Da Rock Content-Type: text/plain; charset=UTF-8 Cc: freebsd-hackers@freebsd.org Subject: Re: 64bit build errors X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 07 Dec 2011 12:17:58 -0000 On Wed, Dec 7, 2011 at 11:47 AM, Da Rock wrote: > I really hate sounding like an idiot, but if I don't ask I'll never know: > The assembler in base is not up-to-date with the latest instruction sets for > the cpu, and is causing an error because its telling the cpu to do something > it doesn't understand and is going WTF! So the port binutils provides the > latest instruction sets for the latest cpus. And ffmpeg and friends use the > latest cpu abilities to run as fast as they do? Right or way off? Otherwise > I'd have problems building anything, wouldn't I? The way I understand it is that they use compiler/assembler features that did not exist in the version of binutils that is in base. That might be related to CPU features - I know you need binutils from ports to use SSE3 features, for example - but whether that is what happens here, or whether it is due to ffmpeg using newer features would have to be answered by someone who understands what is going on! Cheers Tom