#50013 closed defect (invalid)
gimp-app build fails: Could not find service "com.apple.CoreSimulator.CoreSimulatorService"
Reported by: | markb@… | Owned by: | dbevans (David B. Evans) |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | 2.3.4 |
Keywords: | Cc: | ||
Port: | gimp-app |
Description (last modified by dbevans (David B. Evans))
Building gimp-app on Mac OS X 10.11.2 fails with the following diagnostics:
:notice:build ---> Building gimp-app :debug:build Executing proc-pre-org.macports.build-build-0 :info:build Could not find service "com.apple.CoreSimulator.CoreSimulatorService" in domain for uid: 502 :info:build 2015-12-14 06:53:55.738 xcodebuild[64494:2953989] launchctl print returned an error code: 28928 :info:build 2015-12-14 06:53:55.738 xcodebuild[64494:2953989] Failed to locate a valid instance of CoreSimulatorService in the bootstrap. Adding it now. :info:build Could not find service "com.apple.CoreSimulator.CoreSimulatorService" in domain for uid: 502 :info:build 2015-12-14 06:53:56.640 xcodebuild[64494:2953989] launchctl print returned an error code: 28928 :info:build 2015-12-14 06:53:56.640 xcodebuild[64494:2953989] *** Assertion failure in -[SimServiceContext reloadServiceIfMovedOrAbortIfWeAreInvalid], /BuildRoot/Library/Caches/com.apple.xbs/Sources/CoreSimulator/CoreSimulator-201.3/CoreSimulator/SimServiceContext.m:451 :info:build ** INTERNAL ERROR: Uncaught exception ** :info:build Exception: Unable to lookup com.apple.CoreSimulator.CoreSimulatorService in the bootstrap. This can happen if running with a sandbox profile. When running with a sandbox profile, make sure that com.apple.CoreSimulator.CoreSimulatorService.xpc is owned by root, not group writable, and not world writable. See <rdar://problem/22142915>.
Attachments (1)
Change History (7)
Changed 9 years ago by markb@…
comment:1 Changed 9 years ago by dbevans (David B. Evans)
Description: | modified (diff) |
---|---|
Port: | gimp-app added |
Please use Wikiformatting for better readability when quoting terminal or log file contents. The Port: field should also be filled in with the name of the port exhibiting the reported issue. Thanks.
comment:2 Changed 9 years ago by dbevans (David B. Evans)
Owner: | changed from macports-tickets@… to devans@… |
---|---|
Status: | new → assigned |
This issue has been reported against a number of ports and has to do with permission problems when using Xcode 7.2. See the discussion in the ProblemHotlist for a possible fix.
comment:3 Changed 9 years ago by chicagotripp (Altoine Barker)
I can confirm that the solution for Build failures after upgrading to Xcode 7.2 from the ProblemHotlist provided by devans@… solves this problem for myself. I am running Mac OS 10.11.2 (El Capitan) on a MacBook Pro (Mid 2015) with MacPorts 2.3.4 (Binary Installation).
comment:4 Changed 9 years ago by info@…
The solution for Build failures after upgrading to Xcode 7.2 from the ProblemHotlist solved this for me.
Early 2011 MacBook Pro, El Capitan (OSX 10.11.2).
comment:5 Changed 9 years ago by info@…
I filed a bug report with Apple, issue # 24030591, Permissions error in XCode 7.2 installation.
comment:6 Changed 8 years ago by ryandesign (Ryan Carsten Schmidt)
Resolution: | → invalid |
---|---|
Status: | assigned → closed |
Has duplicate #50498.
Closing ticket because it's not a MacPorts bug; it's an Xcode bug.
Build log file