On Sat, Nov 19, 2022 at 04:56:04PM +0100, Jean-Marc Lasgouttes wrote: > Le 19/11/2022 à 01:50, Scott Kostyshak a écrit : > > On Fri, Nov 18, 2022 at 11:39:49PM +0100, Pavel Sanda wrote: > > > On Fri, Nov 18, 2022 at 04:23:43PM +0100, Jürgen Spitzmüller wrote: > > > > Am Donnerstag, dem 17.11.2022 um 19:21 +0100 schrieb Jean-Marc > > > > Lasgouttes: > > > > > You're right, I read to fast. So GCC ???11 is ok. > > > > > > > > I am not sure I understand. > > > > > > Andre references to Qt bug, which claims that it is underlying gcc > > > problem - > > > with another link to particular gcc bug. And that one claims to be fixed > > > with > > > milestone gcc 11. > > > > > > > I have gcc 12.2.1 and see the crash. > > > > > > Bummer. We either see different bug or the fix is not enough. > > > > Jürgen, can you compile with Clang to see if you can reproduce? > > > > In case you have never compiled with Clang before, I think it's > > sufficient to do the following: > > > > export CC="clang" > > export CXX="clang++" > > Last time I checked, clang++ used GNU stdlibc++. To use clang's libc++ > instead, I do: > > ../master/configure --with-version-suffix=-master 'CXX=clang++-14 > -stdlib=libc++'
Ah, thanks for this correction, JMarc! Scott
signature.asc
Description: PGP signature
-- lyx-devel mailing list lyx-devel@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-devel
