Linux Port

That was resolved by removing the trailing ,feb from the Linux component file.

No, that made it more broken by changing the filetype to text causing it to be displayed instead of executed. Did you neglect to change it back?

A build has resulted in the same filetype extension and ‘srcbuild’ not found errors.

I have made the Makefile more verbose if you set the variable VERBOSE, which hopefully pinpoint the problem so please try something like:

git pull --rebase
make VERBOSE=1

You can check if you have changed a git checkout by using git status.

One oddity found earlier was that some filetyping had been lost on copying, under Raspbian, a working HardDrive4 folder to a new binary build. Odd indeed!

What program and options did you use to copy it? It might not support copying extended attributes.

Thanks very much for the assistance.

With a new download the build now stops here as shown by the VERBOSE option.

Obey: set BASIC$Path     Build:
Obey: Set Apps$Path      <Build$Dir>.Apps.
Obey: Set Makefiles$Path <Build$Dir>.BuildSys.Makefiles.
Obey: |
Obey: |set Src$Dir        <Build$Dir>.Sources
Obey: set Install$Dir       <Build$Dir>.Install
Obey: setmacro Install$Path <Install$Dir>.
Obey: 
Obey: |
Obey: | Determine whether we have a working or broken amu - if it is working (5.13 or later), the system variable
Obey: | BuildSys$AMU$Fixed will be set to "yes" - otherwise "yes".   To cope with the broken Makefiles in the build
Obey: | tree, for the time being the compatibility option is required for the fixed version of AMU.  Older versions
Obey: | do not require this fix, but also need to pass environment variables in explicitly.
Obey: |
Obey: /amu -f <Build$Dir>.Env.Makefile FIXED=yes find-amu-version
Error: Syntax: *Type [-File] <filename> [-TabExpand] (Error number &DC)

HAL_DebugRX called and --abort-on-input given.
make: *** [Support/build.mk:48: Build/Linux/RiscOS/Images/rom] Error 117

DDE28 with AMU vsn 5.32 is in use.

Just in case DDE28 is an issue I tried DDE25.

I can’t find ‘amu’ in RISC_OS_Dev, so assuming ‘amu’ is not being found ‘amu.ff8’ was added, taken from DDE25 Lib32.

RISC_OS_Dev/RiscOS/Library/Acorn/amu,ff8

That got the build to the ‘srcbuild’ not found issue, but with more detail.

Obey: /<Build$Dir>.Utilities.Release.srcbuild.srcbuild -s export_hdrs export_libs resources rom install_rom join
Error: File 'IXFS:$.dev.fd.5.Build.Linux.RiscOS.Utilities.Release.srcbuild.srcbuild' not found (Error number &D6)

Added ‘srcbuild’ at that location.

RISC_OS_Dev/RiscOS/Utilities/Release/srcbuild/srcbuild,ff8

That gets the build a bit further.

Obey: 
Obey: Dir <Build$Dir>
Obey: /<Build$Dir>.Utilities.Release.srcbuild.srcbuild -s export_hdrs export_libs resources rom install_rom join
Parsing territory line UK
territory is UK
1 territory detected in the territories list.
Country UK has a code of 1
Numeric territory string is 01
Error creating directory 'Install.ROOL.Linux'.
Fatal error creating directory 'Install.ROOL.Linux'.
Batched errors...
Error creating directory 'Install.ROOL.Linux'.
------------------------------------------------------------------------------
Obey: BASIC -quit IXFS:$.dev.fd.5.Unix.LinuxSupport.Finish

This directory is present.

RISC_OS_Dev/Build/Linux/RiscOS/Install/ROOL/Linux

I don’t know why DDE28 and its ‘amu’ failed. I will have to come back to that later.

Obey: /amu -f <Build$Dir>.Env.Makefile FIXED=yes find-amu-version
Error: Syntax: *Type [-File] <filename> [-TabExpand] (Error number &DC)

I don’t know why DDE28 and its ‘amu’ failed. I will have to come back to that later.

Because it has a (default) filetype of Text, it needs an extension of “,ff8” or a POSIX extended attribute named “user.RISC_OS.LoadExec” which contains the filetype. It appears all your problems are caused by a lack of filetypes on DDE. You can examine extended attributes using the “fgetattr” command.

Building the RISC_OS Linux rom on Raspbian on a Raspberry Pi4 works OK here. I used SunFish to copy over the DDE from RISC_OS.

Also moving stuff around on Linux lost the file type information. Using tar and --xattrs always preserved them.

GNU cp with the -a option preserves filetypes. Rsync works with the -X option

Dolphin and other programs that use kioslaves don’t, some work has been to fix it. What is state other file managers?

It appears all your problems are caused by a lack of filetypes on DDE.

DDE28 with filename extensions was taken from RPCEmu on Ubuntu with tar --xattrs and transferred to the RPi4. The Linux Port built. HardDisc4 from the existing built binary install was copied to new build with cp -a. Filer drags are now good in 256 colours.

(tar on the Mac does not support --xattrs.)

Thanks for all the help.

I have renumbered OS_DynamicArea 26 to 27 to avoid the other one.

I have renumbered IXFS and the IXSupport SWIs to official allocations. Any saved “CMOS” settings will need updating:

*Configure Filesystem IXFS

The big issues with building are usually an issue with the way that DDE has been copied or an issue with comma2attr. A big gotcha is if something trips up the latter, the former can be corrupted. Don’t know how or why, but when it happens it’s easiest to plop down a fresh copy of DDE and forcibly clean the local Git repo.
I just cloned a fresh copy of the Linux2 branch and built it pn my Jetson Nano, so it does build.

I just managed to get a build to work, I had to use the -F flag when unzipping my DDE25.zip file, and, strangely, I had to pause the build and execute “rmdir Build/Linux/RiscOS/Images/rom/” before romlinker is executed, otherwise it failed.

It might have something to do with this, at the start of the build…

Building GIT commit: 54410bd8bcc4f239991203e8c8421e45b57690a9
rm: cannot remove ‘RiscOS/Images/rom*’: No such file or directory

It’s the first time I’ve built any RISC OS from source. Really nice job, many thanks!

Any chance we will see Aemulor working on the Linux Port?
I’d love to see Impression Style running on it.

I had to pause the build and execute “rmdir Build/Linux/RiscOS/Images/rom/” before romlinker is executed, otherwise it failed.

But why is there a directory there? There should only ever be a file by that name.

rm: cannot remove ‘RiscOS/Images/rom*’: No such file or directory

That is to delete any executable (ROM image) from a previous build, otherwise overwriting a running executable will either fail or crash the running instances.

Building GIT commit: 54410bd8bcc4f239991203e8c8421e45b57690a9

Thanks, for identifying version, like every good bug report.

For running PlingStore it seem we have a missing IOCTL:

Unhandled Internet Ioctl: 0×8004667D

It is the ASYNCIO. I wonder how to implement this.

Best regards,
Jan Rinze.

It is the ASYNCIO. I wonder how to implement this.

I have implemented it well enough for PlingStore to run. However to documentation is unclear, incomplete and contradictory.

Should the Internet Event be called in callback context or in interrupt context? Should it be called for events other data available for read or space for writing?

Calling Simon Willcocks
Sorry to hijack this thread but RIG (Risc Investment Group) is trying to contact all its members so that it can be wound up. The address that we have from 10 or so years ago for Simon is just bouncing. So Simon can you please either email myself: alan.dawes@argonet.co.uk or Rob Hemmings who is coordinating the winding up at rhemmings@rgvk.co.uk. Thank You, Alan dawes

Trying to run RISC OS Linux on non rooted Android running Linux always gives this error. The sysctl command fails with a permission denied error.
Is there any way of running it without having to update vm.mmap_min_addr.

./RISC_OS
Failed to reserve address space, try running “sudo sysctl vm.mmap_min_addr=12288.”
#

I’ve been using the linux port on a RPi4 for some time. I could access my data on a NAS via a linux mounted directory (mount -t cifs //fritz.box/fritz.nas …) which worked well until a raspberrypi os update came in about the middle of August. Since then the RISCOS port couldn’t read or write data to/from the mounted directory. I’ve update my RISCO OS port with the binary from GIT but the problem remains. Anyone else had this problem? Is there something I’m overlooking?
Regards
Mark Beerling

I installed the Linux port on the PineBook Pro. From the binaries. Very good work.
I use Manjaro on eMMC and Debian on SDCard.
RPCEmu only works with Debian. So I tried the Linux port. I should have done earlier. ;-)
The Manjaro dependencies are called slightly different. Most of it is installed when you install the KDE developer tool. The rest can be found quickly via the package manager.
The start_riscos script is not running to the end (on both), Harddisc4 and the stuff inside I have add manually.
The first short tests were very positive. RISC OS runs much faster than RPCEmu.
! TempBin crashes and completely sweeps ROSC OS with it. The rest I tested was working.
I miss the directory icons on the icon bar as with the other scrennshots here. Did I not seen something?

Click for bigger screenshot …

I miss the directory icons on the icon bar as with the other scrennshots here. Did I not seen something?

Using the pre-built binary download on a Raspberry Pi 4 the TinyDir harddrive icons are set in Tasks.Pinboard.

X AddTinyDir IXFS:$
X AddTinyDir <IXFS$HardDisc4>

HardDisc4 is at IXFS:$.HardDisc4 here, it is two levels down in the screenshot above.

X AddTinyDir

Now that you write it. Not long ago I read about in forum (and post an entry before) but didn’t remember :-(
Thanks a lot.

PineBook Pro at this times comes with Manjaro. Linux Port works but the mouse pointer has a square on his side…

Debian from SD works without this.

Linux Port works but the mouse pointer has a square on his side…

The same with recent version of RISC OS on the Pi (2560×1440 screen).

On Debian it looks and works very nice!

Thanks a lot!

IMHO, ROS on Linux must become an official ROS port…