Re: [ARMini-support] This machine kills pythons
- From: A Rawnsley <rcomp@xxxxxxxxxxx>
- To: armini-support@xxxxxxxxxxxxx
- Date: Fri, 13 Nov 2020 13:32:38 GMT
In message <58cec51f47john@xxxxxxxxxxxxxxxx>
John Harrison <john@xxxxxxxxxxxxxxxx> wrote:
Not just pythons
I recently found that my browsers of last resort (O-Browser, Otter &
Qupzilla) have all stopped working. They all give (slightly different)
messages complaining about lack of SharedLibs.
I haven't used them for a while since I've been using Iris where NetSurf
can't cope, but this particular task crashed Iris so I needed to revert to
one of the others.
Any idea how I could get them working again?
As shipped, Iris purposefully doesn't mess with your !SharedLibs in !Boot,
nor any other aspect of your system, as the bits it loads (for the
session) may be beta, and therefore not something you want permanently
installed.
That being said, many of those items are now out in the field from other
venues (eg. Otter/Qupzilla, Packman, riscosports.org etc), so can be
considered "released".
I feel that there's been a bit of a murky period with !SharedLibs et al in
the transition from old GCC 4 era code to newer GCC 8 era, and I'm not
sure it has all settled down.
There are new SharedUnixLib and SOmanager modules, plus the various shared
libraries themselves.
I have a sense that some of the old shared-object builds may not be 100%
friendly with the latest modules, or there may have been changes to how
VFP/NEON are handled.
Certainly I'm (personally) not 100% happy that everything has solidified
yet, which is why I've kept !Iris "socially distanced". However, if
you've updated to recent Qupzilla/Otter, you may well have introduced
those elements into your system already via that route, in which case
Iris' "standalone" approach can't help - you're already on the bleeding
edge.
I know none of this is good. Right now there are two approaches:
1) Merge everything in together so that (hopefully) everything
can find what it needs and work.
2) Keep things separate so that individual programs work, and
can be isolated.
1) is definitely the end goal, but I fear that things aren't really quite
stable enough at the moment, and this seems to manifest in things needing
updates etc. This worries me, because old things really ought to continue
working.
2) is not what I'd prefer long term, but allowed us to give people things
to test out without wrecking their system with less-well-tested elements.
However, it can be a problem if you want to mix other shared-libs programs
into the mix.
I hope this helps.
PS, you could try re-installing Otter/Qupzilla via packman (without first
running Iris). Perhaps from Chris G's "riscosports" repository. I've not
tried this to be honest, as I've been rather busy this summer, but I know
Chris has been doing some good work updating things. However, they *do*
now use latest GCC 8/10 stuff I think, so we're back to bleeding edge...
--
R-Comp
22 Robert Moffat, High Legh, Knutsford, Cheshire WA16 6PS
Tel: 01925 755043 Fax: 01925 757377
http://www.rcomp.co.uk
---
To alter your preferences or leave the group,
visit
//www.freelists.org/list/armini-support
List-related queries to info@xxxxxxxxxxxx
Other related posts:
