Displaying 2 results from an estimated 2 matches for "b3d89f73".
2016 Jun 29
0
The clang for centos6 are need GLIBC_2.14, but we only have GLIB 2.12 by default.
It is possible to statically link against libstdc++, yes. I don't quite
know all the pieces to the recipe in order to get that to work. It would
require changes to the release script in order to get those configuration
changes all the way through the third phase build.
I don't believe any other tarball release does this, so it would at least
be an unconventional release.
On Wed, Jun
2016 Jun 29
3
The clang for centos6 are need GLIBC_2.14, but we only have GLIB 2.12 by default.
Well, is that possible to include libstdc++4.7 into llvm?
On Wed, Jun 29, 2016 at 2:26 AM, Brian Cain <brian.cain at gmail.com> wrote:
> Sorry if I was unclear, I have no problems building clang against a newer
> gcc for my own purpose. But it doesn't make sense to provide a release
> binary for clang that's hosted on llvm.org that's ostensibly for
>