Opened 8 years ago

Last modified 3 years ago

#53584 new defect

failed to activate ghostscript

Reported by: mrkapqa Owned by:
Priority: Normal Milestone:
Component: ports Version: 2.4.0
Keywords: Cc: cooljeanius (Eric Gallager)
Port: ghostscript

Description

ttempting to fetch 0bdcfbe5e394d4519e5969918c34d4eebf76a386.zip from http://lil.fr.distfiles.macports.org/ghostscript
--->  Verifying checksums for ghostscript
--->  Extracting ghostscript
--->  Applying patches to ghostscript
--->  Configuring ghostscript
--->  Building ghostscript
--->  Staging ghostscript into destroot
--->  Installing ghostscript @9.19_0+x11
--->  Activating ghostscript @9.19_0+x11
Error: Failed to activate ghostscript: command execution failed

on imac g5 running leopard 10.5.8 with xcode 3.1.4 using

"sudo port install mpv +audiocd+bundle+dvd+libarchive+network+opengl+osdå+python27-rubberband+x11"

Attachments (1)

g5 (1.2 MB) - added by mrkapqa 8 years ago.

Download all attachments as: .zip

Change History (6)

Changed 8 years ago by mrkapqa

Attachment: g5 added

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

Keywords: mpv leopard ghostscript removed
Port: ghostscript added
Summary: mpv@leopard(ppc) - failed to activate ghostscriptfailed to activate ghostscript

In the future, please fill in the Port field with the port that actually fails to build and Cc that port's maintainers (port info --maintainers ghostscript), if any.

comment:2 Changed 8 years ago by mf2k (Frank Schima)

From the log, it stopped here:

:debug:activate system: /opt/local/bin/fc-cache -v /opt/local/share/fonts/Type1/gsfonts
:info:activate Command failed: /opt/local/bin/fc-cache -v /opt/local/share/fonts/Type1/gsfonts
:info:activate Killed by signal: 10

It was rebuilding the font cache which takes some time. Did you hit Control-C? How long did you wait before doing so?

comment:3 Changed 8 years ago by victorp-sg (Victor Pang)

:debug:activate activating file: /opt/local/share/man/man1/ps2pdf.1.gz
:debug:activate activating file: /opt/local/share/man/man1/ps2pdf12.1.gz
:debug:activate activating file: /opt/local/share/man/man1/ps2pdf13.1.gz
:debug:activate activating file: /opt/local/share/man/man1/ps2pdf14.1.gz
:debug:activate activating file: /opt/local/share/man/man1/ps2pdfwr.1.gz
:debug:activate activating file: /opt/local/share/man/man1/ps2ps.1.gz
:debug:activate activating file: /opt/local/share/man/man1/wftopfa.1.gz
:debug:activate Executing proc-post-org.macports.activate-activate-0
:debug:activate system: /opt/local/bin/fc-cache -v /opt/local/share/fonts/Type1/gsfonts
:info:activate Command failed: /opt/local/bin/fc-cache -v /opt/local/share/fonts/Type1/gsfonts
:info:activate Killed by signal: 10
:error:activate Failed to activate ghostscript: command execution failed
:debug:activate Error code: NONE
:debug:activate Backtrace: command execution failed
:debug:activate     while executing
:debug:activate "$post $targetname"
:debug:activate could not read "/opt/local/share/man/man1/wftopfa.1.gz": no such file or directory
:debug:activate     while executing
:debug:activate "::file type $file"
:error:activate See /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_print_ghostscript/ghostscript/main.log for details.

I have the exact same problem on a Power Mac G5 running Mac OS X 10.5.8 and the excerpt from the relevant section of the log file is shown above with, what looks like, the reason of the failure. Can it be related to the issue in Ticket #53669 where I have this same warning while installing?

--->  Applying patches to ghostscript
Warning: reinplace s|#!/usr/bin/perl|#!/opt/local/bin/perl| didn't change anything in /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_print_ghostscript/ghostscript/work/ghostscript-9.19/freetype_local/src/tools/afblue.pl
--->  Configuring ghostscript

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

Replying to victorp-sg:

the excerpt from the relevant section of the log file is shown above with, what looks like, the reason of the failure.

Unfortunately no; your log provides no additional information beyond what we already know: that fc-cache is being killed for some reason.

:debug:activate could not read "/opt/local/share/man/man1/wftopfa.1.gz": no such file or directory

This is not relevant or accurate. MacPorts uses an internal global variable to store the last error message. Some types of errors occur normally while MacPorts does its thing and it ignores them and moves on to other tasks. In this case, that other task had an error but it did not store the new error message in the global variable, so that when the value of the variable was printed out, you saw this older irrelevant error instead of the correct one. Unfortunately MacPorts base code is complex and I do not know where in the code we have neglected to fill the global variable with the correct error message.

Warning: reinplace s|#!/usr/bin/perl|#!/opt/local/bin/perl| didn't change anything in /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_print_ghostscript/ghostscript/work/ghostscript-9.19/freetype_local/src/tools/afblue.pl

This is not relevant to this issue.

comment:5 Changed 3 years ago by cooljeanius (Eric Gallager)

Cc: cooljeanius added
Note: See TracTickets for help on using tickets.