Re: [FFmpeg-user] Can't use latest NASM with FFmpeg?

2018-03-17 Thread Reino Wijnsma
On 2-1-2018 23:17, Carl Eugen Hoyos wrote: > 2018-01-02 17:11 GMT+01:00 Reino Wijnsma : >> nasm: fatal: unable to open output file >> `/cygdrive/c/DOCUME~1/Admin/LOCALS~1/Temp/ffconf.Zrz2Fm8R/test.o' > Is it possible that the binary you tested cannot read

Re: [FFmpeg-user] Can't use latest NASM with FFmpeg?

2018-01-02 Thread Reino Wijnsma
On 2-1-2018 23:17, Carl Eugen Hoyos wrote: > 2018-01-02 17:11 GMT+01:00 Reino Wijnsma : >> nasm: fatal: unable to open output file >> `/cygdrive/c/DOCUME~1/Admin/LOCALS~1/Temp/ffconf.Zrz2Fm8R/test.o' > Is it possible that the binary you tested cannot read

Re: [FFmpeg-user] Can't use latest NASM with FFmpeg?

2018-01-02 Thread Carl Eugen Hoyos
2018-01-02 17:11 GMT+01:00 Reino Wijnsma : > nasm: fatal: unable to open output file > `/cygdrive/c/DOCUME~1/Admin/LOCALS~1/Temp/ffconf.Zrz2Fm8R/test.o' Is it possible that the binary you tested cannot read Cygwin paths? Carl Eugen

[FFmpeg-user] Can't use latest NASM with FFmpeg?

2018-01-02 Thread Reino Wijnsma
Hello, Since compiling x264.git requires NASM 2.13 now, I thought; let's try to use it to compile FFmpeg as well. The FFmpeg builds I made this far used Cygwin's NASM. Here's an excerpt from 'ffbuild/config.log':