OS/2, eCS & ArcaOS - Technical > Internet

FF trap in Web Developer => Network function...

<< < (3/3)

Dariusz Piatkowski:
Dave!


--- Quote from: Dave Yeo on December 21, 2019, 07:08:55 pm ---...should be at the same level as my last releases (might have screwed up the readme slightly). The XQS files are just built from the map files using a script Rich wrote some years back, the problem was in package-manifest.in, which lists what gets packaged.

--- End quote ---

I'm curious about something. This release had all the other DLLs iincluded. I had assumed this was the case since they were built using the same AMD family optimizations.

OK, so since I did not want to leave all these DLLs in the Firefox program directory I moved them out to \usr\local\lib. For FF purposes that was OK (\usr\local\lib is the 1st directory in my LIBPATH), however, things like ANPM fail, specifically that one complains of being unable to load the NSS library:


--- Code: ---Executing: @python G:\UTIL\ANPM\scripts\yum_populate.py
error: Failed to initialize NSS library
Traceback (most recent call last):
  File "G:\UTIL\ANPM\scripts\yum_populate.py", line 6, in <module>
    import yum
  File "/@unixroot/usr/lib/python2.7/site-packages/yum/__init__.py", line 23, in <module>
    import rpm
  File "/@unixroot/usr/lib/python2.7/site-packages/rpm/__init__.py", line 39, in <module>
    from rpm.transaction import *
  File "/@unixroot/usr/lib/python2.7/site-packages/rpm/transaction.py", line 5, in <module>
    from rpm._rpm import ts as TransactionSetCore
ImportError: cannot import name ts
Return code: 0

--- End code ---

Therefore, I moved the DLLs back into FF directory to avoid impacting the remainder of the system. This works so far, but begs the question of: do I not run into DLL conflicts now?

So FF will use it's own DLLs, but when things like ANPM run they will load them from the \usr\lib path, which is where they should be.

Now, maybe all this is a bit of a moot point, and maybe you built stuff like NSS from the latest releases which are currently showing up in netlabs-exp repo, and which i have not installed here?

What do you recommend as the preferred install?

FYI: I did try running just the core FF binaries with the current netlabs-rel DLLs, however that did cause some one-off crashes which i could not explain. So I am making the assumption the stuff in your FF release package must all go together and be used together.

Dave Yeo:
Yes, I updated various security stuff (pins certs) and decided to compile and include NSPR and NSS (NSS is dependent on NSPR) so for this release should be left in the program directory. They're likely compiled with different options compared to the system ones which results in the incompatibilities.
As Firefox etc now have LIBPATHSTRICT and BEGINLIBPATH built in, there should be no DLL conflicts with the system ones though they will use a bit more memory so should have their read only bit turned off and marked to load the code high. I assume the read only attribute is for security.
The ones in exp are a bit questionable right now, I'm running with some more fixes and it is slightly unstable when using the updated NSS and NSPR, as well NSS breaks loading some HTTPS sites on 38ESR. Working on it but not much time currently which is why I built your Firefox from the same base as the other releases though it does have some experimental changes in the optimization flags

ivan:
Hi Dave,

What you are doing with Firefox sounds to me like a step forward.  At least I won't have to be careful with the DLL stupidity that I have to step round at the moment where some of the programs I use don't work with the latest DLLs.

Do you think it is worth my trying the version you did for Dariusz on my Ryzen machines, or is it too optimised for what he has?

Dave Yeo:
Hi Ivan, I think it should work fine on a Ryzen CPU, worth testing anyways.

Navigation

[0] Message Index

[*] Previous page

Go to full version