On Wed, Jan 20, 2021 at 05:43:08PM +0100, Jean-Marc Lasgouttes wrote: > Le 20/01/2021 à 17:14, Scott Kostyshak a écrit : > > > > I've tried to reproduce on Linux with Clang and libc++ but cannot. > > > > However, one thing that I do not understand is that in the output from > > > > ldd, both libstdc++.so.6 and libc++.so.1 show up. See attached. Is this > > > > expected? > > > > > > I wonder if that may be a consequence of using DEBUG_GLIBC ... > > > > Good idea. I thought I had turned that off but maybe I missed something. > > Do you cuse autoconf? If you do, it should tell whether it uses libc++ or > libstdc++.
I use CMake. I should try with Autotools. I would be curious to see your ldd output for your binary if you've compiled with libc++. Does libstdc++ also show up in it? > When I compile with libc++ I have to use included libhunspell because the > std::string API is different. It took me a while to figure out this was going on, but Kornel helped fix things for the bundled Hunspell (even for the bundled Hunspell we were trying to link against the system Hunspell in CMake). I'm planning to search for materials to understand the std::string API. I'm confused as to why this only shows up when linking against libhunspell. Scott
signature.asc
Description: PGP signature
-- lyx-devel mailing list lyx-devel@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-devel
