News:

OS2World.com Forum is back !!!

Remember to visit OS2World at:
http://www.os2world.com

Main Menu

GCC - updates

Started by Paul Smedley, March 16, 2022, 09:57:02 AM

Previous topic - Next topic

Mentore


Paul Smedley

Quote from: Mentore on August 13, 2025, 09:24:15 AM
Quote from: Paul Smedley on August 10, 2025, 11:22:42 AM
Only tested to confirm it can build itself.... https://smedley.id.au/tmp/gcc-15.2.0-os2-20250810.zip

Hi Paul, smedley.id.au is not responding right now. Problems?

Mentore

Nothing I'm aware of, and website loads for me from a 4G connection....

Paul Smedley

https://smedley.id.au/tmp/gcc-15.3.0-os2-20261108.zip only lightly tested - feedback appreciated.

Dave Yeo

#138
Quote from: Paul Smedley on November 08, 2026, 07:29:49 AMhttps://smedley.id.au/tmp/gcc-15.3.0-os2-20261108.zip only lightly tested - feedback appreciated.
Fails to build Dooble, so did 15.2.0. I'll attach the log but basically dooble uses -std=c++17 and fails with errors like
W:/usr/include/qt5/QtCore/qfutureinterface.h:284:37: error: template-id not allowed for constructor in C++20 [-Werror=template-id-cdtor]
  284 |     explicit QFutureInterface<void>(State initialState = NoState)
edit:
Qt6 gives a similar error,
L:/QT6-6.2.X/include/QtCore/qfutureinterface.h:451:37: error: template-id not allowed for constructor in C++20 [-Werror=template-id-cdtor]
  451 |     explicit QFutureInterface<void>(State initialState = NoState)

Paul Smedley

Quote from: Dave Yeo on November 08, 2026, 08:09:14 PM
Quote from: Paul Smedley on November 08, 2026, 07:29:49 AMhttps://smedley.id.au/tmp/gcc-15.3.0-os2-20261108.zip only lightly tested - feedback appreciated.
Fails to build Dooble, so did 15.2.0. I'll attach the log but basically dooble uses -std=c++17 and fails with errors like
W:/usr/include/qt5/QtCore/qfutureinterface.h:284:37: error: template-id not allowed for constructor in C++20 [-Werror=template-id-cdtor]
  284 |     explicit QFutureInterface<void>(State initialState = NoState)
edit:
Qt6 gives a similar error,
L:/QT6-6.2.X/include/QtCore/qfutureinterface.h:451:37: error: template-id not allowed for constructor in C++20 [-Werror=template-id-cdtor]
  451 |     explicit QFutureInterface<void>(State initialState = NoState)


Interesting, pretty sure I've built qt6 with gcc 15 previously. I'm having some issues with my primary OS/2 box, it's taken to hanging within 5 minutes or so of doing any long of serious work, and now on a reboot, vnc server is silently failing to start. Pretty sure the OS on that box isn't 5.1.2 so I try that update first then worst case pull it out of the rack and reseat RAM, replace cpu/heatsink paste

Dave Yeo

It might be a side affect of the recent GCC 9.2.0 updates, includes mostly though suddenly I had to change my environment for Qt6, compiles failed with /@unixroot/usr/include in CPLUS_INCLUDE_PATH.
Hopefully an easy fix for your OS/2 box

Dave Yeo

#141
It does seem like a side affect. Couple of months back I redid the RPM environment so it was all P4. Still have the backups of the old environment on the drive. So I add the old backup w:\usr.01\bin to the front of the PATH, and now Dooble is compiling with 15.3.0.
Weird and needs more investigation.
Edit: Scratch that, it was GCC 9.2.0 compiling it.

Paul Smedley

#142
Well reinstalling (ok updating) AOS got VNC back running again, until is hung solid (no mouse pointer or anything whilst gn.exe was running configuring qt6-webengine) and on next reboot, no vnc. It's crazy... That box has been rock solid for AGES now - after just a couple minutes of load it hangs hard...

I do have a second identical build box, but the drive in there was last mirrored at least a year ago, such is life... I'll have to think about next steps.

Dave Yeo

Run a memory checker, might be one in the BIOS. Reseat everything and clean it?
I had a stick of ram die the other month. In my case it only affected Linux which crashed when going graphical.

Paul Smedley

FYI I see some issues with 15.3 as well and had to roll back to 15.2 - will add it to the growing todo list!