Thanks again chaps. gcc_select isn't available, and the installer continued to
grumble, but you got me headed in the right direction.
>From my notes:
The Python 3.2.2 package installer for OSX was compiled under a previous
version of Xtools that used ``gcc-4.2``. This can cause problems for
installers that rely on ``sysconfig.get_config_var('CC')`` to identify
the C-Compiler because ``gcc-4.2`` is not available from XCode 4.2
onward. Apple instead provides ``llvm-gcc-4.2`` and the improved
``clang`` 4.2.1, intended to replace ``gcc``.
In case anyone else hits this on their dev machines, I compiled Python with
clang:
$ ./configure \
> --prefix=/usr/local/python-3.2.2 \
> --enable-shared \
> CC=clang \
> MACOSX_DEPLOYMENT_TARGET=10.7
Python 3.2.2 (default, Mar 2 2012, 14:25:01) [GCC 4.2.1 Compatible Apple
Clang 3.0 (tags/Apple/clang-211.10.1)] on Darwin-11.3.0-x86_64-i386-64bit
Confirm Pyramid and uWSGI working.
I guess this isn't really a Python build issue as-such, but more of an issue
with how uWSGI locates the compiler on Darwin, and that Apple have phased out
gcc rather brutally.
On 29 Feb 2012, at 18:07, Simon Yarde wrote:
> Thanks Graham and Marius, much appreciated.
>
> I'll get stuck into this tomorrow and report back.
>
> On 29 Feb 2012, at 17:42, Graham Higgins <gjhigg...@gmail.com> wrote:
>
>> On Wednesday, February 29, 2012 5:01:38 PM UTC, Marius Gedminas wrote:
>> It's looking for libpython3.2m.so in $LD_LIBRARY_PATH.
>>
>> At least that's what it would be on Linux. I never worked on Mac OS X.
>>
>> It's $DYLD_LIBRARY_PATH on OS X
>>
>> so something like:
>>
>> DYLD_LIBRARY_PATH="/path/to/dircontaininglibpython3.2m.so:$DYLD_LIBRARY_PATH"
>>
>> should get you a bit further.
>>
>> You might want to check to see if "gcc_select" is an available command. If
>> so, that's a supported means of switching between gcc versions.
>>
>> (Apologies for being vague, the logic board on my PB is fried and I can't
>> decide whether to repair it or junk it).
>>
>> Cheers,
>>
>> Graham
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "pylons-discuss" group.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msg/pylons-discuss/-/KxUkE4GfcoAJ.
>> To post to this group, send email to pylons-discuss@googlegroups.com.
>> To unsubscribe from this group, send email to
>> pylons-discuss+unsubscr...@googlegroups.com.
>> For more options, visit this group at
>> http://groups.google.com/group/pylons-discuss?hl=en.
>
> --
> You received this message because you are subscribed to the Google Groups
> "pylons-discuss" group.
> To post to this group, send email to pylons-discuss@googlegroups.com.
> To unsubscribe from this group, send email to
> pylons-discuss+unsubscr...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/pylons-discuss?hl=en.
--
You received this message because you are subscribed to the Google Groups
"pylons-discuss" group.
To post to this group, send email to pylons-discuss@googlegroups.com.
To unsubscribe from this group, send email to
pylons-discuss+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/pylons-discuss?hl=en.
