Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - Paul Smedley

Pages: 1 2 [3] 4 5 ... 171
31
Programming / Re: Qt6 Application Testing
« on: May 07, 2025, 12:22:41 pm »
I do plan on rebuilding the webengine with GCC 15, but this may take a few days - depending how many times the build machine runs out of memory.

The build went surprisingly smoothly. (link removed) contains a rebuilt webengine from Qt 6.2.6.

Unfortunately, on my machine at least, I'm getting a 'Limit access fault' with simplebrowser.exe and dooble just closes.

<sigh> life wasn't meant to be easy. Will investigate tomorrow, but curious if it's something local (I've installed a bunch of yum updates recently)

32
Programming / Re: Qt6 Application Testing
« on: May 07, 2025, 10:12:14 am »
Thanks Paul - every QT6 app I've tried works just fine with this build! Haven't tried any examples yet though...

Thanks David, there weren't significant changes between 6.2.11 and 6.2.12, so I wouldn't expect behaviour to be too different.

33
Programming / Re: Qt6 Application Testing
« on: May 05, 2025, 10:58:47 am »
Webengine is unchanged from the January release, but the remaining Qt6 components are updated to Qt 6.2.12 LTS. https://smedley.id.au/tmp/qt6-6.2.12-qtwebengine-6.2.6-os2-20250505.zip This is also built with GCC 15.1.0

I do plan on rebuilding the webengine with GCC 15, but this may take a few days - depending how many times the build machine runs out of memory.

34
Programming / Re: Qt6 Development
« on: May 04, 2025, 10:44:04 pm »
Well surprise, surprise, qt 6.8 is still failing with:
Code: [Select]
Assertion failed: _UM_CRUMB_STATUS (crumb) == _UMS_FREE, file ./libc-0.1.13/src/emx/src/lib/malloc/ifree.c, line 30

TRP attached. I should probably do a debug build to make the TRP more useful. I'll have to dust my notes off from when I was last conversing with Steven around this TRP.

35
Programming / Re: Qt6 Development
« on: May 04, 2025, 11:56:25 am »
FWIW - currently updating main to 6.2.12 and 6.8.x to 6.8.3.... Seems it's been 3 months since I touched Qt.... using GCC 15.1.0 to build.

36
Programming / Re: GCC - updates
« on: May 04, 2025, 08:43:01 am »
Turns out I had an updated qt6core.dll built, I just guess I didn't package it up. https://smedley.id.au/tmp/qt6-6.2.x-qt6core-20250204.zip

37
Programming / Re: GCC - updates
« on: May 04, 2025, 08:06:43 am »
I fixed a similar TRP in qmake for Qt 6.8 - never seen it before in 6.2.x... Interestingly, the TRP looks similar to the one in Qt 6.8.x - perhaps its some kind of compiler optimisation issue?

Edit: I think https://github.com/psmedley/qt6-base-os2/commit/528a156563fee77b310f8bd120c7a7f9178fb802 might be the fix for this. I don't think this fix has made it into a public build. Perhaps rebuild qt6core.dll if you can locally and see if it helps.

38
Programming / Re: GCC - updates
« on: May 04, 2025, 07:48:47 am »
even better - then you do'nt have to keep removing it :)

39
Programming / Re: GCC - updates
« on: May 04, 2025, 07:38:00 am »
Are you also updating Qt for C++20?
Code: [Select]
:/work/dooble-dry/Source/dooble.cc
In file included from L:/QT6-6.2.X/include/QtCore/qfuture.h:45,
                 from L:/QT6-6.2.X/include/QtCore/QtCore:92,
                 from L:/QT6-6.2.X/include/QtConcurrent/QtConcurrentDepends:3,
                 from L:/QT6-6.2.X/include/QtConcurrent/QtConcurrent:3,
                 from K:/work/dooble-dry/Source/dooble.cc:41:
L:/QT6-6.2.X/include/QtCore/qfutureinterface.h:451:37: error: template-id not al
lowed for constructor in C++20 [-Werror=template-id-cdtor]
  451 |     explicit QFutureInterface<void>(State initialState = NoState)
      |                                     ^~~~~
L:/QT6-6.2.X/include/QtCore/qfutureinterface.h:451:37: note: remove the '< >'
cc1plus.exe: all warnings being treated as errors
make: *** [Makefile:12688: temp/obj/dooble.obj] Error 1
I wsan't planning on it - just remove -Werror from the makefiles..

40
Programming / Re: GCC - updates
« on: May 04, 2025, 07:37:16 am »
OK I think I've found the root cause of this...

OK https://smedley.id.au/tmp/gcc-15.1.0-os2-20250504.zip should fix the problems with filesystem support in libstdc++

The fix turned out to be pretty simple. I had recently set GCCOPT to -static-libgcc to avoid a dependency on gcc1.dll. However - libstdc++ is built with -shared-libgcc - and the flags conflict - so a bunch of configure tests were failing - which resulted in some broken functionality.

41
Programming / Re: GCC - updates
« on: May 04, 2025, 02:11:17 am »
OK I think I've found the root cause of this...

42
Programming / Re: GCC - updates
« on: May 03, 2025, 10:52:17 am »
just a FYI - gcc 15.1.10 has some issues with libstdc++ filesystem support which prevent syncqt.exe from Qt working, so I can're rebuilt Qt 6.8 with it (older versions don't use a compiled syncqt.exe are are OK).

Couple of different (but maybe related) errors:
Code: [Select]
  what():  filesystem error: cannot get file size: Operation not supported on socket [U:/dev/qt6-base-os2-6.8.x/build-gcc15/include/QtExampleIcons/qtexampleiconsversion.h]
Not a directory(20):filesystem error: cannot create directories: Not a directory [U:/dev/qt6-base-os2-6.8.x/build-gcc15/include/QtCore/6.8.3/QtCore/private]
The fix isn't obvious (yet)

43
Multimedia / Re: Updated Uniaud32 build
« on: May 01, 2025, 10:55:11 pm »
Thanks Mark - confirms no additional fixups are required.

44
Programming / Re: GCC - updates
« on: April 29, 2025, 10:25:51 am »
Fair enough. I'm just interested, what it would take to have a cross compiler.

Don't get me wrong, there could be definite benefits - for example - building qtwebengine on OS/2 is a PITA due to g++ processes consuming ~2gb of RAM on large compilations, so having to limit the number of ninja processes - building on a modern linux system could allow multiple processes to run without memory exhaustion.

45
Programming / Re: GCC - updates
« on: April 29, 2025, 10:15:46 am »
Hi Jochen,
Thanks for the answer. So for a cross compiler setup, we would need a port of these emx tools. The OpenWatcom stuff is already there.
Am I correct? (I know, it's certainly not that easy to do)
For a cross compiler, we'd also need binutils compiled on the host platform with the changes for os2 a.out. We'd probably also need a port of ld.exe that supports EMX a.out for configure tests.

I've thought about a cross compiler a couple of times and it's made my head hurt.

I'd rather spend energy trying to get wlink to work with coff or gas object files - and trying to update the toolchain to support those.

Pages: 1 2 [3] 4 5 ... 171