Re: Master Build Failure in Python3 on Mac OSX with SDK 10.6 and XCode 4.5.2

Alexander Thurgood <alex.thurgood -AT- gmail.com>
Mon, 07 Jan 2013 16:50:44 +0100

Le 07/01/13 14:35, Alexander Thurgood a écrit :

I'm going to copy the XCode xcrun to /usr/bin and see if that makes a
difference, I've just noticed there's a difference in the dates of my
xcrun in /usr/bin and the one supplied with Xcode 4.5.2.


OK, so the copying of xcrun to /usr/bin got rid of my python3 build
error, the build then fails later on in tail_build with a segfault sig 11...

Alex

Context

Re: Master Build Failure in Python3 on Mac OSX with SDK 10.6 and XCode 4.5.2 · Tor Lillqvist
- Re: Master Build Failure in Python3 on Mac OSX with SDK 10.6 and XCode 4.5.2 · Alexander Thurgood
  - Re: Master Build Failure in Python3 on Mac OSX with SDK 10.6 and XCode 4.5.2 · Tor Lillqvist
    - Re: Master Build Failure in Python3 on Mac OSX with SDK 10.6 and XCode 4.5.2 · Alexander Thurgood
      - Re: Master Build Failure in Python3 on Mac OSX with SDK 10.6 and XCode 4.5.2 · Jonathan Aquilina
        
        Re: Master Build Failure in Python3 on Mac OSX with SDK 10.6 and XCode 4.5.2 · Tor Lillqvist
      - Re: Master Build Failure in Python3 on Mac OSX with SDK 10.6 and XCode 4.5.2 · Tor Lillqvist
        
        Re: Master Build Failure in Python3 on Mac OSX with SDK 10.6 and XCode 4.5.2 · Alexander Thurgood
        
        Re: Master Build Failure in Python3 on Mac OSX with SDK 10.6 and XCode 4.5.2 · Alexander Thurgood

Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.