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 163913 - [CYGWIN] libgdk link failure
[CYGWIN] libgdk link failure
Status: RESOLVED OBSOLETE
Product: gtk+
Classification: Platform
Component: .General
2.6.x
Other Windows
: Normal normal
: ---
Assigned To: gtk-bugs
gtk-bugs
Depends on:
Blocks: 163914
 
 
Reported: 2005-01-13 09:41 UTC by Roger Leigh
Modified: 2012-03-20 03:50 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
gtk-2.6.0-gdk-Makefile.diff (1.07 KB, patch)
2005-01-13 09:42 UTC, Roger Leigh
none Details | Review
gtk-2.6.1-Makefile.diff (871 bytes, patch)
2005-01-13 10:04 UTC, Roger Leigh
none Details | Review

Description Roger Leigh 2005-01-13 09:41:23 UTC
Due to the logic in gdk/Makefile.am, when linking under Cygwin, both the UNIX
and Win32 libtool symbols export options are used.  libtool then has a fit (it
only handles one or the other, not both).  The attached patch rearranges the use
of $(LIBTOOL_EXPORT_OPTIONS) so that only one option is used at a time.

Regards,
Rogr
Comment 1 Roger Leigh 2005-01-13 09:42:53 UTC
Created attachment 35934 [details] [review]
gtk-2.6.0-gdk-Makefile.diff

Rearrange LIBTOOL_EXPORT_OPTIONS use.
Comment 2 Roger Leigh 2005-01-13 10:04:48 UTC
Created attachment 35936 [details] [review]
gtk-2.6.1-Makefile.diff

This libtool problem also applies to gtk/Makefile.am
Comment 3 Tor Lillqvist 2005-01-13 10:28:11 UTC
As the patch actually affects Unix builds (including Cygwin) and not mingw
builds at all (LIBTOOL_EXPORT_OPTIONS is empty for mingw builds), could somebody
else verify and apply, thanks? Changing component to general.
Comment 4 Gerrit P. Haase 2005-01-13 15:53:49 UTC
Please just make sure that the Win32 libtool symbols export options are not used
for Cygwin.

Gerrit
Comment 5 André Klapper 2006-10-07 15:55:41 UTC
roger, any news here? is this still an issue for gtk+-2.10?
Comment 6 Roger Leigh 2006-10-07 22:43:36 UTC
Andre,

I haven't used Cygwin in two years, so I'm afraid I don't know.  I no longer have any Windows systems to test on.  However, Cygwin now includes libgdk/libgtk as standard, so it may well be fixed, though I don't know if Cygwin has local patches which need merging upstream.

I think it's likely this can be closed, but it would need a test build of the vanilla distributed GTK+ tarball to verify that.


Regards,
Roger
Comment 7 Matthias Clasen 2012-03-20 03:50:32 UTC
whatever happened there is not long obsolete