After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 653312 - gst-plugins-base attempts to link against GTK X11 lib even with --disable-x
gst-plugins-base attempts to link against GTK X11 lib even with --disable-x
Status: RESOLVED NOTABUG
Product: GStreamer
Classification: Platform
Component: gst-plugins-base
0.10.35
Other Linux
: Normal minor
: NONE
Assigned To: GStreamer Maintainers
GStreamer Maintainers
Depends on:
Blocks:
 
 
Reported: 2011-06-24 07:24 UTC by Ben Klein
Modified: 2011-06-24 09:39 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
Related config.log (130.50 KB, text/plain)
2011-06-24 07:24 UTC, Ben Klein 		Details

Description Ben Klein 2011-06-24 07:24:09 UTC 
Created attachment 190563 [details]
Related config.log

I'm cross-compiling gstreamer on to an ARM-based embedded system that does not have X11. Obviously there is a problem with my pkg-config settings, as it shouldn't be picking up GTK at all, but I get the following error when configured with --disable-x

/usr/src/GPH_SDK/tools/gcc-4.2.4-glibc-2.7-eabi/bin/../lib/gcc/arm-gph-linux-gnueabi/4.2.4/../../../../arm-gph-linux-gnueabi/bin/ld: cannot find -lgtk-x11-2.0

I don't think it should be linking against any X11 libs if --disable-x is selected, even if that means also not building the GTK and/or QT related plugins.
Comment 1 Tim-Philipp Müller 2011-06-24 09:30:38 UTC 
Hrm, well, I understand the sentiment, but they're two separate things really, and it doesn't seem worthwhile or practical to me to hack around issues like this.

If configure detects gtk-x11 via pkg-config even though it's not available on the target, then you need to fix that (and most likely you have other bigger issues as well then, like drawing in platform-specific headers for a different platform).:

configure:23608: checking for GTK_X11
configure:23616: $PKG_CONFIG --exists --print-errors "gtk+-x11-$with_gtk >= $GTK_REQ"
configure:23619: $? = 0
configure:23634: $PKG_CONFIG --exists --print-errors "gtk+-x11-$with_gtk >= $GTK_REQ"
configure:23637: $? = 0
configure:23673: result: yes

> I don't think it should be linking against any X11 libs if --disable-x is
> selected, even if that means also not building the GTK and/or QT related
> plugins.

Neither GTK nor Qt necessarily imply X. Where we need Gtk-X11, we check for it explicitly. If that check fails because your environment isn't set up right, that's not really our problem, and checking explicitly for what one needs seems the right thing to do to me.

Hope you don't mind if I WONTFIX this.
Comment 2 Ben Klein 2011-06-24 09:39:33 UTC 
I understand your point. After all, this only came up because of problems with my build system. However, I argue that Gtk-X11 implies X, even if GTK does not.