gstreamer1 @1.8.2 uses gtk3, atk, gdk-pixbuf2 without declaring dependencies on them

[roberto.avanzi@…]

The summary says all. gstreamer1 1.8.2 does not build as of Monday, July 4th 2016. I attach the build log file

[roberto.avanzi@…]

This is the log file for port gstreamer1

[ryandesign (Ryan Carsten Schmidt)]

The log says the problem is:

:info:build ld: warning: ld: warning: ignoring file /opt/local/lib/libgtk-3.dylib, file was built for x86_64 which is not the architecture being linked (i386): /opt/local/lib/libgtk-3.dylibignoring file /opt/local/lib/libgdk-3.dylib, file was built for x86_64 which is not the architecture being linked (i386): /opt/local/lib/libgdk-3.dylib
:info:build
:info:build ld: warning: ignoring file /opt/local/lib/libatk-1.0.dylib, file was built for x86_64 which is not the architecture being linked (i386): /opt/local/lib/libatk-1.0.dylib
:info:build ld: warning: ignoring file /opt/local/lib/libgdk_pixbuf-2.0.dylib, file was built for x86_64 which is not the architecture being linked (i386): /opt/local/lib/libgdk_pixbuf-2.0.dylib

You are trying to build gstreamer1 universal, but it is trying to use libraries from gtk3, atk and gdk-pixbuf2 which were not built universal. This is unexpected, because gtk3, atk and gdk-pixbuf2 are not declared as dependencies of gstreamer1. If gstreamer1 requires those libraries, they should be added to its dependency list.

The log you attached is not from a ​clean build. Please clean the affected port and try again, then attach the new main.log so that we can see the output of the configure phase, which may say something about how gstreamer1 decided to use these unexpected libraries.

[roberto.avanzi@…]

Ok, I uninstalled the port, also issued "sudo port clean gstreamer1", and "sudo port install gstreamer1" worked flawlessly.

[roberto.avanzi@…]

Now I uninstalled and cleaned it again. Then told macports to BUILD it. I attach the second log as "main2.log"

[dbevans (David B. Evans)]

Replying to roberto.avanzi@…:

Now I uninstalled and cleaned it again. Then told macports to BUILD it. I attach the second log as "main2.log"

This log file appears to be that of a successful build on El Capitan. To confirm, I tried a local test build on El Capitan which was also successful. Whatever problem the reporter may have had seems to have been resolved by a clean rebuild.