[lldb-dev] Build failure on OS X

[Greg Clayton]

I believe if you select "Current MacOSX" instead of the 10.9 SDK, you should be able to build. Or you can remove the Python.framework that is in the SDK. I believe the problem is there is a Python.framework in the SDK, but it is empty (no headers). If you remote the empty Python.framework from the SDK, it should fall back to the installed version.


On Nov 20, 2013, at 8:11 AM, Jean-Daniel Dupas <devlists at shadowlab.org> wrote:

> OK,
> 
> I finally try to build it too, and encounter the same issue. And the problem is in fact that the SDK sold with Xcode no longer provide the Python framework. 
> 
> See this tech note for details: https://developer.apple.com/library/mac/technotes/tn2328/_index.html
> 
> 
> Le 20 nov. 2013 à 09:46, Clayden, Jonathan <j.clayden at ucl.ac.uk> a écrit :
> 
>> Jean-Daniel,
>> 
>> Thanks for the reply. I do, however, already have the command-line tools installed.
>> 
>> Regards,
>> Jon
>> 
>> 
>>> On 20 Nov 2013, at 08:42, "Jean-Daniel Dupas" <devlists at shadowlab.org> wrote:
>>> 
>>> 
>>>> Le 19 nov. 2013 à 18:14, Clayden, Jonathan <j.clayden at ucl.ac.uk> a écrit :
>>>> 
>>>> Dear all,
>>>> 
>>>> I'm trying to build LLDB, and specifically the command line program, from the SVN trunk on OS X (10.9 + Xcode 5.0.2). The build instructions seem to suggest that this should be straightforward, but after selecting the "lldb-tool" scheme and starting the build as described, after a while I get a build failure with "'Python/Python.h' file not found', referring to the source file lldb-python.h.
>>>> 
>>>> I have installed Swig (via Homebrew), so as far as I know all dependencies should be met.
>>>> 
>>>> Apologies in advance if I've missed something obvious, but it's not clear to me how to proceed. Any help would be appreciated.
>>>> 
>>>> Regards,
>>>> Jon
>>> 
>>> 
>>> I didn't try yet to build it on Maverick, but do you have installed "command line tools" with Xcode ?
>>> This kind of error appears when some tools try to use the default search path for header instead of using the SDK distributed with Xcode. 
>>> The usual workaround is to install "command line tools" which provide these headers.
>>> 
>>> You can force installation of the "command line tools" by running the following in the terminal, and then choosing install in the dialog that appears.
>>> 
>>> xcode-select --install
>>> 
>>> Of course, a better solution would be to investigate and figure out what part of the build system relies on this header and fix it to properly use the Xcode SDK.
>>> 
>>> -- Jean-Daniel
>>> 
>>> 
>>> 
>>> 
>>> 
>> 
> 
> -- Jean-Daniel
> 
> 
> 
> 
> 
> _______________________________________________
> lldb-dev mailing list
> lldb-dev at cs.uiuc.edu
> http://lists.cs.uiuc.edu/mailman/listinfo/lldb-dev