[libav-tools] cross compile problem with yasm

Farkas Levente lfarkas at lfarkas.org
Mon Aug 1 17:32:38 CEST 2011

On 08/01/2011 05:29 PM, Luca Barbato wrote:
> On 8/1/11 4:36 PM, Farkas Levente wrote:
>> On 08/01/2011 02:55 PM, Luca Barbato wrote:
>>> On 8/1/11 1:48 PM, Farkas Levente wrote:
>>>> On 08/01/2011 12:45 PM, Luca Barbato wrote:
>>>>> On 8/1/11 11:56 AM, Farkas Levente wrote:
>>>>>> hi,
>>>>>> i try to build on linux with mingw64 toolchain the gstreamer
>>>>>> packages.
>>>>>> all build and working fine except gst-ffmpeg. gst-ffmpeg inlude
>>>>>> libav as
>>>>>> it's backend. when i try build it on linux with mingw than i use
>>>>>> yasm.
>>>>>> it compile and build without any kind of error, but when i try to
>>>>>> use it
>>>>>> seg fault immediately.
>>>>> The backtrace isn't much meaningful, please get gdb to point the
>>>>> sources. We have mingw64 builds on win32.libav.org could you please
>>>>> try
>>>>> those and see if ffplay can decode correctly your testfile?
>>> qlist -Iv yasm mingw
>>> cross-i686-w64-mingw32/binutils-2.21
>>> cross-i686-w64-mingw32/gcc-4.5.2
>>> cross-i686-w64-mingw32/mingw64-runtime-20101003
>>> cross-mingw32/binutils-2.21
>>> cross-mingw32/gcc-4.5.2
>>> cross-mingw32/mingw-runtime-3.18
>>> cross-mingw32/w32api-3.15
>>> cross-x86_64-w64-mingw32/binutils-2.21
>>> cross-x86_64-w64-mingw32/gcc-4.5.2
>>> cross-x86_64-w64-mingw32/mingw64-runtime-20101003
>>> dev-lang/yasm-1.1.0-r1
>>> Those are my versions for the toolchains not sure how much it helps.
>> not too much.
>> now i try to build a standalone libav. here are a few of my thoughts:
>> - it'd be good if configure can except (or ext least don't generate
>> error on default arguments like:
>> --host=i686-w64-mingw32
>> --exec-prefix=/usr/i686-w64-mingw32/sys-root/mingw
>> etc.
> If you are referring to yasm you are supposed to have it installed, it
> is optional-only-if-you-accept-detriment, if you are referring to
> windows-specific hacks, we are still hoping the next iteration could fix
> it.

i referring to windows-specific cross compilation.
but anyway the configure option is independent of the compilation it's
run before the build. so configure could accept these options.

>> - it has no real reason to generate symlink in case of cross compile,
>> since on windows it's not working:
>> avcodec-53.dll ->  avcodec-53.5.0.dll
>> but in this case may be name it avcodec-53.dll would be better then
>> avcodec-53.5.0.dll otherwise the exe can't find the dlls.
> That should be fixed in the current libav git.

i test it with 0.7.1.

  Levente                               "Si vis pacem para bellum!"

More information about the libav-tools mailing list