Descriptionclang/mac: Bundle libc++.dylib with clang.
clang now uses c++11, which on OS X means it depends on libc++.
OS X 10.6 doesn't have libc++ yet, but some bots still are on 10.6 and
upgrading them will take a bit longer. Bundle libc++ with the clang package,
and set rpaths so that both clang and plugins refer to the bundled libc++
instead of /usr/lib/libc++.1.dylib.
(System libraries will still cause libstdc++ to be loaded as well. Since libc++
keeps its symbols in std::__1:: and aliases everything to that, loading libc++
and libstdc++ in the same process is safe.)
Also don't set MACOSX_DEPLOYMENT_TARGET while building the bootstrap
compiler (Xcode's clang complains when using -stdlib=libc++ when targeting
10.6 or older; open-source luckily doesn't for some reason).
Also pass -isysroot; when building on OS X 10.9, /usr/include doesn't exist
unless the command line tools are installed.
BUG=358500
TEST=Run package.sh (with a tweaked clang revision, to not clobber an
existing package). Upload produced tgz file somewhere, download it on
a 10.6 box. Clang should run.
R=hans@chromium.org
Committed: https://src.chromium.org/viewvc/chrome?view=rev&revision=260908
Patch Set 1 #Patch Set 2 : whaat #Patch Set 3 : works? #Patch Set 4 : less hardcode #Patch Set 5 : maybe? #Patch Set 6 : . #Patch Set 7 : mac #Patch Set 8 : mac #Patch Set 9 : package #Patch Set 10 : ooops #Patch Set 11 : plugins #Patch Set 12 : clob #
Total comments: 2
Messages
Total messages: 4 (0 generated)
|