This is the mail archive of the cygwin mailing list for the Cygwin project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: BFD 2.17.50 20061004 assertion fail


info@torsten-klinger wrote:

> when iam try to compile ffmpeg for wince with cegcc under cygwin i get this
> error:

> ove_extradata_bsf.o libavcodec/armv4l/dsputil_arm.o
> libavcodec/armv4l/mpegvideo_ arm.o libavcodec/armv4l/jrevdct_arm.o
> libavcodec/armv4l/simple_idct_arm.o libavc odec/armv4l/dsputil_arm_s.o
> libavutil/libavutil.so -lavutil -lm
  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

  This looks incorrect, listing the library both by its full path and as a -l
option will cause these multiple definition errors, but I can't guess how the
Makefile got that way; is there an ffmpeg group to ask about this?  Hmm, I
googled for "ffpmeg libavutil multiple definitions", and found a link:

http://www.mail-archive.com/libav-user@mplayerhq.hu/msg01661.html

that suggests you have to make sure your mingw runtime is up-to-date, and
(other post in same thread) that you might want to try adding
"--enable-shared" to your configure line.  Beyond that, I dunno, you'll have
to take it up on a suitable ffpmeg mailing list.

> 7 [main] ld 5096 _cygtls::handle_exceptions: Error while dumping state
> (probably corrupted stack)
> collect2: ld terminated with signal 11 [Segmentation fault], core dumped 
> libavutil/libavutil.so: In function `DllMainCRTStartup':
> /cygdrive/e/pedro/cegcc/0.50/src/mingw/dllcrt1.c:60: multiple definition of
> `Dll MainCRTStartup'
> /opt/mingw32ce/lib/gcc/arm-wince-mingw32ce/4.1.0/../../../../arm-wince-mingw32ce
>  /lib/dllcrt3.o:/cygdrive/e/pedro/cegcc/0.50/src/mingw/dllcrt1.c:60: first
> defined here
> /opt/mingw32ce/lib/gcc/arm-wince-mingw32ce/4.1.0/../../../../arm-wince-mingw32ce
>  /bin/ld: BFD 2.17.50 20061004 assertion fail
> /cygdrive/e/pedro/cegcc/0.50/src/binutils/bfd/coff-arm.c:2040

> What iam doing wrong? Is this a bug in ffmpeg, cygwin, cegcc or ld???

  Well, it's definitely a bug that LD crashed, even if presented with bad
data, and you should report that to the cegcc people.  On the other hand, I'm
confused by this:

>  /bin/ld: BFD 2.17.50 20061004 assertion fail

  That..... worries me.  Either the path /bin/ld is just displayed wrong, or
you've somehow overwritten your system native ld with the cegcc version?  When
you run "/bin/ld --version" at the command line, do you get 2.17.50?

    cheers,
      DaveK

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]