#35910: Cannot build Macports in path containing spaces -------------------------------------+-------------------------------------- Reporter: cowwoc@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: base | Version: 2.1.1 Keywords: | Port: -------------------------------------+-------------------------------------- Changes (by ryandesign@…): * cc: cal@…, ryandesign@… (added) Old description:
1. Download Macports source tarball into a path containing spaces 2. Configure the environment and run make 3. The build will fail with numerous errors. For example:
{{{ checking that any existing MacPorts install can be upgraded... ./configure: line 10002: test: /Users/gili/.jenkins/workspace/GStreamer: binary operator expected yes ./configure: eval: line 10011: syntax error near unexpected token `(' ./configure: eval: line 10011: `prefix_expanded=/Users/gili/.jenkins/workspace/GStreamer (iOS)/client/ios/gstreamer/gstreamer/intermediate/macports' }}} or {{{ ===> making install in doc /usr/bin/install -c -d -o gili -g staff -m 0755 /Users/gili/.jenkins/workspace/GStreamer (iOS)/client/ios/gstreamer/gstreamer/intermediate/macports /bin/sh: -c: line 0: syntax error near unexpected token `(' }}}
New description: 1. Download Macports source tarball into a path containing spaces 2. Configure the environment and run make 3. The build will fail with numerous errors. For example: {{{ checking that any existing MacPorts install can be upgraded... ./configure: line 10002: test: /Users/gili/.jenkins/workspace/GStreamer: binary operator expected yes ./configure: eval: line 10011: syntax error near unexpected token `(' ./configure: eval: line 10011: `prefix_expanded=/Users/gili/.jenkins/workspace/GStreamer (iOS)/client/ios/gstreamer/gstreamer/intermediate/macports' }}} or {{{ ===> making install in doc /usr/bin/install -c -d -o gili -g staff -m 0755 /Users/gili/.jenkins/workspace/GStreamer (iOS)/client/ios/gstreamer/gstreamer/intermediate/macports /bin/sh: -c: line 0: syntax error near unexpected token `(' }}} -- Comment: Even if you can fix MacPorts itself to install in a path with spaces, likely many ports will fail to build in such a configuration. Years ago I reported this problem to the developers of autoconf, a configuration system used by many many ports, and the developers of autoconf said they had no plans to fix this issue and that it was a user error to attempt to use a path containing spaces. Therefore it seems unwise for us to attempt to support such a configuration either. Consequently, because we've been under the impression that we'll never run in a path with spaces, many many portfiles make that assumption as well. It would be a great deal of effort to fix this problem in all portfiles, for no discernible gain, since it's trivial for the user to choose to install MacPorts a different path that doesn't contain spaces. I would suggest closing this ticket as "wontfix". -- Ticket URL: <https://trac.macports.org/ticket/35910#comment:5> MacPorts <http://www.macports.org/> Ports system for Mac OS