Re: [Interest] Qt 6.2.2 Webassembly - sign conversion errors

2021-12-22 Thread Axel Spoerl
> Looks like your C++ library is incompatible with your C library. Indeed, that seems to be the case. > Please get a fixed SDK for your target. I using Qt 6.2.2 on OpenSuSE Leap 15.3. and emscripten version 2.0.14 as required according to the documentation. If I install and activate the current

Re: [Interest] Qt 6.2.2 Webassembly - sign conversion errors

2021-12-22 Thread Thiago Macieira
On Wednesday, 22 December 2021 12:07:17 -03 Axel Spoerl wrote: > /home/mnt/axel/CloudStation/download/emsdk/upstream/emscripten/cache/sysroot > / include/c++/v1/cmath:317:9: error: no member named 'signbit' in the global > namespace; did you mean '__signbit'? Looks like your C++ library is incompa

[Interest] Qt 6.2.2 Webassembly - sign conversion errors

2021-12-22 Thread Axel Spoerl
Hi, This is a copy of the following Qt forum entry: https://forum.qt.io/topic/132977/qt-6-2-2-webassembly-sign-conversion-errors/2[1] documentation[2]), I get a lot of signbit and type conversion errors. It looks to me that the 9er subtree (equivalent to /usr/include/c++/9) is not available in t

Re: [Interest] Android 11/SDK 30 file issues

2021-12-22 Thread Marek.Floriańczyk
Hi All Is this bug somehow related to this issue ? https://bugreports.qt.io/browse/QTBUG-97487 Best Regards Marek Dnia środa, 22 grudnia 2021 09:35:26 CET Andreas Buhr pisze: > Hi Philippe, > > On 21.12.21 21:40, maitai wrote: > > I have dug a lot today into it and my feeling is that it is not

Re: [Interest] Dumping compiler flags

2021-12-22 Thread Bob Hood
On 12/21/2021 8:43 AM, Konrad Rosenbaum wrote: Hi, On 21/12/2021 15:53, Bob Hood wrote: I seem to recall, in the dim, distant past, using a Qt utility (qmake?) to display the compiler flags that were used to build the Qt version.  Am I remember that correctly? If so, can somebody give me the c

Re: [Interest] Android 11/SDK 30 file issues

2021-12-22 Thread Andreas Buhr
Hi Philippe, On 21.12.21 21:40, maitai wrote: I have dug a lot today into it and my feeling is that it is not a qt bug. Even if it is not a Qt bug, Qt users are affected by it and it would be valuable to have one central point where we collect information about it. A bug entry on bugreports.