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 125627 - Reconsider --export-dynamic in gmodule LDFLAGS
Reconsider --export-dynamic in gmodule LDFLAGS
Status: RESOLVED FIXED
Product: glib
Classification: Platform
Component: general
2.2.x
Other Linux
: Normal normal
: ---
Assigned To: gtkdev
gtkdev
Depends on:
Blocks:
 
 
Reported: 2003-10-27 20:02 UTC by Owen Taylor
Modified: 2011-02-18 16:09 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Owen Taylor 2003-10-27 20:02:07 UTC 
While if you use gmodule directly from the app, you probably
want the -Wl,--export-dynamic that 

 pkg-config --libs gmodule-2.0

produces, it's a bit dubious (and hurts performance) that
every app using Pango or GTK+ gets these flags.

Simple thing would be to add a gmodule-no-export-2.0.pc or
something like that that Pango, GTK+, etc. would require.

This would be a somewhat incompatible change to GTK+, but
probably OK to sneak in in 2.4. or 2.6.
Comment 1 Matthias Clasen 2004-11-17 04:49:38 UTC 
2004-11-16  Matthias Clasen  <mclasen@redhat.com>

	* m4macros/glib-2.0.m4 (AM_PATH_GLIB_2_0): Support gmodule-no-export.

	* Makefile.am (EXTRA_DIST): 
	* configure.in (AC_CONFIG_FILES): Add gmodule-no-export-2.0.pc.in 

	* gmodule-no-export-2.0.pc.in: Add a variants of gmodule-2.0.pc.in
	which doesn't add -Wl,--export-dynamic, since Pango or GTK+ don't
	need it.  (#125627, Owen Taylor)