Bug #17528

OS X build issue and incompatibility with Xcode on Sierra?

Added by Tracy Usher over 3 years ago. Updated over 2 years ago.

Target version:
Start date:
Due date:
% Done:


Estimated time:
SSI Package:


When I try to attach Xcode to a running lar process it fails with indecipherable messages ("failed to send packet")... when I set up and try to launch lar from Xcode itself then for versions of lar that I build locally it fails with a message telling me that the build target version is above my current OS X version. This message is puzzling since I have the latest version of Sierra... (10.12.6). But when I use otool to look at the target version of lar it, indeed, tells me that it wants 10.12.7! It seems the build machines for distributed code are at 10.12.5, downloading those versions will work because the target version is 10.12.6 for them which is what I have.

It seems there is a compiler override that is getting set which is asking for the version to be 10.12.7, I found this in one of the cmake log files:
COLLECT_GCC_OPTIONS='-v' '-o' 'cmTC_ee9ec' '-mmacosx-version-min=10.12.7' '-asm_macosx_version_min=10.12' '-mtune=core2'

It would be nice if this could be fixed...


#1 Updated by Lynn Garren over 3 years ago

  • Status changed from New to Feedback

Does the resolution to #17529 also resolve this problem?

#2 Updated by Tracy Usher over 3 years ago

No this is a different issue in that it seems the OS X version is getting set one above the actual version of the installed operating system. It seems this is because there is a compiler directive setting this explicitly (see original message).

#3 Updated by Lynn Garren over 3 years ago

  • Project changed from LArSoft to cet-is
  • Category deleted (Install / build / code mgmt)

Tracy, which log file had that compiler directive? We need to know where to look for the problem.

#4 Updated by Kyle Knoepfel over 2 years ago

Tracy, this issue has been open for awhile. Is there still something that needs investigation or can we close it?

#5 Updated by Tracy Usher over 2 years ago

I have not had this problem recently (I'm using the most recent version of Xcode - 10.1). I do still have the issue with having to unsetup python before launching Xcode but have learned to live with that as an annoyance...

#6 Updated by Kyle Knoepfel over 2 years ago

  • Status changed from Feedback to Closed

Okay, based on your response we will close this issue. Unfortunately, there is not a straightforward solution to the Python issue. Thanks for bearing with that annoyance.

Also available in: Atom PDF