[build] targeting different versions of libstdc++

classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

[build] targeting different versions of libstdc++

Boost - Dev mailing list
If I make a system with libstdc++6-dev, libstdc++7-dev, and libstdc++8-dev
on it, is there a way to tell clang to use one over the other?  By default
it will use the latest one.

I know that for linking one can use the clang flag
"--gcc-toolchain=/usr/lib/gcc/x86_64-linux-gnu/7" to get the link to point
at it, but I'm not sure if this also handles the header paths or not.

If this option works for both header inclusion and for linking, would I
need to specify it as <cxxflags> and also as <linkflags>?

Thanks,

Jim

_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
Reply | Threaded
Open this post in threaded view
|

Re: [build] targeting different versions of libstdc++

Boost - Dev mailing list
AMDG

On 11/16/2018 12:46 PM, James E. King III via Boost wrote:
> If I make a system with libstdc++6-dev, libstdc++7-dev, and libstdc++8-dev
> on it, is there a way to tell clang to use one over the other?  By default
> it will use the latest one.
>
> I know that for linking one can use the clang flag
> "--gcc-toolchain=/usr/lib/gcc/x86_64-linux-gnu/7" to get the link to point
> at it, but I'm not sure if this also handles the header paths or not.
>

No idea.  Intuitively, I would expect it to work, though.

> If this option works for both header inclusion and for linking, would I
> need to specify it as <cxxflags> and also as <linkflags>?
>

Yes.

In Christ,
Steven Watanabe

_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost