Hi Erich,
I answered inline.
Best regards
Thomas
On 6/12/21 6:23 PM, Erich Steinböck wrote:
Hi Thomas!
executing rexximage on my Linux works fine and builds rexx.img
OK, please revert the changes you did to Activity::resolveProgramName
Checked
root 14888 14843 10758192 3336 0 0 R ps
What's the reason you are building with root instead of a standard user?
Already answered this. But I have an addition here. When I first tried to
push files on the device I pushed them onto the SD Card.
Files on the SD Card will not get the privilege to be executed. Its also
not possible to grant these privilege with chmod on the SD Card. Therefore,
even when I copied the files to the working path on the device
(/data/local/tmp) they were not executable. In this path its possible to make
them executable again.
Altough, pushing to the device to the path /data/local/bin is only possible
if the adb shell is running as root user. As normal user you can only push to
the SD Card.
Its easy to switch between root and non-root, tough. adb root & adb unroot
does the trick. So, it would be possible to push the files as root and then try
to execute the files as non-root user. I already did this once but I just
installed a fresh Android device because the old one broke. So im trying again
on the new one.
rxapi: lockfile is locked by another rxapi instance; exiting
Does /tmp/.ooRexx-5.0.0-64-root.lock exist?
I'm not able to access the /tmp Folder.
Can you rm /tmp/.ooRexx-5.0.0-64-root.lock and try again?
Can you try running rxapi from a different (root or non-root) user?
I just did this as non-root user and with the changes Prof. Flatscher told
me. More on the changes in the next answer. The bottom line is that its not
working but with additional output.
Might /tmp on the emulated Android device be a file system that is shared with
the host Linux (and be locked there)?
No, it seems that there are no shared files.
As far as I understand direct access to the file system is typically pretty
much restricted on Android. Can your test users access /tmp?
No.
If all else fails, you may try to write a test program that does the equivalent
of acquireLock in APIService.cpp and try whether locking files on various paths
succeeds
Working on that.
_______________________________________________
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net<mailto:Oorexx-devel@lists.sourceforge.net>
https://lists.sourceforge.net/lists/listinfo/oorexx-devel
_______________________________________________
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel
