Re: pangp
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 d.henman wrote: | Regardless, make still prematurely terminates due to errors. | | Why is the pango build code trying to incorporate win32, when it is not in cairo? Did you ever delete the cairo-win32 headers and pkg-config file? Yaakov -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (Cygwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEAREIAAYFAkhhD4EACgkQpiWmPGlmQSP7SgCgod9tvznXwBA+o/yeXe0BXlVG eJwAoLvmaFDYaHojD43178z1GP11FL7R =gR5g -END PGP SIGNATURE- -- 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/
Re: pangp
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 d.henman wrote: | Yes, Dave is right here. His idea gives a way to building a multi-capable pango. Pango is always multi-capable, but cairo (and hence PangoCairo) cannot be both Win32 and X11. Simple as that. | YO, the configuration result is: | Cairo is configured and built with:--with-x | | So is Pango, in which its configuration script upon completion outputs: | configuration:backends: Cairo Win32 FreeType X | | Note, that is has Cairo, Win32, FreeType, and Win32 as backends. Yes, so do my pango builds. The question here is solely which *cairo* you are using. | So what you probably meant, when you said "was cairo built, explicitly exluding win32"... Which is probably neceesaary right? That's the only way to build an X11 cairo on Cygwin. | Well, the YO, is wrong here | "pango-1.21.3" was not gotten fron SVN's trunk. | Is is a newly released version. Not a release candidate, but a public release. GNOME uses the linux-kernel versioning system; odd-numbered minor versions are *development* releases, and is hence a snapshot from trunk. ~ The fact that it's been released as a tarball is irrelevant. The release announcement for 1.21 mentions this all quite clearly. Yaakov -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (Cygwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEAREIAAYFAkhhDwcACgkQpiWmPGlmQSMYuwCg+2lfOpYWIZNODmesPmlNLS8s ZAwAn29LlIne4veaYGnoZcr8sZMdpjSK =PUK7 -END PGP SIGNATURE- -- 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/
Re: pangp
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 d.henman wrote: | What version of pango are you talking about? I've been building cairo since 1.0.x *at least*, and these options have not changed. | Doesn't using the configure option for cairo of "--with-x" build the X11 cairo? Actually you need "--enable-xlib --disable-win32". Yaakov -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (Cygwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEAREIAAYFAkhhC+4ACgkQpiWmPGlmQSOuigCeIsniSgSreyX+8FLla7uwCKj4 RygAnRNI/Rtecnk8oUBTC8c12hMvjOk4 =9Mig -END PGP SIGNATURE- -- 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/
Re: pangp
Yaakov (Cygwin Ports) <[EMAIL PROTECTED]> wrote: > .. snipped > I can attest that there are no issues building pango with the X11 cairo. No I configured cairo with: ./configure --with-x --enable-win32-font=no --enable-win32=no --disable-ps --disable-pdf --disable-svg --prefix= cairo builds and installs fine this way. Pango, configured with: ./configure LDFLAGS='-no-undefined' --with-x --enable-win32-font=no --enable-win32=no --disable-ps --disable-pdf --disable-svg --prefix= # the only option above that pango mentiones in ./configure --help is "--with-x". Regardless, make still prematurely terminates due to errors. Why is the pango build code trying to incorporate win32, when it is not in cairo? (Still waiting to get Yaakov's two configuration options (two lines, one config line eac) uses for (1) cairo and (2) pango. to wit: last lines of "make" output for pango /bin/sh ../libtool --tag=CC --mode=compile /usr/local/bin/gcc -DHAVE_CONFIG_H -I. -I.. -DG_LOG_DOMAIN=\"Pango\" -DPANGO_ENABLE_BACKEND -DPANGO_ENABLE_ENGINE -DSYSCONFDIR=\"/etc\" -DLIBDIR=\"/lib\" -I.. -DPANGO_ENABLE_DEBUG -D_REENTRANT -I/usr/include/g lib-2.0 -I/usr/lib/glib-2.0/include-I/include/cairo -I/usr/include/freetype2 -I/usr/include/libpng12 -I/include/pixman-1 -I/usr/include/freetype2 -I/usr/X11R6/include-g -O2 -Wall -MT libpangocairo_1_0_la-pangocairo-win32font.lo -MD -MP -MF .deps/libpangocairo_1_0_la-pangocairo-win32font.Tpo -c -o libpangocairo_1_0_la-pangocairo-win32font.lo `test -f 'pangocairo-win32font.c' || echo './'`pangocairo-win32font.c /usr/local/bin/gcc -DHAVE_CONFIG_H -I. -I.. -DG_LOG_DOMAIN=\"Pango\" -DPANGO_ENABLE_BACKEND -DPANGO_ENABLE_ENGINE -DSYSCONFDIR=\"/etc\" -DLIBDIR=\"/lib\" -I.. -DPANGO_ENABLE_DEBUG -D_REENTRANT -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/inclu de/cairo -I/usr/include/freetype2 -I/usr/include/libpng12 -I/include/pixman-1 -I/usr/include/freetype2 -I/usr/X11R6/include -g -O2 -Wall -MT libpangocairo_1_0_la-pangocairo-win32font.lo -MD -MP -MF .deps/libpangocairo_1_0_la-pangocairo-win32font.Tpo -c p angocairo-win32font.c -DDLL_EXPORT -DPIC -o .libs/libpangocairo_1_0_la-pangocairo-win32font.o In file included from pangocairo-win32font.c:33: /include/cairo/cairo-win32.h:101:3: error: #error Cairo was not compiled with support for the win32 backend pangocairo-win32font.c: In function 'pango_cairo_win32_font_create_font_face': pangocairo-win32font.c:79: warning: implicit declaration of function 'cairo_win32_font_face_create_for_logfontw' pangocairo-win32font.c:79: warning: return makes pointer from integer without a cast pangocairo-win32font.c: In function 'pango_cairo_win32_font_create_metrics_for_context': pangocairo-win32font.c:122: warning: passing argument 1 of 'pango_cairo_font_get_scaled_font' from incompatible pointer type pangocairo-win32font.c:125: warning: implicit declaration of function 'cairo_win32_scaled_font_done_font' pangocairo-win32font.c: In function 'pango_cairo_win32_font_select_font': pangocairo-win32font.c:190: warning: implicit declaration of function 'cairo_win32_scaled_font_select_font' pangocairo-win32font.c: In function 'pango_cairo_win32_font_get_metrics_factor': pangocairo-win32font.c:207: warning: implicit declaration of function 'cairo_win32_scaled_font_get_metrics_factor' make[4]: *** [libpangocairo_1_0_la-pangocairo-win32font.lo] Error 1 make[4]: Leaving directory `/usr/src/pango/pango-1.21.3/pango' make[3]: *** [all-recursive] Error 1 make[3]: Leaving directory `/usr/src/pango/pango-1.21.3/pango' make[2]: *** [all] Error 2 make[2]: Leaving directory `/usr/src/pango/pango-1.21.3/pango' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/usr/src/pango/pango-1.21.3' make: *** [all] Error 2 end -- 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/
Re: pangp
Yaakov (Cygwin Ports) <[EMAIL PROTECTED]> 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. Yes, Dave is right here. His idea gives a way to building a multi-capable pango. > It's because of the -export-symbols-regex "^pango_.*" flag, hence > _pango_* internal symbols aren't being exported. Well, YO, could have said that he manually, exluded win32 in the configuration. > 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. Well Yaakov, you know why. I expected cairo and pango built a configuration of --with-x would be fine, and it should be. You neglected to mention that it was trying to build a win32 and cygwin.dll version at the same time, which it can't, as far as I know. So you explicity said to configure without win32. You are mentioning something that is esoteric. You mentioned below that... > My questions are: > 1) What is /usr/local/bin/gcc that the OP is using? YO, the gcc version used in not relavant in this case. I checked this. > 2) Has the OP built cairo from sources with the Win32 backend instead of > the X11 as in our distro? YO, the configuration result is: Cairo is configured and built with:--with-x So is Pango, in which its configuration script upon completion outputs: configuration:backends: Cairo Win32 FreeType X Note, that is has Cairo, Win32, FreeType, and Win32 as backends. Cairo builds these automatically. > I can attest that there are no issues building pango with the X11 cairo. So what you probably meant, when you said "was cairo built, explicitly exluding win32"... Which is probably neceesaary right? If you would please educate me as to just what arguments did you use, when you "configure"d cairo and pango, I could verify your aforementioned attestation. > 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 Well, the YO, is wrong here "pango-1.21.3" was not gotten fron SVN's trunk. Is is a newly released version. Not a release candidate, but a public release. See: http://www.pango.org/Download and from there http://ftp.gnome.org/pub/GNOME/sources/pango/ You can also find it at: http://ftp.gnome.org/pub/GNOME/sources/pango/1.21/ named appropriately as "LATEST-IS-1.21.316-Jun-2008..." 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/
Re: pangp
Yaakov (Cygwin Ports) <[EMAIL PROTECTED]> 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/
Re: pangp
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 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? 2) Has the OP built cairo from sources with the Win32 backend instead of the X11 as in our distro? I can attest that there are no issues building pango with 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 -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (Cygwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEAREIAAYFAkhf7tYACgkQpiWmPGlmQSOg7gCfe9qQ2usTHh7kKiWAv4f8bPQ4 1vMAn3e+KoxG7pw/HvfTXHxayrAD1i1+ =oAgA -END PGP SIGNATURE- -- 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/
RE: pangp
d.henman wrote on 23 June 2008 13:21: > 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. 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. A simple workaround might be to build with --disable-shared --enable-static instead. > 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? The DEF file is generated at this point in your make.out log: generating symbol list for `libpangowin32-1.0.la' /bin/nm -B .libs/module-defs-win32.o .libs/pangowin32.o .libs/pangowin32-fontcache.o .libs/pangowin32-fontmap.o | sed -n -e 's/^.*[ ]\([ABCDGIRSTW][ABCDGIRSTW]*\)[ ][ ]*_\([_A-Za-z][_A-Za-z0-9]*\)$/\1 _\2 \2/p' | /bin/sed -e '/^[BCDGRS][ ]/s/.*[ ]\([^ ]*\)/\1 DATA/' -e '/^[AITW][ ]/s/.*[ ]//' | sort | uniq > .libs/libpangowin32-1.0.exp /bin/grep -E -e "^pango_.*" ".libs/libpangowin32-1.0.exp" > ".libs/libpangowin32-1.0.expT" mv -f ".libs/libpangowin32-1.0.expT" ".libs/libpangowin32-1.0.exp" if test "x`/bin/sed 1q .libs/libpangowin32-1.0.exp`" = xEXPORTS; then cp .libs/libpangowin32-1.0.exp .libs/cygpangowin32-1.0-0.dll.def; else echo EXPORTS > .libs/cygpangowin32-1.0-0.dll.def; cat .libs/libpangowin32-1.0.exp >> .libs/cygpangowin32-1.0-0.dll.def; fi /usr/local/bin/gcc -shared .libs/cygpangowin32-1.0-0.dll.def .libs/module-defs-win32.o .libs/pangowin32.o .libs/pangowin32-fontcache.o .libs/pangowin32-fontmap.o ./.libs/libpango-1.0.dll.a -L/usr/lib /usr/lib/libgobject-2.0.dll.a /usr/lib/libgmodule-2.0.dll.a /usr/lib/libglib-2.0.dll.a /usr/lib/libintl.dll.a /usr/lib/libiconv.dll.a -lgdi32 -o .libs/cygpangowin32-1.0-0.dll -Wl,--enable-auto-image-base -Xlinker --out-implib -Xlinker .libs/libpangowin32-1.0.dll.a Creating library file: .libs/libpangowin32-1.0.dll.a You could take a look in the .libs/libpangowin32-1.0.exp; probably it doesn't contain anything that isn't also in .libs/cygpangowin32-1.0-0.dll.def, but it would be intersteing if it didn't. And it might be interesting to compare the nm output from those .o files before and after it gets passed through that sed|sort|uniq pipeline. Also, you should check that nothing went wrong at configure time that caused it to disable font support in the built code - maybe it couldn't find a dependency it needed. 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? 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/
RE: pangp
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 <[EMAIL PROTECTED]> 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/
RE: pangp
d.henman wrote on 23 June 2008 09:32: 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/
