Opened 11 years ago
Closed 11 years ago
#40769 closed defect (duplicate)
port install dropPrivileges problem causes all builds to fail - Snow Leopard
| Reported by: | martini@… | Owned by: | macports-tickets@… |
|---|---|---|---|
| Priority: | Normal | Milestone: | |
| Component: | base | Version: | 2.2.0 |
| Keywords: | Cc: | ||
| Port: |
Description
New install of MacPorts 2.2.0 (via src tar.gz or .pkg) fail to allow building of any packages. The writing of any files or directories fails during port install. It doesn't matter if the install is done as root or an admin user with sudo, installs fail. I've confirmed this on two different Macs (both running Snow Leopard (10.6.8)) and many clean rebuilds. Pre-built packages install normally, but any builds fail.
Reproduce: 1) extract and install MacPorts-2.2.0.tar.gz (using ./configure ; make ; make install) as root or sudo 2) sudo port -d selfupdate 3) port -v install -s kermit (a small package with no dependancies) 4) build fails!
See attached files for session and logs.
I tried ./configure --with-macports-user=root --with-install-group=admin --with-install-user=root and again with my userid. All to no avail. I even tried to remove dropPrivileges in all of the tcl code; and I tried to disable the seteuid calls in the tcl and c.
Attachments (2)
Change History (4)
Changed 11 years ago by martini@…
| Attachment: | macports-2.2-fail.txt added |
|---|
comment:1 Changed 11 years ago by ryandesign (Ryan Carsten Schmidt)
| Component: | ports → base |
|---|---|
| Priority: | High → Normal |
I'm not sure why this is failing for you but it must be something unusual about the way you're installing MacPorts; it works fine for everybody else.
The MacPorts user should not be "root"; it should be a user with normal (not superuser) privileges, usually called "macports", to which MacPorts can drop to ensure that ports don't do things to your system that they're not supposed to do. I know the binary installer pkg will create this user for you if you don't already have it; I don't remember if building from source will do so. If you haven't ever used the binary installer, this might be the problem. You could use the binary installer, or manually create the "macports" user.
comment:2 Changed 11 years ago by larryv (Lawrence Velázquez)
| Resolution: | → duplicate |
|---|---|
| Status: | new → closed |
Your main.log indicates that your MacPorts prefix is symlinked (/opt/local to /opt/local/20131014, if I’m not mistaken), so this is probably a duplicate of #39850.
script of the seesion reproducing the errors