[MacPorts] #17299: ffmpeg build fails: ld error (Undefined symbol): _dvbsub_decoder while installing gimp2

David Evans devans at macports.org
Tue Nov 18 10:11:17 PST 2008


>
> #17299: ffmpeg build fails: ld error (Undefined symbol): _dvbsub_decoder while
> installing gimp2
> ---------------------------------+------------------------------------------
>   Reporter:  hauriege1 at llnl.gov  |       Owner:  acho at macports.org
>       Type:  defect              |      Status:  new              
>   Priority:  Normal              |   Milestone:  Port Bugs        
>  Component:  ports               |     Version:  1.6.0            
> Resolution:                      |    Keywords:  gimp2            
>       Port:  ffmpeg              |  
> ---------------------------------+------------------------------------------
> Changes (by devans at macports.org):
>
>  * cc: acho at macports.org (removed)
>   * owner:  devans at macports.org => acho at macports.org
>
>
> Comment:
>
>  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.
>
>   
Wonder if someone who has access to a 10.4.11 intel system could look at
this and see if they
can reproduce the reported problem.  Works for me on 10.4.11 ppc.

Dave


More information about the macports-dev mailing list