New Ticket     Tickets     Wiki     Browse Source     Timeline     Roadmap     Ticket Reports     Search

Ticket #22801 (closed defect: fixed)

Opened 4 years ago

Last modified 4 years ago

pango, pango-devel +universal+no_x11+quartz fails to install on Snow Leopard x86_64

Reported by: steals.mail@… Owned by: ryandesign@…
Priority: Normal Milestone:
Component: ports Version: 1.8.1
Keywords: Cc: wiml@…, gvibe06@…, nicos_pavlov@…, wmatthews@…, boris.dusek@…, wyatt@…, geoffl@…, ToePeu@…, michaelld@…
Port: pango, pango-devel

Description (last modified by jmr@…) (diff)

can not instal pango with variants +universal+no_x11+quartz on Snow Leopard 10.6.2

Error: Target org.macports.destroot returned: /opt/local/lib/libpangocairo-1.0.la differs in /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_x11_pango/work/destroot-i386 and /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_x11_pango/work/destroot-x86_64 and cannot be merged
Error: Status 1 encountered during processing.

Attachments

gq crash details.txt (30.1 KB) - added by russell.jones@… 4 years ago.
"Problem Report for gq" Problem Details and System Configuration
archcheck.patch (750 bytes) - added by gvibe06@… 4 years ago.
patch that adds addition arch.check ... I am not the author.

Change History

comment:1 Changed 4 years ago by jmr@…

  • Keywords pango quartz x86_64 removed
  • Owner changed from macports-tickets@… to ryandesign@…
  • Description modified (diff)

comment:2 follow-up: ↓ 3 Changed 4 years ago by ryandesign@…

  • Status changed from new to assigned

I can confirm that the problem exists. On i386, libpangocairo-1.0.la wants to contain the line

inherited_linker_flags='  -framework CoreFoundation -framework Carbon -framework Cocoa'

while on x86_64 it wants to contain

inherited_linker_flags='  -framework Carbon'

This should fix itself when we upgrade pango to 1.26.x, because we then won't use the muniversal portgroup anymore. But we can't upgrade to 1.26.x right now because it causes problems.

For now, it looks like you cannot install pango 1.24.5 universal with quartz. I could possibly work around this by looking at how pango 1.26.0 generates its libpangocairo-1.0.la file when building universal with quartz, and apply that to 1.24.5's file.

comment:3 in reply to: ↑ 2 ; follow-ups: ↓ 6 ↓ 7 Changed 4 years ago by russell.jones@…

Replying to ryandesign@…:

This should fix itself when we upgrade pango to 1.26.x, because we then won't use the muniversal portgroup anymore. But we can't upgrade to 1.26.x right now because it causes problems.

For now, it looks like you cannot install pango 1.24.5 universal with quartz. I could possibly work around this by looking at how pango 1.26.0 generates its libpangocairo-1.0.la file when building universal with quartz, and apply that to 1.24.5's file.

I tried building 1.26.0 (may try 1.26.2 in a bit) using the Portfile attached to #21624, but I get the same error. I commented out the PortGroup muniversal 1.0 line and then pango and GTK2 built +no_x11 +quartz. I'm hoping to go on to build gq then to try to build workrave using the instructions here: http://old.nabble.com/How-I-got-1.9.0-compiled-on-Mac-OS-X-10.6-(-Snow-Leopard)-td25547590.html

I can't get openldap to build, which is unrelated, but is stopping me building gq to see if GTK2 works at all. After I've prodded about a bit I'll file a bug against the openldap port (I couldn't find anything like openldap +universal x86_64 fails to build )

comment:4 Changed 4 years ago by wiml@…

  • Cc wiml@… added

Cc Me!

comment:5 Changed 4 years ago by wiml@…

This is especially frustrating since, as far as I can tell, there's no reason to have any of those flags in there in the first place, because pangocairo is only used as a dylib. But libtool still doesn't understand how to make Mach-O dylibs, I guess?

comment:6 in reply to: ↑ 3 Changed 4 years ago by russell.jones@…

Replying to russell.jones@…:

I can't get openldap to build, which is unrelated

See #23300

comment:7 in reply to: ↑ 3 ; follow-up: ↓ 8 Changed 4 years ago by russell.jones@…

Replying to russell.jones@…:

Replying to ryandesign@…:

This should fix itself when we upgrade pango to 1.26.x, because we then won't use the muniversal portgroup anymore. But we can't upgrade to 1.26.x right now because it causes problems.

For now, it looks like you cannot install pango 1.24.5 universal with quartz. I could possibly work around this by looking at how pango 1.26.0 generates its libpangocairo-1.0.la file when building universal with quartz, and apply that to 1.24.5's file.

I tried building 1.26.0 (may try 1.26.2 in a bit) using the Portfile attached to #21624, but I get the same error. I commented out the PortGroup muniversal 1.0 line and then pango and GTK2 built +no_x11 +quartz. I'm hoping to go on to build gq then to try to build workrave using the instructions here: http://old.nabble.com/How-I-got-1.9.0-compiled-on-Mac-OS-X-10.6-(-Snow-Leopard)-td25547590.html

I can't get openldap to build, which is unrelated, but is stopping me building gq to see if GTK2 works at all. After I've prodded about a bit I'll file a bug against the openldap port (I couldn't find anything like openldap +universal x86_64 fails to build )

OK, Ryan Schmidt kindly fixed up the openldap port, so I could build gq with my altered portfile. It runs, but the underlined letters in the menus look odd, and it crashes a lot. I'll try with 1.26.2. (How does one compute rmd160 checksums?) Right, rebuilt pango. port doesn't seem to think gtk2 and gq need to be rebuilt.

I've attached the crash report details from when I press the "Options" button.

Changed 4 years ago by russell.jones@…

"Problem Report for gq" Problem Details and System Configuration

comment:8 in reply to: ↑ 7 ; follow-up: ↓ 10 Changed 4 years ago by ryandesign@…

Replying to russell.jones@…:

(How does one compute rmd160 checksums?)

openssl dgst -rmd160 filename

or perhaps you are looking for

port -d checksum portname

which will print for you the correct checksums line.

I've attached the crash report details from when I press the "Options" button.

I don't know how to help you with this. You may need to contact the authors of the software directly.

comment:9 Changed 4 years ago by russell.jones@…

Posted these details to #21624 where I probably should have put it in the first place.

comment:10 in reply to: ↑ 8 Changed 4 years ago by russell.jones@…

Replying to ryandesign@…:

Replying to russell.jones@…:

(How does one compute rmd160 checksums?)

openssl dgst -rmd160 filename

or perhaps you are looking for

port -d checksum portname

which will print for you the correct checksums line.

I've attached the crash report details from when I press the "Options" button.

I don't know how to help you with this. You may need to contact the authors of the software directly.

OK. Thanks again Ryan. I'll have a look at Gnome's Bugzilla.

comment:11 follow-up: ↓ 12 Changed 4 years ago by ryandesign@…

  • Cc gvibe06@… added
  • Port changed from pango to pango, pango-devel
  • Summary changed from pango +universal+no_x11+quartz fails to install on Snow Leopard x86_64 to pango, pango-devel +universal+no_x11+quartz fails to install on Snow Leopard x86_64

Has duplicate #23391.

comment:12 in reply to: ↑ 11 ; follow-up: ↓ 16 Changed 4 years ago by gvibe06@…

Replying to ryandesign@…:

Has duplicate #23391.

FYI .. the attached Patch seems to do the trick and allow pango-devel 1.25.6 to build and install with +no_x11 +quartz +universal.

Changed 4 years ago by gvibe06@…

patch that adds addition arch.check ... I am not the author.

comment:13 Changed 4 years ago by wmatthews@…

Disabling ATSUI (which was replaced by Core Text in 10.5, and which doesn't seem to have a 64bit version) seems to have solved the problem for me. My hack was to add the line

configure.args-append have_atsui=false

to the Portfile

comment:14 Changed 4 years ago by nicos_pavlov@…

  • Cc nicos_pavlov@… added

Cc Me!

comment:15 Changed 4 years ago by ryandesign@…

  • Cc wmatthews@… added

I am aware that the older ATSUI API has been replaced in Mac OS X 10.5 with the Core Text API. However, isn't the issue that Pango only knows how to use the ATSUI API, and contains no code for using the Core Text API? If so, and you disable ATSUI, what API is Pango using to render text?

comment:16 in reply to: ↑ 12 Changed 4 years ago by ryandesign@…

Replying to gvibe06@…:

Replying to ryandesign@…:

Has duplicate #23391.

FYI .. the attached Patch seems to do the trick and allow pango-devel 1.25.6 to build and install with +no_x11 +quartz +universal.

patch that adds addition arch.check ... I am not the author.

That patch to add the archcheck portgroup has absolutely nothing to do with the issue reported in this ticket, can in no way fix the problem, and was applied by me to the pango and pango-devel ports on December 23, 2009, in r61898.

comment:17 Changed 4 years ago by jeremyhu@…

I bumped pango-devel to 1.27.1 which contains a workaround to the blocker. Feel free to divorce from muniversal there.

comment:18 Changed 4 years ago by ryandesign@…

  • Cc boris.dusek@… added

Has duplicate #24385.

comment:19 Changed 4 years ago by wyatt@…

  • Cc wyatt@… added

Cc Me!

comment:20 follow-up: ↓ 21 Changed 4 years ago by n.a.hawes@…

For me the following worked. I first commented out the "muniversal 1.0 line". This then gave a linking error for atsui. This is already excluded for 64 bit builds, so I also excluded it for i386 build by changing the line

if {![variant_isset universal] && $build_arch == "x86_64" || $build_arch == "ppc64"} {
    configure.args-append have_atsui=false
}

to

if {![variant_isset universal] && $build_arch == "i386" || $build_arch == "x86_64" || $build_arch == "ppc64"} {
    configure.args-append have_atsui=false
}

Fingers crossed this actually runs ok.

comment:21 in reply to: ↑ 20 ; follow-up: ↓ 24 Changed 4 years ago by boris.dusek@…

Replying to n.a.hawes@…:

For me the following worked. I first commented out the "muniversal 1.0 line". This then gave a linking error for atsui. This is already excluded for 64 bit builds, so I also excluded it for i386 build Fingers crossed this actually runs ok.

Have you tested this? e.g. by running gtk-demo? I as well did try disabling atsui for i386, and gtk-demo displayed black-bordered box instead of every character, but I am not sure if this was to maybe missing fonts or some other setup issue (I had never run gtk-demo before). So could you please try gtk-demo and confirm characters are displayed OK?

comment:22 Changed 4 years ago by geoffl@…

  • Cc geoffl@… added

Cc Me!

comment:23 Changed 4 years ago by ToePeu@…

  • Cc ToePeu@… added

Cc Me!

comment:24 in reply to: ↑ 21 ; follow-up: ↓ 27 Changed 4 years ago by joe@…

Replying to boris.dusek@…:

Replying to n.a.hawes@…:

For me the following worked. I first commented out the "muniversal 1.0 line". This then gave a linking error for atsui. This is already excluded for 64 bit builds, so I also excluded it for i386 build Fingers crossed this actually runs ok.

Have you tested this? e.g. by running gtk-demo? I as well did try disabling atsui for i386, and gtk-demo displayed black-bordered box instead of every character, but I am not sure if this was to maybe missing fonts or some other setup issue (I had never run gtk-demo before). So could you please try gtk-demo and confirm characters are displayed OK?

After doing the above change, Pango compiles on Snow Leopard with +universal+no_x11+quartz, however I also get a black bordered box instead of every character. However without the above change, Pango will not compile for me.

comment:25 Changed 4 years ago by joe@…

  • Cc joe@… added

Cc Me!

comment:26 Changed 4 years ago by joe@…

  • Cc joe@… removed

Cc Me!

comment:27 in reply to: ↑ 24 ; follow-up: ↓ 28 Changed 4 years ago by joe@…

Replying to joe@…:

Replying to boris.dusek@…:

Replying to n.a.hawes@…:

For me the following worked. I first commented out the "muniversal 1.0 line". This then gave a linking error for atsui. This is already excluded for 64 bit builds, so I also excluded it for i386 build Fingers crossed this actually runs ok.

Have you tested this? e.g. by running gtk-demo? I as well did try disabling atsui for i386, and gtk-demo displayed black-bordered box instead of every character, but I am not sure if this was to maybe missing fonts or some other setup issue (I had never run gtk-demo before). So could you please try gtk-demo and confirm characters are displayed OK?

After doing the above change, Pango compiles on Snow Leopard with +universal+no_x11+quartz, however I also get a black bordered box instead of every character. However without the above change, Pango will not compile for me.

I noticed in the terminal window where I launched gtk-demo, I get the following.

(gtk-demo:79028): Pango-WARNING : shaping failure, expect ugly output. shape-engine='BasicEngineFc', font='Lucida Grande Medium 12', text='Application main window'

(gtk-demo:79028): Pango-WARNING : shaping failure, expect ugly output. shape-engine='BasicEngineFc', font='Bitstream Vera Sans 18', text='Application main window'

(gtk-demo:79028): Pango-WARNING : shaping failure, expect ugly output. shape-engine='BasicEngineFc', font='Bitstream Vera Sans Mono Oblique 12', text='#include <string.h>'

(gtk-demo:79028): Pango-WARNING : shaping failure, expect ugly output. shape-engine='BasicEngineFc', font='Bitstream Vera Sans Mono 12', text='enum'

(gtk-demo:79028): Pango-WARNING : shaping failure, expect ugly output. shape-engine='BasicEngineFc', font='Bitstream Vera Sans Mono Bold 12', text='"Red"'

I expect the issue to be a font issue. Will post back after I track those fonts down.

comment:28 in reply to: ↑ 27 Changed 4 years ago by joe@…

Replying to joe@…:

Replying to joe@…:

Replying to boris.dusek@…:

Replying to n.a.hawes@…:

For me the following worked. I first commented out the "muniversal 1.0 line". This then gave a linking error for atsui. This is already excluded for 64 bit builds, so I also excluded it for i386 build Fingers crossed this actually runs ok.

Have you tested this? e.g. by running gtk-demo? I as well did try disabling atsui for i386, and gtk-demo displayed black-bordered box instead of every character, but I am not sure if this was to maybe missing fonts or some other setup issue (I had never run gtk-demo before). So could you please try gtk-demo and confirm characters are displayed OK?

After doing the above change, Pango compiles on Snow Leopard with +universal+no_x11+quartz, however I also get a black bordered box instead of every character. However without the above change, Pango will not compile for me.

I noticed in the terminal window where I launched gtk-demo, I get the following.

(gtk-demo:79028): Pango-WARNING : shaping failure, expect ugly output. shape-engine='BasicEngineFc', font='Lucida Grande Medium 12', text='Application main window'

(gtk-demo:79028): Pango-WARNING : shaping failure, expect ugly output. shape-engine='BasicEngineFc', font='Bitstream Vera Sans 18', text='Application main window'

(gtk-demo:79028): Pango-WARNING : shaping failure, expect ugly output. shape-engine='BasicEngineFc', font='Bitstream Vera Sans Mono Oblique 12', text='#include <string.h>'

(gtk-demo:79028): Pango-WARNING : shaping failure, expect ugly output. shape-engine='BasicEngineFc', font='Bitstream Vera Sans Mono 12', text='enum'

(gtk-demo:79028): Pango-WARNING : shaping failure, expect ugly output. shape-engine='BasicEngineFc', font='Bitstream Vera Sans Mono Bold 12', text='"Red"'

I expect the issue to be a font issue. Will post back after I track those fonts down.

I found #20924 which seems to be what I have run into now. Also adding the above fonts has no effect.

comment:29 Changed 4 years ago by michaelld@…

  • Cc michaelld@… added

Cc Me!

comment:30 Changed 4 years ago by jmr@…

  • Status changed from assigned to closed
  • Resolution set to fixed
Note: See TracTickets for help on using tickets.