[Mingw-w64-public] ffmpeg.c:4492: undefined reference to `_avdevice_register_all'

2011-09-08 Thread Kyle Schwarz
I'm having issues compiling FFmpeg for Windows with MinGW-w64. I'm using the latest MinGW-w64 and the latest FFmpeg. A bug report can be found here: https://ffmpeg.org/trac/ffmpeg/ticket/282 A mailing list post can be found here: https://lists.ffmpeg.org/pipermail/ffmpeg-user/2011-September/00224

Re: [Mingw-w64-public] ffmpeg.c:4492: undefined reference to `_avdevice_register_all'

2011-09-08 Thread Kai Tietz
2011/9/8 Kyle Schwarz : > I'm having issues compiling FFmpeg for Windows with MinGW-w64. I'm > using the latest MinGW-w64 and the latest FFmpeg. > > A bug report can be found here: https://ffmpeg.org/trac/ffmpeg/ticket/282 > > A mailing list post can be found here: > https://lists.ffmpeg.org/piperm

Re: [Mingw-w64-public] ffmpeg.c:4492: undefined reference to `_avdevice_register_all'

2011-09-09 Thread Kyle
On 9/8/2011 5:10 PM, Kai Tietz wrote: > i686-w64-mingw32-objdump "./libavdevice/avdevice.dll" | grep > "avdevice_register_all" That doesn't actually return anything other then objdump's usage info. I see that there are many options and am unsure of which I should use. > So my bet would go for

Re: [Mingw-w64-public] ffmpeg.c:4492: undefined reference to `_avdevice_register_all'

2011-09-10 Thread Kai Tietz
2011/9/10 Kyle : > On 9/8/2011 5:10 PM, Kai Tietz wrote: > >> i686-w64-mingw32-objdump "./libavdevice/avdevice.dll" | grep >> "avdevice_register_all" > > That doesn't actually return anything other then objdump's usage info. I see > that there are many options and am unsure of which I should use.

Re: [Mingw-w64-public] ffmpeg.c:4492: undefined reference to `_avdevice_register_all'

2011-09-10 Thread Kyle
On 9/10/2011 3:45 AM, Kai Tietz wrote: > Sorry for that. I missed the option -x. So complete line is > 'i686-w64-mingw32-objdump -x "./libavdevice/avdevice.dll" | grep > "avdevice_register_all"' That command returns: [ 187] avdevice_register_all [ 49](sec 1)(fl 0x00)(ty 20)(scl 2) (nx 1) 0x0

Re: [Mingw-w64-public] ffmpeg.c:4492: undefined reference to `_avdevice_register_all'

2011-09-10 Thread Kai Tietz
2011/9/10 Kyle : > On 9/10/2011 3:45 AM, Kai Tietz wrote: >> Sorry for that. I missed the option -x. So complete line is >> 'i686-w64-mingw32-objdump -x "./libavdevice/avdevice.dll" | grep >> "avdevice_register_all"' > > That command returns: > [ 187] avdevice_register_all > [ 49](sec  1)(fl 0x00)(

Re: [Mingw-w64-public] ffmpeg.c:4492: undefined reference to `_avdevice_register_all'

2011-09-10 Thread Kyle
On 9/10/2011 4:51 AM, Kai Tietz wrote: > So this means that the export is present. So the issue might be > caused by link-order of libraries and objects. Do you use gcc's > frontend for linking, or are you invoking linker (i686-w64-mingw-ld) > directly? > > Could you provide me the link command-l

Re: [Mingw-w64-public] ffmpeg.c:4492: undefined reference to `_avdevice_register_all'

2011-09-10 Thread Kai Tietz
2011/9/10 Kyle : > On 9/10/2011 4:51 AM, Kai Tietz wrote: >> So this means that the export is present.  So the issue might be >> caused by link-order of libraries and objects.  Do you use gcc's >> frontend for linking, or are you invoking linker (i686-w64-mingw-ld) >> directly? >> >> Could you prov

Re: [Mingw-w64-public] ffmpeg.c:4492: undefined reference to `_avdevice_register_all'

2011-09-10 Thread Kyle
On 9/10/2011 5:37 AM, Kai Tietz wrote: > Hmm, would it help to move command '-lavdevice' before the command > '-lavicap32'? > > Kai > > -- > Malware Security Report: Protecting Your Business, Customers, and the > Bottom Li

Re: [Mingw-w64-public] ffmpeg.c:4492: undefined reference to `_avdevice_register_all'

2011-09-10 Thread Kai Tietz
2011/9/10 Kyle : > On 9/10/2011 5:37 AM, Kai Tietz wrote: >> Hmm, would it help to move command '-lavdevice' before the command >> '-lavicap32'? >> >> Kai >> >> -- >> Malware Security Report: Protecting Your Business, Cust

Re: [Mingw-w64-public] ffmpeg.c:4492: undefined reference to `_avdevice_register_all'

2011-09-10 Thread PcX
于 2011/9/10 17:42, Kyle 写道: Unfortunately I get the same error with -lavdevice located at the end: i686-w64-mingw32-gcc -Llibavcodec -Llibavdevice -Llibavfilter -Llibavformat -Llibavutil -Llibpostproc -Llibswscale -L/home/kyle/software/ffmpeg/packages/sdl/sdl-1.2.14-win32/lib -Wl,--as-needed -Wl,

Re: [Mingw-w64-public] ffmpeg.c:4492: undefined reference to `_avdevice_register_all'

2011-09-10 Thread PcX
于 2011/9/10 18:51, PcX 写道: i686-w64-mingw32-gcc -Wl,--as-needed -Wl,--warn-common -Wl,-rpath-link=libpostproc:libswscale:libavfilter:libavdevice:libavformat:libavcodec:libavutil -o ffmpeg_g.exe ffmpeg.o cmdutils.o-Wl,--start-group -Llibavcodec -Llibavdevice -Llibavfilter -Llibavformat -Llibavutil

Re: [Mingw-w64-public] ffmpeg.c:4492: undefined reference to `_avdevice_register_all'

2011-09-10 Thread Kyle
On 9/10/2011 6:52 AM, PcX wrote: ? 2011/9/10 18:51, PcX ??: i686-w64-mingw32-gcc -Wl,--as-needed -Wl,--warn-common -Wl,-rpath-link=libpostproc:libswscale:libavfilter:libavdevice:libavformat:libavcodec:libavutil -o ffmpeg_g.exe ffmpeg.o cmdutils.o-Wl,--start-group -Llibavcodec -Llibavdevice -Llib

Re: [Mingw-w64-public] ffmpeg.c:4492: undefined reference to `_avdevice_register_all'

2011-09-10 Thread Kai Tietz
2011/9/10 Kyle : > On 9/10/2011 6:52 AM, PcX wrote: > > 于 2011/9/10 18:51, PcX 写道: > > i686-w64-mingw32-gcc -Wl,--as-needed -Wl,--warn-common > -Wl,-rpath-link=libpostproc:libswscale:libavfilter:libavdevice:libavformat:libavcodec:libavutil > -o ffmpeg_g.exe ffmpeg.o cmdutils.o -Wl,--start-group > -

Re: [Mingw-w64-public] ffmpeg.c:4492: undefined reference to `_avdevice_register_all'

2011-09-10 Thread Kyle Schwarz
On Sat, Sep 10, 2011 at 3:55 PM, Kai Tietz wrote: > 2011/9/10 Kyle : >> On 9/10/2011 6:52 AM, PcX wrote: >> >> 于 2011/9/10 18:51, PcX 写道: >> >> i686-w64-mingw32-gcc -Wl,--as-needed -Wl,--warn-common >> -Wl,-rpath-link=libpostproc:libswscale:libavfilter:libavdevice:libavformat:libavcodec:libavutil

Re: [Mingw-w64-public] ffmpeg.c:4492: undefined reference to `_avdevice_register_all'

2011-09-10 Thread Kyle
On 9/10/2011 11:29 PM, Kyle Schwarz wrote: > Thanks a lot for all the help, I'm glad I could get to the bottom of this. > > Any idea why it would only have this issue when SDL is found? I can > build a shared build without needing to edit the source at all, how > could finding SDL cause the symbo