Opened 10 years ago
Closed 10 years ago
#46118 closed defect (fixed)
gmp pre-configure fails with "couldn't create error file for command"
Reported by: | mgs0lid_sn4ke@… | Owned by: | MarcusCalhoun-Lopez (Marcus Calhoun-Lopez) |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | 2.3.3 |
Keywords: | Cc: | jmroot (Joshua Root), ryandesign (Ryan Carsten Schmidt), neverpanic (Clemens Lang) | |
Port: | gmp |
Description
Hi,
I used macports in the past on this laptop and it worked fine. I had to reinstall it for several reasons. I am know in the process of reinstalling all the package I need.
I tried to run
sudo port install gmp
and I got the following output :
sudo port install gmp Password: ---> Configuring gmp Error: org.macports.configure for port gmp returned: couldn't create error file for command: permission denied Please see the log file for port gmp for details: /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_devel_gmp/gmp/main.log To report a bug, follow the instructions in the guide: http://guide.macports.org/#project.tickets Error: Processing of port gmp failed
I don't know why it says "permission denied" since i am using sudo.
can you help with this issue please ?
Thanks in advance.
Best, Thomas
Attachments (2)
Change History (7)
Changed 10 years ago by mgs0lid_sn4ke@…
comment:1 Changed 10 years ago by larryv (Lawrence Velázquez)
Cc: | jmr@… ryandesign@… cal@… added |
---|---|
Component: | ports → base |
Port: | gmp removed |
Summary: | can't install gmp using macports on Yosemite → gmp pre-configure fails with "couldn't create error file for command" |
comment:2 Changed 10 years ago by ryandesign (Ryan Carsten Schmidt)
Yes you are using sudo
, but MacPorts drops privileges to an unprivileged "macports" user. gmp's pre-configure block runs exec
. According to my Google search, the error message can occur when exec
tries to create a temporary file but does not have permission to do so, because the tmp directory is not world writable. The question is: which tmp directory—/tmp, /var/tmp, something in /var/folders? MacPorts creates a .tmp directory in the work directory, but Tcl might be using a different one; certainly the MacPorts-created one should have correct permissions. We've seen other errors before due to tmp directories in /var/folders mysteriously having wrong permissions, which were resolved by removing the offending directory and letting the system recreate it, possibly following a restart.
comment:3 Changed 10 years ago by jmroot (Joshua Root)
Component: | base → ports |
---|---|
Owner: | changed from macports-tickets@… to mcalhoun@… |
Port: | gmp added |
I can only assume config.guess is doing something that fails. I’ve addressed one possible failure mode in r129028, but I don’t know if that is actually your problem.
Changed 10 years ago by mgs0lid_sn4ke@…
Attachment: | main.2.log added |
---|
comment:4 Changed 10 years ago by mgs0lid_sn4ke@…
The new portfile r129028 did the job for gmp. Thanks. But i'm still having trouble with other ports. I tried to install gcc49 and during the installation of ld64, I go tthis output :
---> Building ld64 Error: org.macports.build for port ld64 returned: command execution failed Please see the log file for port ld64 for details: /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_devel_ld64/ld64/main.log To report a bug, follow the instructions in the guide: http://guide.macports.org/#project.tickets Error: Processing of port ld64 failed
But I may need to open another ticket for this.
comment:5 Changed 10 years ago by ryandesign (Ryan Carsten Schmidt)
Resolution: | → fixed |
---|---|
Status: | new → closed |
Yes please.
The error comes from the configure phase, which usually runs as an unprivileged user.
I’ve never seen this failure before, and I don’t know what this “error file” is.