How to switch linking from libc++ to libstdc++?

[DennisZhangOiler]

How to switch linking from libc++ to libstdc++?

[haohaolee]

As far as I know, zig needs a complicated config to link to libstdc++, you can refer to this issue (ziglang/zig#18300).
However, for zigbuild I am not sure if we can or want to support this case

[DennisZhangOiler]

As far as I know, zig needs a complicated config to link to libstdc++, you can refer to this issue (ziglang/zig#18300). However, for zigbuild I am not sure if we can or want to support this case

but it's pretty common issue, I met this issue on building opencv-rust crate.

[messense]

Not so common for most people who don't need to use opencv. :-)

[haohaolee]

The tricky part is, zig is used especially when you want a very convenient toolchain for cross compiling which includes all components, so you need nothing from the HOST. However, when you want to link to libstdc++, it definitely means you will rely on the HOST (or you need craft a libstdc++ sysroot on your own), which is not the target scenarios for zig cc I think.

It should be way easier to just use g++ on the host.

[DennisZhangOiler]

Got it, I thought it was easy to do it since it's just a linking tag, well it's not able to compile rust with g++, and it's not easy to control glibc version with g++, I can already build the program using cross but gilbc version was incorrect.

[haohaolee]

Got it, I thought it was easy to do it since it's just a linking tag, well it's not able to compile rust with g++, and it's not easy to control glibc version with g++, I can already build the program using cross but gilbc version was incorrect.

You are right that it is just linking and compiling tags, but it will involve something like -nostdinc++, -nostdlib++, and you need specify the libstdc++ libs yourself (which means you must have a copy of them)

And libstdc++ also relies on glibc versions at build time. A possible approach is to build a new gcc toolchain targeting a low version of glibc.