[llvm-dev] The clang for centos6 are need GLIBC_2.14, but we only have GLIB 2.12 by default.
罗勇刚(Yonggang Luo) via llvm-dev
llvm-dev at lists.llvm.org
Tue Jun 28 10:44:54 PDT 2016
It's possible to upgrade CentOS's gcc version from 4.6.1 to gcc 4.8.1 by
the following instructions:
```
wget -O /etc/yum.repos.d/slc6-devtoolset.repo
http://linuxsoft.cern.ch/cern/devtoolset/slc6-devtoolset.repo
wget -O /etc/pki/rpm-gpg/RPM-GPG-KEY-cern
http://ftp.scientificlinux.org/linux/scientific/5x/x86_64/RPM-GPG-KEYs/RPM-GPG-KEY-cern
yum clean all
yum list
echo y | yum install devtoolset-2
```
We have no need to upgrade gcc to the newest version(Gcc 6)
the GCC 5 or gcc 4.8.1 is enough to compile clang under centos
On Wed, Jun 29, 2016 at 1:15 AM, Brian Cain <brian.cain at gmail.com> wrote:
> On Tue, Jun 28, 2016 at 11:50 AM, 罗勇刚(Yonggang Luo) <luoyonggang at gmail.com
> > wrote:
>
>> So CentOS before 6.7 is not an option after all?
>> Is that possible to use clang on CentOS 6.6 and before?
>>
>>
> Not with these binaries, unless you can update your libc/libstdc++. In
> the general sense -- yes, it's possible if you build from source. There's
> a couple of potential approaches: build against libc++, build against newer
> libstdc++. If you're more adventurous you could also try building with
> ellcc. That one requires patches but will yield a statically linked binary.
>
> I built clang trunk/tip a few weeks ago on CentOS 6.0. But I first built
> the gcc6 suite, then used it to build clang. I believe clang 3.4.2 is the
> latest version that supports the older libstdc++. I ran into challenges
> with using clang so I stuck with gcc6. The resulting binaries depend on
> the gcc6 libraries so I can't really use this procedure to make a new
> official release for centos. If it's helpful I can publish the steps I
> used, but really just followed the build instructions.
>
> -Brian
>
--
此致
礼
罗勇刚
Yours
sincerely,
Yonggang Luo
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20160629/283650a5/attachment.html>
More information about the llvm-dev
mailing list