From owner-freebsd-hackers@FreeBSD.ORG Thu Dec 8 13:20:41 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 44D2A1065680 for ; Thu, 8 Dec 2011 13:20:41 +0000 (UTC) (envelope-from freebsd-hackers@herveybayaustralia.com.au) Received: from mail.unitedinsong.com.au (mail.unitedinsong.com.au [150.101.178.33]) by mx1.freebsd.org (Postfix) with ESMTP id E20648FC0A for ; Thu, 8 Dec 2011 13:20:40 +0000 (UTC) Received: from laptop1.herveybayaustralia.com.au (laptop1.herveybayaustralia.com.au [192.168.0.179]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by mail.unitedinsong.com.au (Postfix) with ESMTPSA id 6717F5C24 for ; Thu, 8 Dec 2011 23:33:02 +1000 (EST) Message-ID: <4EE0B905.1050505@herveybayaustralia.com.au> Date: Thu, 08 Dec 2011 23:17:57 +1000 From: Da Rock User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:7.0.1) Gecko/20111109 Thunderbird/7.0.1 MIME-Version: 1.0 To: freebsd-hackers@freebsd.org References: <4EDEB600.9000102@herveybayaustralia.com.au> <4EDF4703.1050705@herveybayaustralia.com.au> <4EDF5253.5060201@herveybayaustralia.com.au> <20111207114756.48295690@mikmeyer-vm-fedora> <4EDFE933.3060708@herveybayaustralia.com.au> <4EDFE9BD.9020105@herveybayaustralia.com.au> <4EE0539E.3030406@herveybayaustralia.com.au> In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [SOLVED]Re: 64bit build errors - use gcc46 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: Thu, 08 Dec 2011 13:20:41 -0000 On 12/08/11 19:58, Tom Evans wrote: > On Thu, Dec 8, 2011 at 6:05 AM, Da Rock > wrote: >> Just to let the list know, I changed as - ./configure >> --as=/usr/local/bin/as. I still had the exact same error oddly enough. >> >> I then had to install gcc46; and the error changed. >> >> I then had to update the configure script to comment out the v4l videodev >> headers (weird). Bingo! I had success. >> >> So, it begs the question did the as option change things? Or does gcc46 >> imply the use of it anyway? >> >> I'll have to try again without the option to see for sure, but for now I >> have another project that I need to keep the status quo for. > Yes, sometimes as is invoked via gcc, and if you are using the stock > gcc, it uses the stock as, and you still get the errors. You need both > gcc46 and binutils from ports. > > Sorry, forgot that bit :o > > Confirmed. Built without --as and only --cc arguments. Great learning experience for me anyway... :) Cheers