[MacPorts] #38787: cairo 1.12.14 Build and install problems

MacPorts noreply at macports.org
Sat Apr 13 20:31:52 PDT 2013


#38787: cairo 1.12.14 Build and install problems
-------------------------+--------------------------
  Reporter:  ian.rees@…  |      Owner:  ryandesign@…
      Type:  defect      |     Status:  closed
  Priority:  Normal      |  Milestone:
 Component:  ports       |    Version:  2.1.3
Resolution:  fixed       |   Keywords:
      Port:  cairo       |
-------------------------+--------------------------

Comment (by ian.rees@…):

 Replying to [comment:7 ryandesign@…]:
 > Correct, lookup-symbol.c is not being compiled on my system.
 >
 > Comparing our logs, the significant difference seems to be:
 >
 > {{{
 > #!diff
 > --- main.log  2013-04-13 18:08:58.000000000 -0500
 > +++ main.log  2013-04-13 16:55:49.000000000 -0500
 > @@ -1005,12 +1001,15 @@
 >  :info:configure checking whether cairo's cairo-trace feature could be
 enabled... yes
 >  :info:configure checking for cairo's cairo-script-interpreter
 feature...
 >  :info:configure checking whether cairo's cairo-script-interpreter
 feature could be enabled... yes
 > -:info:configure checking for bfd_openr in -lbfd... no
 > -:info:configure checking libiberty.h usability... no
 > -:info:configure checking libiberty.h presence... no
 > -:info:configure checking for libiberty.h... no
 > +:info:configure checking for bfd_openr in -lbfd... yes
 > +:info:configure checking bfd.h usability... yes
 > +:info:configure checking bfd.h presence... yes
 > +:info:configure checking for bfd.h... yes
 > +:info:configure checking libiberty.h usability... yes
 > +:info:configure checking libiberty.h presence... yes
 > +:info:configure checking for libiberty.h... yes
 >  :info:configure checking for cairo's symbol-lookup feature...
 > -:info:configure checking whether cairo's symbol-lookup feature could be
 enabled... no (requires bfd)
 > +:info:configure checking whether cairo's symbol-lookup feature could be
 enabled... yes
 >  :info:configure checking for glib... yes
 >  :info:configure checking for shm_open in -lrt... (cached) no
 >  :info:configure checking for gtk... yes
 > @@ -1144,7 +1143,7 @@
 >  :info:configure   pthread:       yes
 >  :info:configure   gtk-doc:       no
 >  :info:configure   gcov support:  no
 > -:info:configure   symbol-lookup: no (requires bfd)
 > +:info:configure   symbol-lookup: yes
 >  :info:configure   test surfaces: no (disabled, use --enable-test-
 surfaces to enable)
 >  :info:configure   ps testing:    no (requires libspectre)
 >  :info:configure   pdf testing:   no (requires poppler-glib >= 99999)
 > }}}
 >
 > So your system has libiberty.h and libbfd.dylib, on the basis of which
 cairo has decided to enable the symbol-lookup feature, which then fails to
 compile. Where did these files come from on your system?
 Not sure honestly, it's entirely possible that they came from outside
 macports as egall suggested.  This computer has been used for cross-
 compiling to mingw32 and AVR, and I don't remember the details of getting
 that setup.
 >
 > Hopefully the problem is fixed by explicitly disabling the symbol lookup
 feature in r105226.
 >
 > Another difference I noticed by looking through our logs is that you're
 running the version of clang included with Xcode 4.2. Are you really still
 running Xcode 4.2? If so, please consider upgrading to Xcode 4.6.1. After
 upgrading Xcode, or if you've already upgraded Xcode, open the Xcode
 application, go to the Preferences window, to the Downloads section, and
 update the command line tools.
 Good catch, and thanks for the tip!  I had upgraded Xcode, and guess I had
 just assumed that would upgrade clang too.  Fixed now.

-- 
Ticket URL: <https://trac.macports.org/ticket/38787#comment:9>
MacPorts <http://www.macports.org/>
Ports system for OS X


More information about the macports-tickets mailing list