Opened 11 years ago

Closed 11 years ago

#38908 closed defect (fixed)

ffmpeg: build failure on ppc running osx 10.4

Reported by: jasper@… Owned by: dbevans (David B. Evans)
Priority: Normal Milestone:
Component: ports Version: 2.1.3
Keywords: Cc: jeremyhu (Jeremy Huddleston Sequoia)
Port: ffmpeg

Description (last modified by larryv (Lawrence Velázquez))

here is the session:

barbie:~ jaspert$ sudo port clean ffmpeg
--->  Cleaning ffmpeg
barbie:~ jaspert$ sudo port install ffmpeg
--->  Computing dependencies for ffmpeg
--->  Fetching archive for ffmpeg
--->  Attempting to fetch ffmpeg-1.2_1+gpl2.darwin_8.ppc.tbz2 from http://mse.uk.packages.macports.org/sites/packages.macports.org/ffmpeg
--->  Attempting to fetch ffmpeg-1.2_1+gpl2.darwin_8.ppc.tbz2 from http://lil.fr.packages.macports.org/ffmpeg
--->  Attempting to fetch ffmpeg-1.2_1+gpl2.darwin_8.ppc.tbz2 from http://packages.macports.org/ffmpeg
--->  Fetching distfiles for ffmpeg
--->  Verifying checksum(s) for ffmpeg
--->  Extracting ffmpeg
--->  Configuring ffmpeg
--->  Building ffmpeg
Error: org.macports.build for port ffmpeg returned: command execution failed
Please see the log file for port ffmpeg for details:
    /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_multimedia_ffmpeg/ffmpeg/main.log
To report a bug, follow the instructions in the guide:
    http://guide.macports.org/#project.tickets
Error: Processing of port ffmpeg failed

Attachments (2)

main.log (1.1 MB) - added by jasper@… 11 years ago.
log referenced in session
main2.log (290.7 KB) - added by jasper@… 11 years ago.
main.log using gcc-apple-4.2

Download all attachments as: .zip

Change History (11)

Changed 11 years ago by jasper@…

Attachment: main.log added

log referenced in session

comment:1 Changed 11 years ago by larryv (Lawrence Velázquez)

Cc: jeremyhu@… added
Description: modified (diff)
Owner: changed from macports-tickets@… to devans@…
Port: ffmpeg added
Summary: ffmpeg install fails on ppc running osx 10.4ffmpeg: build failure on ppc running osx 10.4

Thanks. In the future, please Cc relevant port maintainers, fill in the Port field, and use WikiFormatting in your ticket descriptions.

comment:2 Changed 11 years ago by jeremyhu (Jeremy Huddleston Sequoia)

:info:build /usr/bin/gcc-4.0 -dynamiclib -Wl,-single_module -Wl,-install_name,/opt/local/lib/libavdevice.54.dylib,-current_version,54.3.103 -Llibavcodec -Llibavdevice -Llibavfilter -Llibavformat -Llibavresample -Llibavutil -Llibpostproc -Llibswscale -Llibswresample -L/opt/local/lib -arch ppc  -Wl,-dynamic,-search_paths_first -o libavdevice/libavdevice.54.dylib libavdevice/alldevices.o libavdevice/avdevice.o libavdevice/lavfi.o libavdevice/sdl.o -lavfilter -lavformat -lavcodec -lavutil -liconv -ljack -L/opt/local/lib -lSDLmain -Wl,-framework,AppKit -lSDL -Wl,-framework,Cocoa -lxvidcore -lx264 -lvpx -lvpx -lvorbisenc -lvorbis -logg -ltheoraenc -ltheoradec -logg -lspeex -L/opt/local/lib -lschroedinger-1.0 -L/opt/local/lib -lopus -lopenjpeg -lmp3lame -lmodplug -L/opt/local/lib -lfreetype -lm -lbz2 -lz 
:info:build ld: warning can't open dynamic library: /opt/local/lib/libswresample.0.dylib referenced from: libavfilter/libavfilter.dylib (checking for undefined symbols may be affected) (No such file or directory, errno = 2)
:info:build ld: warning can't open dynamic library: /opt/local/lib/libpostproc.52.dylib referenced from: libavfilter/libavfilter.dylib (checking for undefined symbols may be affected) (No such file or directory, errno = 2)
:info:build ld: warning can't open dynamic library: /opt/local/lib/libswscale.2.dylib referenced from: libavfilter/libavfilter.dylib (checking for undefined symbols may be affected) (No such file or directory, errno = 2)

Please try:

sudo port -f uninstall ffmpeg
sudo port install ffmpeg

comment:3 Changed 11 years ago by jasper@…

Result is much the same:

barbie:~ jaspert$ grep "can't" /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_multimedia_ffmpeg/ffmpeg/main.log
:info:build ld: warning can't open dynamic library: /opt/local/lib/libswresample.0.dylib referenced from: libavfilter/libavfilter.dylib (checking for undefined symbols may be affected) (No such file or directory, errno = 2)
:info:build ld: warning can't open dynamic library: /opt/local/lib/libpostproc.52.dylib referenced from: libavfilter/libavfilter.dylib (checking for undefined symbols may be affected) (No such file or directory, errno = 2)
:info:build ld: warning can't open dynamic library: /opt/local/lib/libswscale.2.dylib referenced from: libavfilter/libavfilter.dylib (checking for undefined symbols may be affected) (No such file or directory, errno = 2)

comment:4 Changed 11 years ago by jeremyhu (Jeremy Huddleston Sequoia)

Hmm... then I wonder if this is an issue with Tiger's ancient linker not finding those in the build directories at link time. I see -Llibswresample in LDFLAGS and assume libswresample.0.dylib should be in there...

Try:

sudo port clean ffmpeg
sudo port install apple-gcc42
sudo port install ffmpeg configure.compiler=apple-gcc-4.2

comment:5 Changed 11 years ago by jasper@…

Already had apple-gcc42 installed -- result is a different error, see main2.log

Changed 11 years ago by jasper@…

Attachment: main2.log added

main.log using gcc-apple-4.2

comment:6 Changed 11 years ago by jeremyhu (Jeremy Huddleston Sequoia)

:info:build /usr/bin/ld: -i argument: nstall_name must have a ':' between its symbol names

It looks like you have apple-gcc42 installed with the +bootstrap variant. Please do:

sudo port install cctools
sudo port cctools
sudo port install ffmpeg configure.compiler=apple-gcc-4.2

comment:7 Changed 11 years ago by jasper@…

could not install cctools because it depended on ld64 which failed, see ticket 38931

comment:8 Changed 11 years ago by t.tensi@…

Dear Jasper,

as mentioned in ticket 38931, LD64 can be fixed to build on Tiger.

After that fix, the build for FFMPEG on Tiger works (at least for me).

Best regards, Thomas

comment:9 Changed 11 years ago by jeremyhu (Jeremy Huddleston Sequoia)

Resolution: fixed
Status: newclosed

Ok, so with #38931 resolved, it seems this should be resolved as well.

Note: See TracTickets for help on using tickets.