#49950 closed defect (worksforme)
MacVim @7.4.snapshot85: build fails due to permissions on com.apple.CoreSimulator.CoreSimulatorService.xpc
Reported by: | jianguohsiang82@… | Owned by: | raimue (Rainer Müller) |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | 2.3.4 |
Keywords: | Cc: | szhorvat (Szabolcs Horvát) | |
Port: | MacVim |
Description
See log file attached. Thank you.
Attachments (1)
Change History (9)
Changed 9 years ago by jianguohsiang82@…
comment:1 Changed 9 years ago by mf2k (Frank Schima)
Cc: | raimue@… removed |
---|---|
Owner: | changed from macports-tickets@… to raimue@… |
comment:2 follow-up: 7 Changed 9 years ago by raimue (Rainer Müller)
Status: | new → assigned |
---|---|
Summary: | Error installing MacVim → MacVim @7.4.snapshot85: build fails due to permissions on com.apple.CoreSimulator.CoreSimulatorService.xpc |
comment:4 follow-up: 8 Changed 9 years ago by sean@…
FYI, I'm having the same issue on Yosemite 10.10.5 with Xcode 7.2
> sw_vers ProductName: Mac OS X ProductVersion: 10.10.5 BuildVersion: 14F1021 > xcodebuild -version Xcode 7.2 Build version 7C68
The output of:
> ls -lad /Applications/Xcode.app/Contents/Developer/Library/PrivateFrameworks/CoreSimulator.framework/Versions/A/XPCServices/com.apple.CoreSimulator.CoreSimulatorService.xpc drwxrwxr-x 3 root wheel 102 Nov 10 05:21 /Applications/Xcode.app/Contents/Developer/Library/PrivateFrameworks/CoreSimulator.framework/Versions/A/XPCServices/com.apple.CoreSimulator.CoreSimulatorService.xpc/
which seems to match your output.
Against my better judgement, I ran:
sudo chmod 755 /Applications/Xcode.app/Contents/Developer/Library/PrivateFrameworks/CoreSimulator.framework/Versions/A/XPCServices/com.apple.CoreSimulator.CoreSimulatorService.xpc
And the build now succeeds. This seems like more than just a problem with the MacVim build, though.
comment:5 Changed 9 years ago by trond.kandal@…
This really beats me... How can a stricter access on the catalog allow to build MacVim? Shouldn't it be the opposite? I tested on my own computer too and it worked,- but it does not make sense to me.
comment:6 Changed 9 years ago by raimue (Rainer Müller)
Resolution: | → worksforme |
---|---|
Status: | assigned → closed |
I was able to reproduce the problem and the workaround also worked for me. Apparently it is an additional security check in Xcode 7.2 that checks the permissions on CoreSimulatorService.xpc and errors out if they are not strict enough. I doubt this is actually needed for building MacVim, but Xcode 7.2 wants this check to be satisfied.
This is now also documented in the ProblemHotlist. Since this is not a problem specific to MacVim only, I am closing this ticket.
comment:7 Changed 9 years ago by jianguohsiang82@…
Replying to raimue@…:
I do not have El Capitan available to test right now. Which permissions are set on this file? Please show me the output of this command:
ls -lad /Applications/Xcode.app/Contents/Developer/Library/PrivateFrameworks/CoreSimulator.framework/Versions/A/XPCServices/com.apple.CoreSimulator.CoreSimulatorService.xpc
I get the following:
drwxrwxr-x 3 root wheel 102 Nov 10 00:21 /Applications/Xcode.app/Contents/Developer/Library/PrivateFrameworks/CoreSimulator.framework/Versions/A/XPCServices/com.apple.CoreSimulator.CoreSimulatorService.xpc
This is actually against the requirements mentioned in the log above. Did you upgrade your Xcode and Command Line Tools to the latest version?
Yes
comment:8 Changed 9 years ago by eborisch (Eric A. Borisch)
Replying to sean@…:
Against my better judgement, I ran:
sudo chmod 755 /Applications/Xcode.app/Contents/Developer/Library/PrivateFrameworks/CoreSimulator.framework/Versions/A/XPCServices/com.apple.CoreSimulator.CoreSimulatorService.xpcAnd the build now succeeds. This seems like more than just a problem with the MacVim build, though.
For others hitting this, this resolved the issue for me as well.
I do not have El Capitan available to test right now. Which permissions are set on this file? Please show me the output of this command:
For reference, this is the output on my OS X 10.10 Yosemite.
This is actually against the requirements mentioned in the log above. Did you upgrade your Xcode and Command Line Tools to the latest version?