#17299 closed defect (worksforme)
ffmpeg build fails: ld error (Undefined symbol): _dvbsub_decoder while installing gimp2
Reported by: | hauriege1@… | Owned by: | acho@… |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | 1.6.0 |
Keywords: | gimp2 | Cc: | dbevans (David B. Evans), ryandesign (Ryan Carsten Schmidt) |
Port: | ffmpeg |
Description (last modified by mf2k (Frank Schima))
During the installation of gimp2, I get a
ld: Undefined symbols: _dvbsub_decoder
error during building of ffmpeg. I attached the output of the error log.
Thanks!
Attachments (4)
Change History (15)
Changed 16 years ago by hauriege1@…
Changed 16 years ago by hauriege1@…
Attachment: | temp.2.txt added |
---|
comment:1 Changed 16 years ago by mf2k (Frank Schima)
Keywords: | gimp2 removed |
---|---|
Owner: | changed from macports-tickets@… to devans@… |
Assigning to maintainer.
comment:2 Changed 16 years ago by mf2k (Frank Schima)
Description: | modified (diff) |
---|
comment:3 Changed 16 years ago by dbevans (David B. Evans)
Cc: | acho@… added |
---|---|
Keywords: | gimp2 added; ffmpeg removed |
Port: | ffmpeg added; gimp2 removed |
Summary: | gimp2 installation: ld error (Undefined symbol): _dvbsub_decoder → ffmpeg build fails: ld error (Undefined symbol): _dvbsub_decoder while installing gimp2 |
While this occurred while installing gimp2, the problem appears to be with the build of ffmpeg so am Ccing its maintainer who may want to take over.
I tried a rebuild of ffmpeg (Tiger 10.4.11 ppc) last night and could not reproduce this error so more information is required.
- What version of OS X are you using and what architecture (ffmpeg has a lot of arch specific code)
- Can you clean your ffmpeg build and retry in debug mode, saving the output as follows:
sudo port clean --all ffmpeg sudo port -d install ffmpeg |& tee ffmpeg.log
and post this as an attachment to the ticket?
Thanks
Changed 16 years ago by hauriege1@…
Attachment: | ffmpeg.log added |
---|
comment:4 Changed 16 years ago by hauriege1@…
Thanks for getting back to me. I attached the log file. I have Mac OS X 10.4.11 with a 2.6 GHz Intel Core 2 Duo, 4 GB RAM. Thx,-Stefan
comment:5 Changed 16 years ago by dbevans (David B. Evans)
Cc: | acho@… removed |
---|---|
Owner: | changed from devans@… to acho@… |
Well, I'm confused now. This log shows an entirely different problem:
gcc-4.0 -DHAVE_AV_CONFIG_H -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_ISOC9X_SOURCE -I. -I"/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_multimedia_ffmpeg/work/trunk" -O2 -DHAVE_LRINTF -I/opt/local/include -pipe -force_cpusubtype_ALL -Wno-sign-compare -fomit-frame-pointer -g -Wdeclaration-after-statement -Wall -Wno-switch -Wdisabled-optimization -Wpointer-arith -Wredundant-decls -Wno-pointer-sign -Wcast-qual -Wwrite-strings -O3 -fno-math-errno -c -o libavcodec/h264.o libavcodec/h264.c In file included from libavcodec/h264.c:31: libavcodec/h264.h:365: error: parse error before 'CABACContext' libavcodec/h264.h:365: warning: no semicolon at end of struct or union
which again, I do not see here. The only difference is that I'm on ppc and you're on intel. This results in additional compile switches in my case to enable altivec and pic but I can't see why that would make a difference.
I guess it would be helpful if someone with the same configuration as you could confirm or deny the error to rule out something specific to your installation. In the meantime, you might want to go to the work directory and see if you can understand why this error is being generated.
cd /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_multimedia_ffmpeg/work/trunk
and look at avcodec/h264.h avcodec/h264.c etc.
Sorry I can't be more help right now. Will reassign to ffmpeg maintainer.
comment:6 Changed 16 years ago by dbevans (David B. Evans)
FYI, attaching build my successful build log (again 10.4.11 ppc) in case that might help someone.
Changed 16 years ago by dbevans (David B. Evans)
Attachment: | build.log.gz added |
---|
Successful build log from 10.4.11 ppc system
comment:7 follow-up: 8 Changed 16 years ago by ryandesign (Ryan Carsten Schmidt)
Cc: | devans@… ryandesign@… added |
---|
I haven't had a problem building ffmpeg on Mac OS X 10.4.11 Intel.
I see some differences between hauriege1's output and mine.
- His says:
debug symbols yes
Mine says nothing about debug symbols, yes or no.
- His says:
SDL support no
Mine says:
SDL support yes
ffplay ends up being linked to ${prefix}/lib/libSDL-1.2.0.dylib, which is part of the libsdl port. So ffmpeg should be changed, either to declare a dependency on libsdl or not to link with that library.
- His says:
libavcodec/h264.h:365: error: parse error before 'CABACContext'
And all the subsequent errors, and I don't know what that's about.
What version of Xcode do you have? If less than 2.4.1, please update to Xcode 2.4.1 or 2.5.
comment:8 Changed 16 years ago by hauriege1@…
I have Xcode 2.5. -Stefan
Replying to ryandesign@…:
I haven't had a problem building ffmpeg on Mac OS X 10.4.11 Intel.
I see some differences between hauriege1's output and mine.
- His says:
debug symbols yesMine says nothing about debug symbols, yes or no.
- His says:
SDL support noMine says:
SDL support yesffplay ends up being linked to ${prefix}/lib/libSDL-1.2.0.dylib, which is part of the libsdl port. So ffmpeg should be changed, either to declare a dependency on libsdl or not to link with that library.
- His says:
libavcodec/h264.h:365: error: parse error before 'CABACContext'And all the subsequent errors, and I don't know what that's about.
What version of Xcode do you have? If less than 2.4.1, please update to Xcode 2.4.1 or 2.5.
comment:9 Changed 16 years ago by dbevans (David B. Evans)
comment:10 Changed 16 years ago by dbevans (David B. Evans)
Resolution: | → worksforme |
---|---|
Status: | new → closed |
No response from reporter and works for me (and Ryan) on tiger. Assume problem resolved.
build log