From: "d.henman" <dhenman@gmail.com>
To: <cygwin@cygwin.com>
Subject: Re: pangp
Date: Tue, 24 Jun 2008 03:34:00 -0000 [thread overview]
Message-ID: <20080624102459.3476@blackhawk> (raw)
In-Reply-To: Your message of Mon, 23 Jun 2008 13:43:34 -0500 <485FEED6.5000504@users.sourceforge.net>
Yaakov (Cygwin Ports) <yselkowitz@users.sourceforge.net> wrote:
> Dave Korn wrote:
> | So, they're in the DLL itself, but for some reason not marked as exports
> | in the DEF file, and hence no available stubs for them in the import .a
> | library.
>
> It's because of the -export-symbols-regex "^pango_.*" flag, hence
> _pango_* internal symbols aren't being exported. This isn't supposed to
> be used when building a Win32 Pango, as you'll see from the configure.in
> where this flag is declared; now you know why.
>
> My questions are:
> 1) What is /usr/local/bin/gcc that the OP is using?
/usr/local/bin/gcc is: gcc (GCC) 4.3.1 20080529 (prerelease)
I get the same results using cygin's
/bin/gcc (gcc 3.4.4 cygming special)
> 2) Has the OP built cairo from sources with the Win32 backend instead of
> the X11 as in our distro?
cairo 1.6.4 was configured as follows:
./configure CC=/usr/local/bin/gcc --with-x --prefix=
> I can attest that there are no issues building pango with the X11 cairo.
What version of pango are you talking about?
Doesn't using the configure option for cairo of "--with-x" build the X11 cairo?
> | A simple workaround might be to build with --disable-shared
> | --enable-static instead.
>
> NO, don't do that!! Pango must be built dynamic.
>
> | Hmmm. There's various pango and pang-devel packages in the distro. Do
> | you have any/all/none of those installed? Is this a source build from the
> | distro source tarballs, or are you trying the upstream sources?
>
> 1.21.3 is from SVN trunk; the latest upstream version is 1.20.3, also in
> Ports. It's irrelevant though, as this flag has been used for years.
>
> (Why isn't the distro Pango updated? X11R7.)
>
> Yaakov
> --
Regards,
Henman
--
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-06-24 1:25 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-23 8:48 pangp d.henman
2008-06-23 10:14 ` pangp Dave Korn
2008-06-23 18:43 ` pangp d.henman
2008-06-23 19:16 ` pangp Dave Korn
2008-06-23 20:26 ` pangp Yaakov (Cygwin Ports)
2008-06-24 3:34 ` d.henman [this message]
2008-06-24 15:15 ` pangp Yaakov (Cygwin Ports)
2008-06-24 9:40 ` pangp d.henman
2008-06-24 15:33 ` pangp Yaakov (Cygwin Ports)
2008-06-24 10:56 ` pangp d.henman
2008-06-24 17:41 ` pangp Yaakov (Cygwin Ports)
2008-06-25 2:55 ` pango d.henman
2008-06-24 14:55 ` pango solution d.henman
2008-06-24 15:12 ` Yaakov (Cygwin Ports)
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=20080624102459.3476@blackhawk \
--to=dhenman@gmail.com \
--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).