[MacPorts] #39659: macports source build: ./configure --with-xxx-dir
#39659: macports source build: ./configure --with-xxx-dir ---------------------------------------+-------------------------------- Reporter: von.helmut@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Low | Milestone: Component: base | Version: 2.1.3 Keywords: source, configure, prefix | Port: ---------------------------------------+-------------------------------- `./configure --prefix=~/path/to/macports` installs to $HOME. This is reflected in the macports.conf file on the prefix line as `/Users/name/path/to/macports`. But on other _dir lines in the .conf file, the ~ is not expanded (in my case i specified `--with-applications-dir` and `--with-frameworks-dir` as `~/path/to/Applications`, `~/path/to/Frameworks`. I was installing libsdl, when it got to python27 it failed: `---> Staging python27 into destroot Error: org.macports.destroot for port python27 returned: command execution failed Error: Failed to install python27` the .conf files listed the prefix as /Users/name/path/to/macports, but applications_dir and frameworks_dir as ~/path/to/Applications, ~/path/to/Frameworks, respectively. These aren't expanded during port installation it seems. Updating the .conf files to absolute paths, port clean python27, port install libsdl did the trick, correctly installing without errors. I know it's up to the user when they start installing to other places, but perhaps this is somehow useful. Thanks. -- Ticket URL: <https://trac.macports.org/ticket/39659> MacPorts <http://www.macports.org/> Ports system for OS X
#39659: configure script does not expand "~" for applications_dir and frameworks_dir ---------------------------+-------------------------------- Reporter: von.helmut@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: base | Version: 2.1.3 Resolution: | Keywords: Port: | ---------------------------+-------------------------------- Changes (by larryv@…): * keywords: source, configure, prefix => * priority: Low => Normal Old description:
`./configure --prefix=~/path/to/macports` installs to $HOME. This is reflected in the macports.conf file on the prefix line as `/Users/name/path/to/macports`. But on other _dir lines in the .conf file, the ~ is not expanded (in my case i specified `--with-applications- dir` and `--with-frameworks-dir` as `~/path/to/Applications`, `~/path/to/Frameworks`.
I was installing libsdl, when it got to python27 it failed: `---> Staging python27 into destroot Error: org.macports.destroot for port python27 returned: command execution failed Error: Failed to install python27`
the .conf files listed the prefix as /Users/name/path/to/macports, but applications_dir and frameworks_dir as ~/path/to/Applications, ~/path/to/Frameworks, respectively. These aren't expanded during port installation it seems.
Updating the .conf files to absolute paths, port clean python27, port install libsdl did the trick, correctly installing without errors.
I know it's up to the user when they start installing to other places, but perhaps this is somehow useful. Thanks.
New description: `./configure --prefix=~/path/to/macports` installs to $HOME. This is reflected in the macports.conf file on the prefix line as `/Users/name/path/to/macports`. But on other _dir lines in the .conf file, the ~ is not expanded (in my case i specified `--with-applications-dir` and `--with-frameworks-dir` as `~/path/to/Applications`, `~/path/to/Frameworks`. I was installing libsdl, when it got to python27 it failed: {{{ ---> Staging python27 into destroot Error: org.macports.destroot for port python27 returned: command execution failed Error: Failed to install python27 }}} the .conf files listed the prefix as /Users/name/path/to/macports, but applications_dir and frameworks_dir as ~/path/to/Applications, ~/path/to/Frameworks, respectively. These aren't expanded during port installation it seems. Updating the .conf files to absolute paths, port clean python27, port install libsdl did the trick, correctly installing without errors. I know it's up to the user when they start installing to other places, but perhaps this is somehow useful. Thanks. -- -- Ticket URL: <https://trac.macports.org/ticket/39659#comment:1> MacPorts <http://www.macports.org/> Ports system for OS X
participants (1)
-
MacPorts