OS/2, eCS & ArcaOS - Technical > Applications

ANPM on Warp 4.52 - Error and Loop on RPM/YUM install

<< < (6/7) > >>

Dave Yeo:
When I first installed RPM/YUM on Warp v4, I already had UNIXROOT set to pointing to an EMX developer setup, talk about fun.
As for RPM's with no internet, or really bad internet, I found the simplest is to just have a local repository.

tthoms:
Martin, you are a beautiful man!

It seems to have worked!

Thank you so much for all of your effort..

Luey123:
Hi,
This is my first post on this forum 😊

This also resolve problem I had on install of eCs 2.1 on VirtualBox.
ANPM had error that loop every time I try to run it. It was messaging that YUM/RPM is not installed.
I tried everything but nothing was working.
So I found this instruction on OS/2 wiki and tried it on my eCs 2.1 VM.

So after installing ANPM and then from it YUM/RPM I edit config.sys and ad this:
LIBPATH=C:\USR\LOCAL\LIB;C:\USR\LIB;
PATH=C:\USR\BIN;
SET UNIXROOT=C:

And it worked! 😊
Only everytime I run ANPM it was messaging about changing config.sys.
Since I done it myself I was clicking “NO”, but this message get irritating so finally I click “YES” and it still works.

I was able to update all repositories. Install Firefox, SeaMonkey and VLC…… and then run into some problem but describe it different thread 😊

Andreas Schnellbacher:

--- Quote from: Mieszko on November 18, 2020, 04:44:31 pm ---LIBPATH=C:\USR\LOCAL\LIB;C:\USR\LIB;

--- End quote ---
You should better ensure that one segment with a single dot is added to LIBPATH. The default place is at the begin: LIBPATH=.;LIBPATH=C:\USR\LOCAL\LIB;... but some experienced ones of us prefer adding it to the end: LIBPATH=...;.;

If the dot is not added, many programs that come with additional DLLS in the dir of the EXE won't find them.

Andi B.:

--- Quote ---Only everytime I run ANPM it was messaging about changing config.sys.
--- End quote ---
This can be changed in the ANPM options. "Ansicht" "Einstellungen" "Pfadüberprüfung überspringen" - in English probably 'View' 'Setting' ....

Libpath - since a while I personally prefer P:\USR\LOCAL\LIB;P:\USR\LIB;.;<here comes the rest>. P: is my UNIXROOT. This ensures that my own build libraries are loaded if available P:\USR\LOCAL\LIB, if not the official RPM libs are loaded (P:\USR\LIB) and only if there is no match there then some libs from some weird programs (.) get loaded. So let's say if I start some very old weird_app which came with its own version of libc063 in its own weird_app directory it will use the current version from P:\USR\LIB. Either because some other program has the right one loaded before or cause it finds libc063 in P:\USR\LIB before it looks into it's own (.) directory. At least that's my understanding.

If this weird_app really needs it own outdated libc063 then it would not work and I know I've to start this special weird_app with LIBPATHSTRICT and BEGINLIBPATH. But it does not interfere with the rest of the system (other programs which benefits form the current libc063 forwarder).

Navigation

[0] Message Index

[#] Next page

[*] Previous page

Go to full version