Opened 7 years ago

Closed 7 years ago

#54368 closed defect (wontfix)

Macports build doesn't work if spaces in Xcode path

Reported by: mattvick (Matthew Vickery) Owned by:
Priority: Normal Milestone:
Component: base Version:
Keywords: Cc:
Port:

Description

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

Change History (3)

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

Component: ports → base

comment:2 Changed 7 years ago by raimue (Rainer Müller)

Are you sure this is caused by MacPorts itself? This is most probably the Makefile rule expanding $CC without escaping the space. I expect almost all Makefiles to be written this way. If this is the case here, there is nothing base can do about it. Just avoid spaces in path names.

comment:3 Changed 7 years ago by ryandesign (Ryan Carsten Schmidt)

Resolution: → wontfix
Status: new → closed

User error. Don't do that.

Note: See TracTickets for help on using tickets.