Aquileo | Recent changes to bugs

Aquileo | #35 makefiles fail is NITROS9DIR path has spaces in it.

Sun, 03 Jul 2022 22:09:59 -0000

https://nitros9.sourceforge.io/wiki/index.php/Building_NitrOS9
It says "prebuilt" but that means binaries.

Unix/etc allow spaces in filenames, but many tools are not so much at ease with it. If you do shell scripting, adding quotation marks all over (except where you shouldn't) works. If you do Makefiles, it is well, complicated.

Aquileo | #35 makefiles fail is NITROS9DIR path has spaces in it.

Sun, 03 Jul 2022 21:20:36 -0000

anyone with a modern Window PC would have defaulted to OneDrive

Good grief, I hope you are not right, and I think you aren't.

One could say that anyone with a Windows PC usually doesn't build his own software, and that's why we are providing release and snapshot binaries :)

And if it can be fixed simply by adding quotes around things in makefiles, why don't we just do that and solve it for everyone?

I think you tried that 2 years ago, and I think it is not so easy. GNU Make doesn't deal well with spaces, period. You will often see people install things like Cygwin, Python or many other cross-platform things on their C:\ root and that is for a reason. But here, also C:\Users\allen\Documents\nitros9 or anything like this will work too. Even Microsoft went way from using "Documents & Settings" or whatever stupid standard path element they used in the '95 days.

Anyway I think using relative paths instead of NITROS9DIR is a better way to solve this.

The days of paths without spaces is long, long gone.

That's why we like retro-computing!

At the very least, this needs to be documented.

Yes, please. If you don't have wiki access just post the text here and I'll copy it it.

Aquileo | #35 makefiles fail is NITROS9DIR path has spaces in it.

Sun, 03 Jul 2022 20:12:51 -0000

Is this documented?

As it stands today, anyone with a modern Window PC would have defaulted to OneDrive, and would be unable to build this.

Likewise, anyone with a modern Mac, with iCloud on by default, would be unable to build this.

At the very least, this needs to be documented. I consider myself a far more advanced user than most, and it's bitten me on both operating systems.

And if it can be fixed simply by adding quotes around things in makefiles, why don't we just do that and solve it for everyone?

The days of paths without spaces is long, long gone. That's been supported by OSes for so long, it's stunning this is still an issue with so many programs -- including commercial ones that cost $$$$.

Aquileo | #35 makefiles fail is NITROS9DIR path has spaces in it.

Sat, 02 Jul 2022 10:31:59 -0000

Go to a folder with no spaces in it, i.e. /Users/allen then create a soft link there:

cd
ln -s /Volumes/WhatNot/With Spaces/etc/nitros-9
cd nitros-9
make

Aquileo | #35 makefiles fail is NITROS9DIR path has spaces in it.

Sat, 02 Jul 2022 02:42:22 -0000

This hit me again tonight when I started trying to get NitrOS9 going ;-) It's the first time I've tried to build from an iCloud drive on Mac, and it has the same issue any Windows system with OneDrive has -- space in the path name, darnit.

Aquileo | #39 level 2 pmap assembly error with 4K block DAT

Fri, 15 Apr 2022 14:19:32 -0000

status: open --> closed-fixed

Aquileo | #39 level 2 pmap assembly error with 4K block DAT

Fri, 15 Apr 2022 11:58:45 -0000

Yes, it will assemble after just that line is fixed.

Aquileo | #39 level 2 pmap assembly error with 4K block DAT

Fri, 15 Apr 2022 09:26:58 -0000

Ah, the printed header string. I get it. Is it only line 104 that needs fixing?

Aquileo | #39 level 2 pmap assembly error with 4K block DAT

Fri, 15 Apr 2022 02:38:40 -0000

Twice as many blocks to show need a longer header, I guess?

Aquileo | #39 level 2 pmap assembly error with 4K block DAT

Thu, 14 Apr 2022 15:33:34 -0000

The "force direct" change was probably added to save a byte here and there and is not strictly necessary. I guess the same binary code is generated for CoCo3 because the assembler silently optimizes it to direct mode (see the LWASM forwardrefmax pragma).

Why is the header string longer for the 4K block DAT?