#51142: ghostscript: build fails when Xcode.app is renamed so that it contains a space ----------------------------+-------------------------------- Reporter: steve.sisak@… | Owner: macports-tickets@… Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Resolution: invalid | Keywords: Port: ghostscript | ----------------------------+-------------------------------- Changes (by ryandesign@…): * status: new => closed * keywords: ElCapitan => * resolution: => invalid Old description:
I just attempted a clean install of MacPorts (never installed) then ImageMagick -- Xcode 7.3 release
Install failed with ghostscript, did a clean and reinstall of ghostscript alone
Install failed with:
MBP-R:~ sgs$ sudo port install ghostscript ---> Computing dependencies for ghostscript ---> Building ghostscript Error: org.macports.build for port ghostscript returned: command execution failed Please see the log file for port ghostscript for details: /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_print_ghostscript/ghostscript/main.log To report a bug, follow the instructions in the guide: http://guide.macports.org/#project.tickets Error: Processing of port ghostscript failed
New description: I just attempted a clean install of MacPorts (never installed) then ImageMagick -- Xcode 7.3 release Install failed with ghostscript, did a clean and reinstall of ghostscript alone Install failed with: {{{ MBP-R:~ sgs$ sudo port install ghostscript ---> Computing dependencies for ghostscript ---> Building ghostscript Error: org.macports.build for port ghostscript returned: command execution failed Please see the log file for port ghostscript for details: /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_print_ghostscript/ghostscript/main.log To report a bug, follow the instructions in the guide: http://guide.macports.org/#project.tickets Error: Processing of port ghostscript failed }}} -- Comment: This problem occurred because you renamed Xcode containing a space. Don't do that. Spaces in paths cause problems for lots of UNIX software. -- Ticket URL: <https://trac.macports.org/ticket/51142#comment:2> MacPorts <https://www.macports.org/> Ports system for OS X