Looks like OS X does not support thread local storage. I.e. __thread
causes an compile error and thus one would not need to use
--enable-threads or would need to disable them explicitely using
--disable-threads. Is this a known issue on OS X?

Cheers
Daniel

On Wed, Aug 10, 2011 at 12:53 AM, dsh <daniel.hais...@googlemail.com> wrote:
> Hi Jean-Sebastien Delfino,
>
> some things I noticed during the configure process (I am using MacPorts):
>
> * I think it would help to point out in the INSTALL file that mozjs
> can be downloaded at -> ftp://ftp.mozilla.org/pub/mozilla.org/js/
> * On OSX Lion xulrunner won't install from MacPorts and thus one would
> end up without a proper mozjs installation
> * If compiling mozjs from the prio mentioned URL, it ends up to be
> installed as /opt/local/lib/libmozjs185.1.0.0.dylib which causes the
> configure process to fail
> * I thus symlinked /opt/local/lib/libmozjs185.1.0.0.dylib to
> /opt/local/lib/libmozjs.dylib
> * The configure process is looking for -lapr-2 instead of -lapr-1 (I
> have APR 1.4.5_1 installed)
> * I thus had to symlink /opt/local/lib/libapr-1.0.dylib to
> /opt/local/lib/libapr-2.dylib
>
> If you like I could try to update the INSTALL document accordingly and
> attach the patch to a JIRA. I am doing the dependency setup in
> parallel on FreeBSD 8.2 to see whether I would run into similar issues
> (for instance the one of having a -lapr-1 installed instead of the
> expected -lapr-2). We could then decide whether we want to improve the
> auto* tools infrastructure or not (or even migrate to CMake).
>
> PS: I am planning to create a FreeBSD port for Apache Tuscany (native)
> cause I feel having to setup all of these dependencies is kind of
> daunting.
>
> Cheers
> Daniel
>
> On Mon, Aug 8, 2011 at 7:05 PM, Jean-Sebastien Delfino
> <jsdelf...@apache.org> wrote:
>> On Sun, Aug 7, 2011 at 6:35 PM, dsh <daniel.hais...@googlemail.com> wrote:
>>> Just a little update:
>>>
>>> OSX Lion with Xcode 4.1:
>>>
>>> * i686-apple-darwin11-llvm-gcc-4.2 (GCC) 4.2.1 (Based on Apple Inc.
>>> build 5658) (LLVM build 2335.15.00)
>>> * Apple clang version 2.1
>>>
>>> OSX Lion with Xcode 4.2:
>>>
>>> * i686-apple-darwin11-llvm-gcc-4.2 (GCC) 4.2.1
>>> * Apple clang version 3.0
>>>
>>> OSX Snow Leopard with Xcode 4.0.2:
>>>
>>> * i686-apple-darwin10-llvm-gcc-4.2 (GCC) 4.2.1
>>> * Apple clang version 2.0 based on LLVM 2.9svn
>>>
>>> PS: There exists an Apple Xcode version 4.2 for OSX Snow Leopard which
>>> we could use as a fallback if 4.0.2 turns out to be unusable
>>> PPS: I really love these virtualized OSX envs I setup recently because
>>> they allow to have all those different setups and configurations :)
>>>
>>> Cheers
>>> Daniel
>>>
>>
>> OK, here's what I'm using on OS X Lion:
>>
>> Xcode Version 4.1 Build 4B110
>>
>> macbook-air:~$ g++ --version
>> i686-apple-darwin11-llvm-g++-4.2 (GCC) 4.2.1 (Based on Apple Inc.
>> build 5658) (LLVM build 2335.15.00)
>>
>> macbook-air:~$ clang++ --version
>> Apple clang version 2.1 (tags/Apple/clang-163.7.1) (based on LLVM 3.0svn)
>> Target: x86_64-apple-darwin11.0.0
>> Thread model: posix
>>
>> --
>> Jean-Sebastien
>>
>

Reply via email to