We are running a Jenkins-master on Windows Server with an iOS Job, which runs on a mac os x slave. The slave was running well on Mac OS X Yosemite but after upgrading to El Capitan, the build was broken.
The issue is that xcodebuild does not recognize our workspace file anymore: xcodebuild: error: './*****.xcworkspace' is not a workspace file.
When I execute this command from the command line with the Jenkins user, it succeeds.
Has anyone an idea how we can solve this issue?
It seems that xcodebuild can see the file because otherwise, it would say that ****.xcworkspace was not found.
We could only reproduce this issue, when ****.xcworkspace is a file and not a directory
We also checked permissions and encoding. I made also exact same clean setups of Yosemite and El Capitan. Yosemite works, and El Capitan does not work.
It was obvious an strange bug with El Capitan. After the upgrade to mac os sierra, it worked again.
Related
When installing cabal packages on OSX 10.11 El Capitan, I get a permission error even though I am using an administrator account.
cabal: /usr/bin/gcc: permission denied
Changing it with chmod command to +rw or adding my account to root group doesn't fix the permission error. I'm able to run gcc --version just fine.
After much searching and scouring through the interwebs, I stumbled upon a discussion over at Cabal issue tracker. Someone's answer mentioned the rootless feature with El Capitan causing problems.
Here's how to turn off the rootless feature.
Restart your machine. Press cmd+R until you see the apple logo
Open the terminal, by going to Utilities > Terminal
Type in csrutil disable; reboot and hit return
Wait for your osx to reboot itself and then proceed with continuing your cabal installation(s).
Reference:
Cabal Issue #2653 - ar permission errors on OS X 10.11 El Capitan with GHC 7.8.4
Quora - How do I turn off the rootless in OS X El Capitan 10.11?
OSX Daily - How to Disable System Integrity Protection (rootless) in OS X El Capitan
I just installed Aptana Studio 3 on my iMac running El Capitan. When I try to launch it, an alert pops up with this message:
The JVM shared library "/Library/Java/JavaVirtualMachines/jdk1.8.0_45.jdk/Contents/Home/bin/../jre/lib/server/libjvm.dylib" does not contain the JNI_CreateJavaVM symbol.
Is there any way to fix this?
-Sam
I found the solution at Aptana 3 wont start after OS-X El Capitan update
This is no longer an issue.
When I searched for a mac os x opengl tutorial and tried to build it, I got the following error message. I tried to change "OS X Deployment Target" to 10.10 Yosemite (which I am running), but it has no effect. I can't find any documentation online to explain what might be going wrong, nor could I find any tutorials about XCode 7. Any ideas on what I'm doing wrong?
"My Mac runs OS X 10.10.5, which is lower than tutorial01_first_window’s minimum deployment target. Change your project’s minimum deployment target or upgrade My Mac’s version of OS X."
Here is the original tutorial I downloaded and built with CMake according to the instructions:
http://www.opengl-tutorial.org/beginners-tutorials/tutorial-1-opening-a-window/
I ran into the exact same thing. I'm running 10.10.5 Yosemite and am using Xcode 7.0.1 with CMake 3.3.2 and it insisted on generating 10.11 deployment targets.
This answer is a bit dated, but it got me a long way towards a solution:
https://stackoverflow.com/a/26329890/2059999
I can get it to work by manually setting the OS X Deployment Target on the target binary in my project to 10.10, but CMake will clobber my change each time it gets re-run which is annoying.
I ran into this problem after a recent upgrade of Xcode (Version 7.0.1). It turns out that the default deployment target for it is OS X 10.11, which is higher than the one I have. The solutions above do work. However, to set this "permanently" in CMake, find the advanced option "CMAKE_OSX_DEPLOYMENT_TARGET" and set it to the one on your system, e.g. 10.10.
Setting CMAKE_OSX_DEPLOYMENT_TARGET
I was having this message with homebrew and updating Xcode from 7.3.1 to Xcode 8.1 fixed it
I updated my Xcode last night, and found I cannot run my code now. It shows: error: Could not resolve SDK path for 'macosx10.10'
My Xcode is version 7.0. And I'm using Qt on OS X 10.10.5. I didn't change anything, just updated the Xcode from App store.
Does anyone know how to fix it?
I think I found a solution from https://stackoverflow.com/questions/26320677/error-could-not-resolve-sdk-path-for-macosx10-8`.
I changed it to QMAKE_MAC_SDK = macosx10.11 and it works. But I don't know why here should be 10.11, as I'm using OS X 10.10.5. I just guess that the Xcode updated yesterday is used for new version of Mac OS called OS X el capitan.
Trying to install py2cairo-1.10.0 on Mac OS X 10.9. Configure went fine, then when I go to run $ ./waf build I get the following:
/usr/local/include/cairo/cairo-xlib.h:44:10: fatal error: 'X11/Xlib.h' file not found
I see from this question that I need to have X11 installed, but since X11 is no longer included with OS X, I can't use that solution. I do have the latest version of XQuartz installed, but that doesn't seem to help anything.
Does anyone know of a workaround for this? Thanks!
UPDATE: Build and install working fine now, but still can't get it to import. Any thoughts?