Opened 11 years ago
Last modified 11 years ago
#39659 new defect
configure script does not expand "~" for applications_dir and frameworks_dir
Reported by: | von.helmut@… | Owned by: | macports-tickets@… |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | base | Version: | 2.1.3 |
Keywords: | Cc: | larryv (Lawrence Velázquez) | |
Port: |
Description (last modified by larryv (Lawrence Velázquez))
./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.
Change History (2)
comment:1 Changed 11 years ago by larryv (Lawrence Velázquez)
Description: | modified (diff) |
---|---|
Keywords: | source configure prefix removed |
Priority: | Low → Normal |
Summary: | macports source build: ./configure --with-xxx-dir → configure script does not expand "~" for applications_dir and frameworks_dir |
comment:2 Changed 11 years ago by larryv (Lawrence Velázquez)
Cc: | larryv@… added |
---|
Cc Me!