Opened 12 years ago

Closed 12 years ago

#33240 closed defect (fixed)

mupdf build makefile/makerules extraneous text after else directive

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

Description (last modified by mf2k (Frank Schima))

--->  Extracting mupdf-0.9-source.tar.gz
--->  Applying patches to mupdf
--->  Applying /opt/local/var/macports/sources/rsync.macports.org/release/tarballs/ports/graphics/mupdf/files/patch-Makerules.diff
patching file Makerules
--->  Configuring mupdf
--->  Building mupdf
make: Entering directory `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_graphics_mupdf/mupdf/work/mupdf-0.9'
Makerules:10: Extraneous text after `else' directive
Makerules:13: Extraneous text after `else' directive
Makerules:13: *** only one `else' per conditional.  Stop.
make: Leaving directory `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_graphics_mupdf/mupdf/work/mupdf-0.9'
shell command " cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_graphics_mupdf/mupdf/work/mupdf-0.9" && /usr/bin/make -w all " returned error 2
Error: Target org.macports.build returned: shell command failed (see log for details)
Warning: the following items did not execute (for mupdf): org.macports.activate org.macports.build org.macports.destroot org.macports.install

Attachments (2)

mupdf.zip (4.0 MB) - added by elr@… 12 years ago.
build directory and log
mupdf-gmake382.zip (4.5 KB) - added by elr@… 12 years ago.
log of build using gmake v 3.82

Change History (6)

Changed 12 years ago by elr@…

Attachment: mupdf.zip added

build directory and log

comment:1 Changed 12 years ago by mf2k (Frank Schima)

Description: modified (diff)
Port: 0.9 removed

comment:2 Changed 12 years ago by ryandesign (Ryan Carsten Schmidt)

Cc: ryandesign@… added
Keywords: tiger added

The log shows you are on Tiger, which is known to have an old version of GNU make. Try installing the gmake port. Then clean mupdf. Then try again. Does that work? If so, we can add the gmake dependency to mupdf on Tiger.

Changed 12 years ago by elr@…

Attachment: mupdf-gmake382.zip added

log of build using gmake v 3.82

comment:3 in reply to:  2 ; Changed 12 years ago by elr@…

Replying to ryandesign@…:

Unfortunately on tiger the /usr/bin/make is gnumake 3.80 (at least for 10.4.11). 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.

comment:4 in reply to:  3 Changed 12 years ago by ryandesign (Ryan Carsten Schmidt)

Resolution: fixed
Status: newclosed

Replying to 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.

Note: See TracTickets for help on using tickets.