Re: [SOLVED]Re: 64bit build errors - use gcc46
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 Cheers Tom ___ 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
Re: [SOLVED]Re: 64bit build errors - use gcc46
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
Re: 64bit build errors
On Wed, Dec 7, 2011 at 12:40 AM, Da Rock freebsd-hack...@herveybayaustralia.com.au wrote: I'm trying to build some newer versions of ffserver. But I keep getting asm build errors when I get to libavcodec/vp*. Error: `(%esi,%eax)' is not a valid 64 bit base/index expression If I set it to build static it fails at h264. Error: `-1(%edi)' is not a valid 64 bit base/index expression Googling hasn't proved helpful in finding an answer. I've tried setting some configure options: arch=amd64/x86_64, disabling cmov/fast_cmov, ebx, etc. Any ideas how to fix this? Cheers Yes, you need to use newer binutils from ports. It also helps with ffmpeg/mplayer to use a newer gcc from ports as well (I use gcc46), but the main thing is installing binutils and configuring with --as=/usr/local/bin/as. Cheers Tom ___ 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
Re: 64bit build errors
On 12/07/11 20:36, Tom Evans wrote: On Wed, Dec 7, 2011 at 12:40 AM, Da Rock freebsd-hack...@herveybayaustralia.com.au wrote: I'm trying to build some newer versions of ffserver. But I keep getting asm build errors when I get to libavcodec/vp*. Error: `(%esi,%eax)' is not a valid 64 bit base/index expression If I set it to build static it fails at h264. Error: `-1(%edi)' is not a valid 64 bit base/index expression Googling hasn't proved helpful in finding an answer. I've tried setting some configure options: arch=amd64/x86_64, disabling cmov/fast_cmov, ebx, etc. Any ideas how to fix this? Cheers Yes, you need to use newer binutils from ports. It also helps with ffmpeg/mplayer to use a newer gcc from ports as well (I use gcc46), but the main thing is installing binutils and configuring with --as=/usr/local/bin/as. Cool! Thanks for that. I got a manual to read by the looks of it anyway, but can anyone give me the inside gos on the why it does what it does? (Or something like that.. :) ) 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
Re: 64bit build errors
On 12/07/11 21:29, Tom Evans wrote: On Wed, Dec 7, 2011 at 10:59 AM, Da Rock freebsd-hack...@herveybayaustralia.com.au wrote: Cool! Thanks for that. I got a manual to read by the looks of it anyway, but can anyone give me the inside gos on the why it does what it does? (Or something like that.. :) ) This email explains it: http://lists.mplayerhq.hu/pipermail/mplayer-users/2011-July/083051.html 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? ___ 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
Re: 64bit build errors
On Wed, Dec 7, 2011 at 10:59 AM, Da Rock freebsd-hack...@herveybayaustralia.com.au wrote: Cool! Thanks for that. I got a manual to read by the looks of it anyway, but can anyone give me the inside gos on the why it does what it does? (Or something like that.. :) ) This email explains it: http://lists.mplayerhq.hu/pipermail/mplayer-users/2011-July/083051.html Cheers Tom ___ 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
Re: 64bit build errors
On Wed, Dec 7, 2011 at 11:47 AM, Da Rock freebsd-hack...@herveybayaustralia.com.au 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 ___ 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
Re: 64bit build errors
On 2011-12-07 01:40, Da Rock wrote: I'm trying to build some newer versions of ffserver. But I keep getting asm build errors when I get to libavcodec/vp*. Error: `(%esi,%eax)' is not a valid 64 bit base/index expression If I set it to build static it fails at h264. Error: `-1(%edi)' is not a valid 64 bit base/index expression Googling hasn't proved helpful in finding an answer. I've tried setting some configure options: arch=amd64/x86_64, disabling cmov/fast_cmov, ebx, etc. Any ideas how to fix this? At first glance, I'd say you are compiling it with a 32-bit compiler or assembler. In any case, I downloaded the latest version (0.8.7) from ffmpeg.org, and it compiles just fine with base gcc. What are the exact commands you are running? ___ 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
Re: 64bit build errors
On 12/07/11 22:17, Tom Evans wrote: On Wed, Dec 7, 2011 at 11:47 AM, Da Rock freebsd-hack...@herveybayaustralia.com.au 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! Ok, that did just answer it. For starters SSE3 is used in ffmpeg/mplayer, but there would be more (3DNOW, etc). So that explains it... interesting study. I'll have a closer look at the docs on binutils to find out more. 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
Re: 64bit build errors
On Wed, Dec 7, 2011 at 1:52 PM, Dimitry Andric d...@freebsd.org wrote: On 2011-12-07 01:40, Da Rock wrote: I'm trying to build some newer versions of ffserver. But I keep getting asm build errors when I get to libavcodec/vp*. Error: `(%esi,%eax)' is not a valid 64 bit base/index expression If I set it to build static it fails at h264. Error: `-1(%edi)' is not a valid 64 bit base/index expression Googling hasn't proved helpful in finding an answer. I've tried setting some configure options: arch=amd64/x86_64, disabling cmov/fast_cmov, ebx, etc. Any ideas how to fix this? At first glance, I'd say you are compiling it with a 32-bit compiler or assembler. In any case, I downloaded the latest version (0.8.7) from ffmpeg.org, and it compiles just fine with base gcc. What are the exact commands you are running? I imagine you are running CURRENT or 9.0, which has a newer binutils than 8-STABLE, which is what causes/exposes this issue. Cheers Tom ___ 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
Re: 64bit build errors
On Dec 7, 2011, at 6:22 AM, Tom Evans tevans...@googlemail.com wrote: On Wed, Dec 7, 2011 at 1:52 PM, Dimitry Andric d...@freebsd.org wrote: On 2011-12-07 01:40, Da Rock wrote: I'm trying to build some newer versions of ffserver. But I keep getting asm build errors when I get to libavcodec/vp*. Error: `(%esi,%eax)' is not a valid 64 bit base/index expression If I set it to build static it fails at h264. Error: `-1(%edi)' is not a valid 64 bit base/index expression Googling hasn't proved helpful in finding an answer. I've tried setting some configure options: arch=amd64/x86_64, disabling cmov/fast_cmov, ebx, etc. Any ideas how to fix this? At first glance, I'd say you are compiling it with a 32-bit compiler or assembler. In any case, I downloaded the latest version (0.8.7) from ffmpeg.org, and it compiles just fine with base gcc. What are the exact commands you are running? I imagine you are running CURRENT or 9.0, which has a newer binutils than 8-STABLE, which is what causes/exposes this issue. The question is: what is the OP running? I don't think that's been identified yet.. Thanks! -Garrett___ 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
Re: 64bit build errors
On Wed, 7 Dec 2011 12:17:57 + Tom Evans tevans...@googlemail.com wrote: 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. Which begs the question - why isn't the new version of the tools (provided by ports) listed in BUILDDEPENDS in the port, then? mike ___ 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
Re: 64bit build errors
On 12/08/11 00:45, Garrett Cooper wrote: On Dec 7, 2011, at 6:22 AM, Tom Evanstevans...@googlemail.com wrote: On Wed, Dec 7, 2011 at 1:52 PM, Dimitry Andricd...@freebsd.org wrote: On 2011-12-07 01:40, Da Rock wrote: I'm trying to build some newer versions of ffserver. But I keep getting asm build errors when I get to libavcodec/vp*. Error: `(%esi,%eax)' is not a valid 64 bit base/index expression If I set it to build static it fails at h264. Error: `-1(%edi)' is not a valid 64 bit base/index expression Googling hasn't proved helpful in finding an answer. I've tried setting some configure options: arch=amd64/x86_64, disabling cmov/fast_cmov, ebx, etc. Any ideas how to fix this? At first glance, I'd say you are compiling it with a 32-bit compiler or assembler. In any case, I downloaded the latest version (0.8.7) from ffmpeg.org, and it compiles just fine with base gcc. What are the exact commands you are running? I imagine you are running CURRENT or 9.0, which has a newer binutils than 8-STABLE, which is what causes/exposes this issue. The question is: what is the OP running? I don't think that's been identified yet.. For reference 8.1 and 8.2. I'll post once I've had a chance to confirm the solution, but I'm pretty sure it will solve it based on the info I've been given. 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
Re: 64bit build errors
On 12/08/11 05:47, Mike Meyer wrote: On Wed, 7 Dec 2011 12:17:57 + Tom Evanstevans...@googlemail.com wrote: 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. Which begs the question - why isn't the new version of the tools (provided by ports) listed in BUILDDEPENDS in the port, then? I'm not building the port. This is my own build, so the builddepends isn't existent. ___ 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
Re: 64bit build errors
On 12/08/11 08:31, Da Rock wrote: On 12/08/11 05:47, Mike Meyer wrote: On Wed, 7 Dec 2011 12:17:57 + Tom Evanstevans...@googlemail.com wrote: 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. Which begs the question - why isn't the new version of the tools (provided by ports) listed in BUILDDEPENDS in the port, then? I'm not building the port. This is my own build, so the builddepends isn't existent. Hence hackers@, else I would have posted ports@ ___ 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
[SOLVED]Re: 64bit build errors - use gcc46
On 12/08/11 08:33, Da Rock wrote: On 12/08/11 08:31, Da Rock wrote: On 12/08/11 05:47, Mike Meyer wrote: On Wed, 7 Dec 2011 12:17:57 + Tom Evanstevans...@googlemail.com wrote: 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. Which begs the question - why isn't the new version of the tools (provided by ports) listed in BUILDDEPENDS in the port, then? I'm not building the port. This is my own build, so the builddepends isn't existent. Hence hackers@, else I would have posted ports@ 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. ___ 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
