From: Reini Urban <rurban@x-ray.at>
To: cygwin@cygwin.com
Subject: Re: GTK+ externals are unresolved
Date: Wed, 17 Dec 2008 19:26:00 -0000 [thread overview]
Message-ID: <49495236.6080407@x-ray.at> (raw)
In-Reply-To: <4948117F.6080208@users.sourceforge.net>
Yaakov (Cygwin/X) schrieb:
> Reini Urban wrote:
>> The order of libs is wrong for $(pkg-config --libs gtk+-2.0)
>>
>> -lgtk-x11-2.0 -lgdk-x11-2.0 should be at the end.
>>
>> $ pkg-config --libs gtk+-2.0
>> -L/usr/X11R6/lib -lgtk-x11-2.0 -lgdk-x11-2.0 -latk-1.0 -lgdk_pixbuf-2.0
>> -lpangoxft-1.0 -lXft -lfreetype -lz -lXrender -lXext -lfontconfig
>> -lpangox-1.0 -lX11 -lpango-1.0 -lm -lgobject-2.0 -lgmodule-2.0
>> -lglib-2.0 -lintl -liconv
>
> No, this is correct.
>
>> Windows need the libs in the correct order, i.e. backwards.
>
> No, the order is as with --as-needed on Linux, and in this case, where
> all those libs are shared, the order doesn't matter at all as long as
> they come after the object files which require them.
I tend to disagree.
With the original order:
-L/usr/X11R6/lib -lgtk-x11-2.0 -lgdk-x11-2.0 -latk-1.0 -lgdk_pixbuf-2.0
-lpangoxft-1.0 -lXft -lfreetype -lz -lXrender -lXext -lfontconfig
-lpangox-1.0 -lX11 -lpango-1.0 -lm -lgobject-2.0 -lgmodule-2.0
-lglib-2.0 -lintl -liconv
it fails to link, and with the reverse order of requires it works okay.
-L/usr/X11R6/lib -latk-1.0 -lgdk_pixbuf-2.0 -lpangoxft-1.0 -lXft
-lfreetype -lXrender -lXext -lfontconfig -lpangox-1.0 -lpango-1.0
-lgobject-2.0 -lgmodule-2.0 -lglib-2.0 -lgdk-x11-2.0 -lgtk-x11-2.0 -lX11
-lz -lintl -liconv
The windows linker doesn't allow unresolved symbols at linktime, the
linux linker does.
--
Reini
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
next prev parent reply other threads:[~2008-12-17 19:26 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-15 21:20 M.O.D.
2008-12-15 22:32 ` Greg Chicares
2008-12-16 0:15 ` M.O.D.
2008-12-15 22:45 ` John Emmas
2008-12-16 6:01 ` Andreas Eibach
2008-12-16 19:08 ` M.O.D.
2008-12-16 20:20 ` Reini Urban
2008-12-16 20:38 ` Yaakov (Cygwin/X)
2008-12-17 19:26 ` Reini Urban [this message]
2008-12-17 22:37 ` Yaakov (Cygwin/X)
2008-12-18 0:47 ` René Berber
2008-12-18 6:01 ` Yaakov (Cygwin/X)
2008-12-20 15:44 ` Reini Urban
2008-12-21 0:45 ` Yaakov (Cygwin/X)
2008-12-21 15:29 ` M.O.D.
2008-12-21 16:18 ` Yaakov (Cygwin/X)
2008-12-22 13:29 ` M.O.D.
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=49495236.6080407@x-ray.at \
--to=rurban@x-ray.at \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).