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 - Dave Yeo

Pages: 1 2 [3] 4 5 ... 360
31
Setup & Installation / Re: Troubleshooting process trap/dump...how?
« on: May 05, 2025, 06:56:38 am »
Sometimes reseating the ram and any other cards fixes these types of issues as wears off any oxidation.

32
Networking / Re: TCP/IP from MVDM DOS sessions
« on: May 05, 2025, 01:25:56 am »
Dave: Possibly. I'm still no clear how the PC/FTP exactly works, but since it was meant as a TCPIP stack for OS2 systems _without_ one (without IBM tcpip for os2) I suspect the IBM BSD stack to be completely bypassed?

In that case, there may be sharing issues, the network adapter and sockets at least. "ifconfig lan0 down" for example may fix the socket sharing, not sure about the network adapter.

33
Networking / Re: TCP/IP from MVDM DOS sessions
« on: May 04, 2025, 07:45:35 pm »
Code: [Select]
F:\test>help 1521

SYS1521: There are too many parameters specified in the
*** statement on line *** of the CONFIG.SYS file.  Line ***
is ignored.

EXPLANATION: The specified statement in the CONFIG.SYS file has more
parameters than are expected.

ACTION: Edit the CONFIG.SYS file to correct or remove the incorrect
statement and restart the system.

One I haven't seen.
Understand that through Warp v4 OS/2 used a 16 bit stack based on BSD 4.3, while now we use a 32 bit stack ported from AIX based on BSD 4.4. Not sure about using an old device with the new stack.

34
Programming / Re: GCC - updates
« on: May 04, 2025, 08:48:35 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

Thanks, that fixed it
Code: [Select]
[K:\work\dooble-dry\build]make
L:/QT6-6.2.X/bin/qmake.exe -o Makefile K:/work/dooble-dry/dooble.pro
Project MESSAGE: The QtCharts module has been discovered.
make: Nothing to be done for 'first'.

need a make clean or such

35
Programming / Re: GCC - updates
« on: May 04, 2025, 08:18:10 am »
It did work here, though the trp seems familiar.
I'll reinstall Qt6 tomorrow and see if that helps.

36
Programming / Re: GCC - updates
« on: May 04, 2025, 08:02:18 am »
Unluckily, another problem which I have a vague feeling you figured out before. Using
Code: [Select]
L:\qt6-6.2.x\bin>bldlevel qmake.exe
Build Level Display Facility Version 6.12.675 Sep 25 2001
(C) Copyright IBM Corporation 1993-2001
Signature:       @#cmake build system:0.0#@##1## 18 Jan 2025 18:18:51     ARCAOS-803C4C0::::0::@@qmake
Vendor:          cmake build system
Revision:        0.00
Date/Time:       18 Jan 2025 18:18:51
Build Machine:   ARCAOS-803C4C0
ASD Feature ID:  4C0
File Version:    0.0
Description:     qmake

I get,
Code: [Select]
[K:\work\dooble-dry\build]make
L:/QT6-6.2.X/bin/qmake.exe -o Makefile K:/work/dooble-dry/dooble.pro
Assertion failed: _UM_LUMP_STATUS (olump) == _UMS_FREE, file U:/DEV/libc-git/src
/emx/src/lib/malloc/ialloc.c, line 116

Killed by SIGABRT
pid=0x0911 ppid=0x0910 tid=0x0001 slot=0x00c3 pri=0x0200 mc=0x0001 ps=0x0010
L:\QT6-6.2.X\BIN\QMAKE.EXE
Creating 0911_01.TRP
Moved 0911_01.TRP to W:\var\log\app\68169e12-0911_01-QMAKE-exceptq.txt
make: *** [Makefile:515: Makefile] Abort trap

Trp attached.
Also want to test changing -O3 to -O2. Over optimization really made Mozilla unstable.

37
Programming / Re: GCC - updates
« on: May 04, 2025, 07:46:43 am »
[Even better, any idea where the -Werror comes from?

Of course. dooble.pro

38
Programming / Re: GCC - updates
« on: May 04, 2025, 07:44:53 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..

A simple good idea. Even better, any idea where the -Werror comes from?

39
Programming / Re: GCC - updates
« on: May 04, 2025, 03:28:58 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

40
Programming / Re: GCC - updates
« on: April 30, 2025, 01:35:50 am »
It's a fairly small computer, https://www.os2world.com/wiki/index.php?title=Lenovo_ThinkCentre_M910s_-_10ML and likely no room in it for a water cooler. I have picked up a small (40mm?) fan to stick in the front, have to figure out the wiring as the fan has 3 wires and the header has 4 wires, also picked up a heat sink for the NVMe. Have to take it apart and add the components and clean it again. I use wood heat and the house is dusty:)
I also see that actually the CPU was faster then I mentioned, 3.4/3.8GHz.
It's a nice little computer, was C$80 used with no storage. Going to a lot of similar on the market as it is just a hair too old to run Win 11 being released in 2019.

41
Programming / Re: GCC - updates
« on: April 29, 2025, 05:15:10 pm »
I tried building Qt6 on Linux, it was scarily fast. This I5 went into turbo mode, 3.6 GHz, OS/2 doesn't seem to enable the turbo and stays at 3.2 GHz, and temperatures shot up in this little computer, CPU at close to 90C (60C is about the highest it gets on OS/2) and worse, the NVMe at its max of 85C. Build failed in the webengine and I didn't want to do it again without more cooling.
As for cross-compiling, not only GCC and friends, the EMX toolchain need porting, a lot of other tools have OS/2 specific code. Think of the autotools. Plus there are test programs and such built during a complex build. Some use Rexx too. Possible but a bigger job then likely expected.

42
Programming / Re: GCC - updates
« on: April 28, 2025, 11:28:59 pm »
Just a question: What are we doing to produce OS/2 binaries?
Do we call emxomf, wlink etc. to convert the binaries?

Set up your environment and then the usual gcc flags work.
My gcc1510env.cmd is attached, adjust if needed. Put it on your PATH, execute in a cmd session, check by running gcc-v, then use as older GCC's

43
Setup & Installation / Re: PYTHON - v2 vs v3 and dependencies...
« on: April 28, 2025, 12:25:28 am »
Ok, thanks

44
Setup & Installation / Re: PYTHON - v2 vs v3 and dependencies...
« on: April 27, 2025, 08:33:57 pm »
ANPM comes with Python2 scripts to begin with.
Are you sure about that? I thought that everything had been updated to python3. Looking, all the scripts simply call python, "#! /usr/bin/python -tt", which here is,
Code: [Select]
W:\usr\bin>python --version
Python 3.9.21


45
Setup & Installation / Re: PYTHON - v2 vs v3 and dependencies...
« on: April 27, 2025, 05:49:48 pm »
You have already identified the problem: your python.exe is the same as python3.9.exe.
Just copy python2.7.exe over python.exe and you are fine.

That's only a good solution if you want to usually use Python2. Other solutions include using the full name, python2.7.exe instead of python2.7 or python2. I think our system doesn't like the multiple dots in the executable name. Another solution is to use sh to launch the python2/python3 script as it seems to get it right.
As for removing python2, it is different enough from python3 it is likely worth keeping it around as there are lots of python2 scripts still out there. I also suspect that there are dependencies between the two in the RPM environment.

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