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 ... 168
1
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.

2
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.

3
Programming / Re: GCC - updates
« on: April 29, 2025, 07:26:06 am »
Expanding on Dave's comments, I tend to compile in a.out (the default) but then link with -Zomf which makes the compiler invoke emxomfld which uses emxomf and wlink to make the executables or DLLs.

This code is all basically evolved from the earlier gcc 3.x builds.

4
Programming / Re: GCC - updates
« on: April 27, 2025, 11:13:39 am »
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?

For cc1plus from 15.1.0:
Code: [Select]
à ## Ä Base ÄÄÄ Size ÄÄRÄWÄEÄResÄDisÄShrÄPreÄInvÄSwpÄRsdÄLocÄA16Ä32BÄCnfÄIOPÄ
³  2 02690000 005B97F0 û û                                        û         

005B97F0 = 6,002,672 - so half the size of 15.0.1

GCC 14.3.0- cc1plus.map - 2.8mb
GCC 15.0.1 - cc1plus.map - 19.7mb
GCC 15.1.0 - cc1plus.map - 3.5mb

5
Programming / Re: GCC - updates
« on: April 27, 2025, 10:10:12 am »
I've now built GCC 15.1.0, apache2 and php 8.1 with gcc15.1.0.

I haven't (yet) tried to build with multiple jobs - I suspect this will fail like 15.0.1 did... (ie due to apparent fork()n bugs/limitiations in libc)

Edit: interestingly, qt6-base-os2 appears to be building fine with GCC 15.1.0 - so appears the problems with fork were due to something that was only in the GCC beta code <shrug>

6
Programming / Re: GCC - updates
« on: April 27, 2025, 05:40:17 am »
Sorry, try again...

8
I donn't mean to be negative about the prospects of getting a working browser, but in the 2+ years since I first got Qt6webengine compiling, to the best of my knowledge, despite all code being published in githib, nobody except me has compiled the webengine.

A few others have built qt6base and some of the other dependencies, and have contributed patches, for which I'm grateful.

I've had some success getting it compiling, and through tenacity, have fixed some stuff, but the reality is that I'n *NOT* a programmer. I know literally none of the OS/2 API, and only have very basic knowledge of C/C++. I can hack existing code and maybe get it working, but when it comes to complex code and interpreting crashes, I'm truly not that good.

What I'm trying to say is that right now, I hold out little prospect of us getting a newer browser than the one based on Qt 6.2.6.

The other reality is, that even if we can somehow get a newer version, the 4GB memory limit is a REAL issue.....

9
Programming / Re: GCC - updates
« on: April 26, 2025, 10:10:28 am »
Building the release version of GCC 15.1.0 now - I expect the forking will still be a problem...

Code: [Select]
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.

10
Programming / Re: GCC - updates
« on: April 26, 2025, 03:09:31 am »
Building the release version of GCC 15.1.0 now - I expect the forking will still be a problem...

11
Programming / Re: Qt6 Application Testing
« on: April 25, 2025, 07:45:47 am »
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.

I tend to use chkdll32.exe rather than pmdll - for no real reason :)

12
Programming / Re: Qt6 Application Testing
« on: April 24, 2025, 07:34:55 am »
I've reinstated the missing file - apologies for the inconvenience.

13
Programming / Re: Qt6 Application Testing
« on: April 24, 2025, 01:28:00 am »
When I try to download https://smedley.id.au/tmp/qt6weben-6.2.6-20250124.zip I get a 404.

I'm trying to follow Martin's guide to installing Qt6 and Dooble on page 1.

Probably my bad as I did a cleanup of my tmp directory over Easter. Pretty sure there is a better choice of binaries than that link. I'm out this morning but will follow up here this afternoon my time.

14
Multimedia / Re: Updated Uniaud32 build
« on: April 20, 2025, 11:28:48 pm »
Thanks Tellie and Martin - reviewed alsa.log and confirmed all necessary fixups are in place.

15
Multimedia / Re: Updated Uniaud32 build
« on: April 20, 2025, 08:29:09 am »
OK - I did some searching - I think https://git.launchpad.net/~canonical-kernel/ubuntu/+source/linux-oem/+git/noble/log/?h=oem-6.11-next is the list of checkins to the OEM kernel.

More specifically https://git.launchpad.net/~canonical-kernel/ubuntu/+source/linux-oem/+git/noble/log/?h=oem-6.11-next&qt=grep&q=asus is checkins which mention asus.

https://smedley.id.au/tmp/uniaud32.sys has a small change taken from the above source.

The other possibility is that the entry 'Cirrus Amp detection not supported on OS/2' could be what's causing the problem. This function had some code that was in the 'too hard' bucket to port when I was getting things building.

Edit: I think the issue is the lack of support for the amp - seems https://forums.gentoo.org/viewtopic-p-8826751.html?sid=022a561d200218c68bbf8e86827faef6 might describe what you're experiencing?

Pages: [1] 2 3 ... 168