[MacPorts] #54368: Macports build doesn't work if spaces in Xcode path
MacPorts
noreply at macports.org
Fri Jun 23 16:10:58 UTC 2017
#54368: Macports build doesn't work if spaces in Xcode path
----------------------+-----------------
Reporter: mattvick | Owner:
Type: defect | Status: new
Priority: Normal | Milestone:
Component: ports | Version:
Keywords: | Port:
----------------------+-----------------
Macports build doesn't work if there are spaces in the Xcode path.
For example below is an error message from the macports:
{{{
$ sudo port upgrade outdated
---> Computing dependencies for ghostscript
---> Building ghostscript
Error: Failed to build ghostscript: command execution failed
Error: See
/opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_print_ghostscript/ghostscript/main.log
for details.
Error: Problem while installing ghostscript
}}}
The coresponding error in the ghostscript main.log:
{{{
:info:build /Applications/Xcode
8.2.1/Xcode.app/Contents/Developer/usr/bin/make -f Makefile so-subtarget
BUILDDIRPREFIX=so
:info:build make: /Applications/Xcode: No such file or directory
:info:build make: *** [so] Error 1
}}}
Perhaps this is documented somewhere but a better solution would be to
make Macports build work even if there are spaces in the Xcode path
--
Ticket URL: <https://trac.macports.org/ticket/54368>
MacPorts <https://www.macports.org/>
Ports system for macOS
More information about the macports-tickets
mailing list