pango 1.30 cannot be installed

[an0nym@…]

*@* ~  $ sudo port clean pango
--->  Cleaning pango
*@* ~  $ sudo port install pango +no_x11 +quartz
--->  Computing dependencies for pango
--->  Fetching archive for pango
--->  Attempting to fetch pango-1.30.0_0+no_x11+quartz.darwin_11.x86_64.tbz2 from http://packages.macports.org/pango
--->  Fetching pango
--->  Verifying checksum(s) for pango
--->  Extracting pango
--->  Applying patches to pango
--->  Configuring pango
--->  Building pango
Error: Target org.macports.build returned: shell command failed (see log for details)
Log for pango is at: /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_x11_pango/pango/main.log
Error: Status 1 encountered during processing.
To report a bug, see <http://guide.macports.org/#project.tickets>

[an0nym@…]

Cc Me!

[Tom.Schoonjans@…]

Cc Me!

[macports1@…]

Cc Me!

[ryandesign@…]

In the future please remember to Cc the port's maintainer (in this case, me) so he sees the ticket and can begin to investigate...

[ryandesign@…]

I can confirm the problem on Snow Leopard i386, when using +quartz +no_x11. I have filed a ​bug report about this in the pango bug tracker.

[suv-sf@…]

Replying to ryandesign@…:

I can confirm the problem on Snow Leopard i386, when using +no_x11 +quartz as global variants.

Same build failure for pango 1.30.0 on Lion 10.7.2 (x86_64) when installing with +no_x11+quartz.

The workaround mentioned in related #32722 (comment 3) allowed to install it successfully - though I didn't further investigate what the linker flag does and why it apparently is (or was) required or not.

[suv-sf@…]

Cc Me!

[ryandesign@…]

Oh right. Thanks for reminding me of that earlier ticket.