Sorry for the duplicate posting but the last seemed to go out empty.
With the release of Xcode 4.2, we will have to be alert to package breakage
due to the newly enabled TLS support in clang under darwin11. This issue only
occurs on the darwin11 SDK using llvm.org's clang 2.9 or svn under Xcode
When Xcode 4.2 is released, we will need to be alert for new build problems
on 10.7 stable. The Xcode 4.2's clang compilers now use the new TLS support
in the darwin11 SDK (which wasn't the case for Xcode 4.1). This has already
been discovered to break libmpfr4. If your package fails to pass it's
Jack,
Thanks for bug-hunting this one. I've CCd myself on the bug, and
will also notify mpfr upstream of the issue so they are at least aware of
it.
Fang
> David,
> I have puzzled this one out. Comparing the config.log's generated by Xcode
> 4.1's clang and
> the fink llvm29 package
David,
I have puzzled this one out. Comparing the config.log's generated by Xcode
4.1's clang and
the fink llvm29 package's clang, I see...
-checking for TLS support... no
+checking for TLS support... yes
If I simply append --disable-thread-safe to ConfigureParams in libmpfr4.info, I
am able
On Mon, Oct 10, 2011 at 11:17:27PM -0600, David Palmer wrote:
> I did a survey of compilers to see what works and what doesn't.
>
> In the .info file, I changed the ../configure line to
> ../configure %c "CC=llvm-gcc -m64" "CXX=llvm-g++ -m64"
> --libdir='${prefix}/%lib'
> etc.
>
> llvm-gcc
On Mon, Oct 10, 2011 at 11:17:27PM -0600, David Palmer wrote:
> I did a survey of compilers to see what works and what doesn't.
>
> In the .info file, I changed the ../configure line to
> ../configure %c "CC=llvm-gcc -m64" "CXX=llvm-g++ -m64"
> --libdir='${prefix}/%lib'
> etc.
>
> llvm-gcc
