Opened 12 years ago

Closed 7 years ago

#36211 closed defect (worksforme)

ccache: FATAL: Failed to create /opt/local/var/macports/build/.ccache/6/3: Permission denied

Reported by: bzbarsky (Boris Zbarsky) Owned by: macports-tickets@…
Priority: Normal Milestone:
Component: base Version: 2.1.2
Keywords: Cc: ryandesign (Ryan Carsten Schmidt), de5ton56@…, cooljeanius (Eric Gallager)
Port:

Description (last modified by ci42)

When I try to install any port, configure fails like so:

Error: org.macports.configure for port cairo returned: configure failure: command execution failed
Please see the log file for port cairo for details:
    /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_graphics_cairo/cairo/main.log
To report a bug, follow the instructions in the guide:
    http://guide.macports.org/#project.tickets
Error: Processing of port cairo failed

I've tried this for several different ports now, and all behave the same way.

Attachments (2)

main.log (51.9 KB) - added by bzbarsky (Boris Zbarsky) 12 years ago.
Log file
config.log (16.2 KB) - added by bzbarsky (Boris Zbarsky) 12 years ago.
The config.log too

Download all attachments as: .zip

Change History (18)

Changed 12 years ago by bzbarsky (Boris Zbarsky)

Attachment: main.log added

Log file

Changed 12 years ago by bzbarsky (Boris Zbarsky)

Attachment: config.log added

The config.log too

comment:1 Changed 12 years ago by bzbarsky (Boris Zbarsky)

Turning off ccache for macports does seem to fix this... See the permissions errors in the config.log.

comment:2 Changed 12 years ago by ci42

Description: modified (diff)
Priority: HighNormal

Please remember to use WikiFormatting and that priority 'high' is reserved for macports developers.

Do you get your repository from trunk? If so, please have a look at: http://lists.macosforge.org/pipermail/macports-dev/2012-September/020444.html

comment:3 Changed 12 years ago by ryandesign (Ryan Carsten Schmidt)

Cc: ryandesign@… added
Summary: Trying to install any port fails configure with MacPorts 2.1.2 on Mountain Lionccache: FATAL: Failed to create /opt/local/var/macports/build/.ccache/6/3: Permission denied

I was seeing this problem too.

comment:4 Changed 12 years ago by neverpanic (Clemens Lang)

comment:5 Changed 12 years ago by ben-macports@…

I was seeing this as well. Check the permissions in /opt/local/var/macports/build/.ccache I had:

/opt/local/var/macports/build/.ccache benc$ ls -ltra
total 8
-rw-r--r--   1 macports  admin   190 Aug 29  2011 CACHEDIR.TAG
drwxr-xr-x  20 macports  admin   680 Aug 29  2011 .
drwxr-xr-x  34 root      admin  1156 Sep 20 13:59 ..
drwxr-xr-x   8 root      admin   272 Sep 20 14:01 b
drwxr-xr-x  19 macports  admin   646 Sep 20 14:01 8

so that when any port tried to hit "b" it was getting a permissions error.

A "chown -R macports /opt/local/var/macports/build/.ccache" fixed the problem.

I am not sure how or when the problem started, possibly with the recent ccache update?

Last edited 12 years ago by ben-macports@… (previous) (diff)

comment:6 Changed 12 years ago by ryandesign (Ryan Carsten Schmidt)

Cc: de5ton56@… added

Has duplicate #36278.

comment:7 in reply to:  6 Changed 12 years ago by de5ton56@…

After "chown -R macports /opt/local/var/macports/build/.ccache" xkeyboard-config & xorg-server update fine. thanks alot.

comment:8 Changed 11 years ago by ryandesign (Ryan Carsten Schmidt)

Has duplicate #36403.

comment:9 Changed 11 years ago by ryandesign (Ryan Carsten Schmidt)

Has duplicate #36630.

comment:10 Changed 11 years ago by dave@…

This happens to me too, even after I completely remove /opt/local/var/macports/build/.ccache and start over. So I think there's a real problem here.

comment:11 Changed 11 years ago by ryandesign (Ryan Carsten Schmidt)

Has duplicate #37269.

comment:12 Changed 11 years ago by cooljeanius (Eric Gallager)

Cc: egall@… added

Cc Me!

comment:13 Changed 11 years ago by cooljeanius (Eric Gallager)

I think this might be related to #12218 (possibly)

comment:14 Changed 11 years ago by ryandesign (Ryan Carsten Schmidt)

How so? That's about trace mode (the "-t" flag) which we're not using here.

comment:15 in reply to:  14 Changed 11 years ago by cooljeanius (Eric Gallager)

Replying to ryandesign@…:

How so? That's about trace mode (the "-t" flag) which we're not using here.

Oh, I thought trace mode checked invalid permissions or something (idk, I'm not really that familiar with it)...

Last edited 11 years ago by cooljeanius (Eric Gallager) (previous) (diff)

comment:16 Changed 7 years ago by raimue (Rainer Müller)

Resolution: worksforme
Status: newclosed

This seems to have been resolved.

Note: See TracTickets for help on using tickets.