罗勇刚(Yonggang Luo) via llvm-dev
2016-Jun-28 16:50 UTC
[llvm-dev] The clang for centos6 are need GLIBC_2.14, but we only have GLIB 2.12 by default.
So CentOS before 6.7 is not an option after all? Is that possible to use clang on CentOS 6.6 and before? On Wed, Jun 29, 2016 at 12:48 AM, Brian Cain <brian.cain at gmail.com> wrote:> Yes, I believe it was built against centos 6.7. I wanted to build it > against an older release but couldn't quite bootstrap it without newer > libstdc++. > > Sorry, it would be clearer if I'd have made the package name include > "centos6.7". > > On Tue, Jun 28, 2016 at 11:43 AM, 罗勇刚(Yonggang Luo) < > llvm-dev at lists.llvm.org> wrote: > >> [root at localhost clang+llvm-3.8.0-linux-x86_64-centos6]# cd bin >> [root at localhost bin]# ./clang >> ./clang: /lib64/libc.so.6: version `GLIBC_2.15' not found (required by >> ./clang) >> ./clang: /lib64/libc.so.6: version `GLIBC_2.14' not found (required by >> ./clang) >> ./clang: /usr/lib64/libstdc++.so.6: version `GLIBCXX_3.4.14' not found >> (required by ./clang) >> ./clang: /usr/lib64/libstdc++.so.6: version `GLIBCXX_3.4.18' not found >> (required by ./clang) >> ./clang: /usr/lib64/libstdc++.so.6: version `CXXABI_1.3.5' not found >> (required by ./clang) >> ./clang: /usr/lib64/libstdc++.so.6: version `GLIBCXX_3.4.15' not found >> (required by ./clang) >> >> >> -- >> 此致 >> 礼 >> 罗勇刚 >> Yours >> sincerely, >> Yonggang Luo >> >> _______________________________________________ >> LLVM Developers mailing list >> llvm-dev at lists.llvm.org >> http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev >> >> > > > -- > -Brian >-- 此致 礼 罗勇刚 Yours sincerely, Yonggang Luo -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20160629/e81249ca/attachment.html>
Brian Cain via llvm-dev
2016-Jun-28 17:15 UTC
[llvm-dev] The clang for centos6 are need GLIBC_2.14, but we only have GLIB 2.12 by default.
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 -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20160628/62aa8902/attachment.html>
罗勇刚(Yonggang Luo) via llvm-dev
2016-Jun-28 17:44 UTC
[llvm-dev] The clang for centos6 are need GLIBC_2.14, but we only have GLIB 2.12 by default.
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>
罗勇刚(Yonggang Luo) via llvm-dev
2016-Jun-28 18:13 UTC
[llvm-dev] The clang for centos6 are need GLIBC_2.14, but we only have GLIB 2.12 by default.
Hell, Brian, I found a way to install Gcc 5.3 on CentOS 6 without the need to building it from source. You may try it on CentOS 6.0 That's makes clang/llvm won't depends on the newer version of glibc 2.14 The instruction: vim /etc/yum.repos.d/llvm.repo The content: ``` [sclo] name=SCLO baseurl=http://mirror.centos.org/centos/6/sclo/x86_64/rh/ gpgcheck=0 enabled=1 ``` Installation step: ``` yum clean all yum list echo y | yum install devtoolset-4 ``` 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/f6875c95/attachment.html>
Apparently Analagous Threads
- The clang for centos6 are need GLIBC_2.14, but we only have GLIB 2.12 by default.
- The clang for centos6 are need GLIBC_2.14, but we only have GLIB 2.12 by default.
- The clang for centos6 are need GLIBC_2.14, but we only have GLIB 2.12 by default.
- The clang for centos6 are need GLIBC_2.14, but we only have GLIB 2.12 by default.
- The clang for centos6 are need GLIBC_2.14, but we only have GLIB 2.12 by default.