Opened 9 years ago

Closed 9 years ago

#32717 closed defect (invalid)

fontconfig@2.8.0.0 build failure

Reported by: daledouglas@… Owned by: macports-tickets@…
Priority: Normal Milestone:
Component: ports Version: 2.0.3
Keywords: Cc: ryandesign (Ryan Schmidt)
Port:

Description

Log attached

Attachments (1)

main.log (21.6 KB) - added by daledouglas@… 9 years ago.
fontconfig failed build log

Download all attachments as: .zip

Change History (2)

Changed 9 years ago by daledouglas@…

Attachment: main.log added

fontconfig failed build log

comment:1 Changed 9 years ago by ryandesign (Ryan Schmidt)

Cc: ryandesign@… added
Resolution: invalid
Status: newclosed

I see in the log:

fontconfig-2.8.0_0+universal.darwin_10.i386-ppc.tgz 

This shows that you are on Darwin 10, a.k.a. Snow Leopard, yet are for some reason trying to build universal for i386 & ppc. We don't support building for PowerPC on Snow Leopard because Snow Leopard does not run on PowerPC Macs.

It also shows your macports.conf contains outdated values, in particular portarchivetype tgz; the default these days is tbz2.

I also see:

:info:configure checking for pkg-config... /opt/local/bin/pkg-config
:info:configure checking pkg-config is at least version 0.9.0... dyld: Library not loaded: /opt/local/lib/libiconv.2.dylib
:info:configure   Referenced from: /opt/local/bin/pkg-config
:info:configure   Reason: Incompatible library version: pkg-config requires version 8.0.0 or later, but libiconv.2.dylib provides version 7.0.0
:info:configure ./configure: line 14631:   423 Trace/BPT trap          $PKG_CONFIG --atleast-pkgconfig-version $_pkg_min_version

This commonly means that your libiconv library is installed for the wrong architecture, for example is installed for ppc or i386 but you're now building for Snow Leopard's default architecture, x86_64.

All of the above suggest that you have migrated your MacPorts installation to this Snow Leopard Mac from a Mac with an earlier OS X version (or upgraded this Mac to Snow Leopard from an earlier OS X version) and did not follow the Migration procedure, so please follow it now.

Note: See TracTickets for help on using tickets.