[MacPorts] #33240: mupdf build makefile/makerules extraneous text after else directive

MacPorts noreply at macports.org
Sat Mar 3 21:43:57 PST 2012


#33240: mupdf build makefile/makerules extraneous text after else directive
---------------------------+------------------------------------------------
  Reporter:  elr@…         |       Owner:  macports-tickets@…                   
      Type:  defect        |      Status:  closed                               
  Priority:  Normal        |   Milestone:                                       
 Component:  ports         |     Version:  2.0.3                                
Resolution:  fixed         |    Keywords:  tiger                                
      Port:  mupdf         |  
---------------------------+------------------------------------------------
Changes (by ryandesign@…):

  * status:  new => closed
  * resolution:  => fixed


Comment:

 Replying to [comment:3 elr@…]:
 > Unfortunately on tiger the /usr/bin/make is gnumake 3.80 (at least for
 10.4.11).

 Right, that's what I was trying to say in my earlier comment.

 > In hope that
 > a more recent gmake would help, I tried the latest macport gmake (3.82)
 as well but that only
 > provoked early failures in the build. I have attached the logs. I had
 updated macports before
 > these attempts.

 Actually just installing the gmake port isn't enough; we also have to
 modify the mupdf port to tell it to use MacPorts' gmake instead of Xcode's
 older copy. I've verified that these changes allow the port to build on
 Tiger (ppc) and committed the fix in r90391 so you should be able to
 "`sudo port selfupdate`", "`sudo port clean mupdf`" and try again.

 The new log you attached shows this unrelated error:

 {{{
 :info:build /bin/sh: line 1: pkg-config: command not found
 }}}

 This is strange because the mupdf port does declare a dependency on the
 pkgconfig port so the `pkg-config` program should be there. Is the
 pkgconfig port installed? ("`port installed pkgconfig`") If so, is the
 `pkg-config` program present? ("`which pkg-config`") If so, does it work?
 (Run "`pkg-config`" which should respond "`Must specify package names on
 the command line`") If the pkgconfig port is not installed, install it. If
 it's installed but the `pkg-config` program is not present or does not
 work, uninstall and reinstall the pkgconfig port.

-- 
Ticket URL: <https://trac.macports.org/ticket/33240#comment:4>
MacPorts <http://www.macports.org/>
Ports system for Mac OS


More information about the macports-tickets mailing list