From: "d.henman" <dhenman@gmail.com>
To: <cygwin@cygwin.com>
Subject: RE: pangp
Date: Mon, 23 Jun 2008 18:43:00 -0000 [thread overview]
Message-ID: <20080623212037.2088@blackhawk> (raw)
In-Reply-To: Your message of Mon, 23 Jun 2008 09:42:19 +0100 <004001c8d50d$0be88ca0$2708a8c0@CAM.ARTIMI.COM>
Dave, thanks for your response.
None of the symbols:
`__pango_win32_font_get_type', `__pango_win32_font_map_get_type',
`__pango_win32_fontmap_cache_remove', and `__pango_win32_make_matching_logfontw'
are not in: "libpangowin32-1.0.dll.a" 's symbol table, or
are they in: "cygpangowin32-1.0-0.dll.def", or any other .def file.
but, they are in: "cygpangowin32-1.0-0.dll" as "T" symbols.
I wish I new more about the mechanics of this. Maybe a simple export in the file they are defined in would suffice to cure the problem?
regards,
henman
Dave Korn <dave.korn@artimi.com> wrote:
> d.henman wrote on 23 June 2008 09:32:
>> Re: Buiding Pango 1.21.3
>
> Take a look in the output of "nm ./.libs/libpangowin32-1.0.dll.a" and see
> if those symbols are there?
>
> cheers,
> DaveK
> --
> Can't think of a witty .sigline today....
> --
--
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-23 12:20 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 ` d.henman [this message]
2008-06-23 19:16 ` pangp Dave Korn
2008-06-23 20:26 ` pangp Yaakov (Cygwin Ports)
2008-06-24 3:34 ` pangp d.henman
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=20080623212037.2088@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).