issue while building gdk-pixbuf on PPC

[Ryan Schmidt]

On Apr 20, 2018, at 01:17, Riccardo wrote:

> while installing gimp dependencies, on Leopart 10.5 PPC
> 
> --->  Building gdk-pixbuf2
> Error: Failed to build gdk-pixbuf2: command execution failed
> Error: See /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_graphics_gdk-pixbuf2/gdk-pixbuf2/main.log for details.
> 
> 
> there I see link errors:
> 
> :info:build /bin/sh ../libtool  --tag=CC   --mode=link /usr/bin/gcc-4.2 -arch ppc  -pipe -Os -arch ppc -Wall  -L/opt/local/lib -Wl,-headerpad_max_install_names -arch ppc -o pixbuf-read pixbuf-read.o ../gdk-pixbuf/libgdk_pixbuf-2.0.la -L/opt/local/lib -lgmodule-2.0 -lgio-2.0 -lgobject-2.0 -lglib-2.0 -lintl -Wl,-framework -Wl,CoreFoundation -lpng16    -L/opt/local/lib -lgobject-2.0 -lgmodule-2.0 -lgthread-2.0 -lglib-2.0 -lintl -Wl,-framework -Wl,CoreFoundation
> :info:build libtool: link: /usr/bin/gcc-4.2 /usr/bin/gcc-4.2 -arch ppc -pipe -Os -arch ppc -Wall -Wl,-headerpad_max_install_names -arch ppc -o .libs/pixbuf-read pixbuf-read.o -Wl,-framework -Wl,CoreFoundation -Wl,-framework -Wl,CoreFoundation  -L/opt/local/lib ../gdk-pixbuf/.libs/libgdk_pixbuf-2.0.dylib /opt/local/lib/libgio-2.0.dylib /opt/local/lib/libpng16.dylib /opt/local/lib/libgobject-2.0.dylib /opt/local/lib/libgmodule-2.0.dylib /opt/local/lib/libgthread-2.0.dylib /opt/local/lib/libglib-2.0.dylib /opt/local/lib/libintl.dylib
> :info:build ld: in /usr/bin/gcc-4.2, can't link with a main executable
> :info:build collect2: ld returned 1 exit status
> :info:build make[3]: *** [pixbuf-read] Error 1
> :info:build make[3]: Leaving directory `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_graphics_gdk-pixbuf2/gdk-pixbuf2/work/gdk-pixbuf-2.36.12/tests'
> 
> I attach the log.
> 
> is something not setup correctly on my side? Doing the "same" installs on 10.5 but on x86 worked.

It builds fine for us on our PowerPC Leopard buildbot worker. We distribute a binary of it; I'm not sure why you didn't receive it.

Do you have the ld64 port installed? If not, try that. It provides a newer linker.