On 12/08/11 19:58, Tom Evans wrote:
On Thu, Dec 8, 2011 at 6:05 AM, Da Rock
<freebsd-hack...@herveybayaustralia.com.au> 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
_______________________________________________
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "freebsd-hackers-unsubscr...@freebsd.org"
