16
Programming / Re: GCC - updates
« on: May 04, 2025, 02:11:17 am »
OK I think I've found the root cause of this...
OS2World.com Forum is back !!!
Remember to visit OS2World at:
http://www.os2world.com
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.
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)
Fair enough. I'm just interested, what it would take to have a cross compiler.
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.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.
Am I correct? (I know, it's certainly not that easy to do)
Hey Steven,
I'll get you a debug cc1plus.exe once it's rebuilt.Code: [Select]Ã ## Ä Base ÄÄÄ Size ÄÄRÄWÄEÄResÄDisÄShrÄPreÄInvÄSwpÄRsdÄLocÄA16Ä32BÄCnfÄIOPÄ
³ 2 032A0000 00B760A0 û û û
So 12017824 bytes or 12,017,824 - so shouldn't be an issue?
à ## Ä Base ÄÄÄ Size ÄÄRÄWÄEÄResÄDisÄShrÄPreÄInvÄSwpÄRsdÄLocÄA16Ä32BÄCnfÄIOPÄ
³ 2 02690000 005B97F0 û û û
Building the release version of GCC 15.1.0 now - I expect the forking will still be a problem...
gcc.exe (GCC) 15.1.0
Copyright (C) 2025 Free Software Foundation, Inc.
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
Thanks! I downloaded and followed Martin's instructions and I have dooble-QT6 running.
Interesting observation: I wondered if I was missing some depenencies, so I ran PMDLL Qt6WebEn.dll
PMDLL does not do anything useful after that. Maybe it was never intended to work on such a complex DLL.