[Puppy Linux Bionic] NPM troubles

[newton1372]

Good morning. I'm trying to run a React/NodeJS app using npm, but whatever npm command i try to run, i get the following error

/usr/local/bin/node: error while loading shared libraries: libstdc++.so.6: wrong ELF class: ELFCLASS64

I had looked in several forums (including this!) and i have found that problem could be the compatibility with 32bit systems. So i installed
32bit_compatibility_bionicpup64.sfs, then i've updated and rebooted, but the issue has not disappeared.

I think that the problrem is the missing of ibstdc++.so.6. Where can i do to find it?

Another question: if I would purge NodeJS/Npm and reinstall it again, how would i do? I looked for NodeJS in PPM, in UNINSTALL section, but i just have not found it.

[taersh]

If error message returns: wrong ELF class: ELFCLASS64 it means libstdc++.so.6 is installed.
Otherwise it could not return wrong ELF class.
Usually this error message appears if 64bit libstdc++.so.6 is installed in 32bit Operating System or 32bit libstdc++.so.6 is installed into 64bit Operating System.

Which Bionic Puppy are you running, 32bit or 64bit?

[newton1372]

my Bionic version is 64 bit. I'm not sure of that, how could i check it by terminal?

[taersh]

Check the base .sfs in install directory.
If it is puppy_bionicpup64_8.0.sfs then it is 64bit Puppy. If it is something like UPupBB then it's 32bit Puppy.

[newton1372]

Where is install directory? Can't find it.
However, i'm pretty sure i've installed 64 bit version.

[taersh]

Where did you install?
Check the HD drive, USB flash drive etc., where ever you had installed Puppy.

[newton1372]

I have installed it using a Live CD, into the sda1 partition of my Hard Disk. It is formatted as ext3

[taersh]

Then there must be some files on sda1 like vmlinuz, initrd.gz etc.
There's also some files with the .sfs suffix. One is puppy_XXX_XXX.sfs where XXX is name and version number.
How's that file named?

[newton1372]

Can't find it. The files vmlinux, initrd stay inside /boot directory, and in this directory i can't find any puppy_XXX_XXX.sfs file.
In the main directory of sda1 i find only a sfs, namely 32bit_compatibility_bionicpup64.sfs

When i update in Quickpet, the first line written in console during the updating is

http://distro.ibiblio.org/puppylinux/pu ... c64fix.zip

I hope this helps...

[taersh]

How do you boot then?

Edit:

Ok, it seems you have 64bit Puppy.

However, how do you boot, if there's no puppy .sfs?

[taersh]

What kind of install did you make?

Frugal install or Full install?

[newton1372]

I have grub4dos

The title i take to go into puppy linux is
title Bionicpup64 8.0 (sda1/boot)

So we can be sure that it is 64 bit

[taersh]

Please, send a screenshot from sda1.
Attach it to a post.

[taersh]

Ok,

if you have directory /boot on /mnt/sda1, then it seems you had made a full installation. With a full installation there is no puppy_XXX_XXX.sfs or puppy_bionicpup64_8.0.sfs.
In a full installation you can't load/unload .sfs files.

Did you use React/NodeJS app/npm from .sfs file?
If so, then there is no option to uninstall via Puppy Package Manager.

Puppy is best to be installed as a so-called frugal installation. Frugal doesn't have any disadvantages, but lots of advantages and benefits.

I recommend to start again from scratch and doing a fugal install.

After doing the frugal installation /mnt/sda1 or the install directory on /mnt/sda1 should similar look like this:

Screenshot.jpg (24.74 KiB) Viewed 388 times

[newton1372]

i don't know.
How could I do an extensive research to find such a sfs in the whole SDA1 partition?

Is it that fundamental to solve my issue (ossia doing npm and nodejs work?)

[newton1372]

I would to not be dependent by putting an external stuff to do puppy work. I'd prefer to have it inside my HD and using it as each else operative system...

What about Nodejs and Npm? Is there something i could do in order to let them work?

Last thing. I have installed nodejs using wget using a tutorial externally. I don't know if it uses .sfs..."

I am mainly an "Ubuntu" user. I'm having some troubles passing to puppy,It's approach is a bit..."traumetic" to me. But my pc is really old, and i thought Puppy is the last hope to make my pc living again.

[taersh]

I don't know anything about Nodejs etc.

As I wrote, it seems you have made a full install, as there's directory /boot in /mnt/sda1.
You should do a frugal installation and post further questions here: viewtopic.php?f=115&t=99
This is the forum section especially for Puppy Bionic64.

Though, you should also post the specs of your computer.
Model, type, how old, how much RAM etc.pp.
The more information you post the better help can be offered.

[cobaka]

Identifying your Linux distro.

Hello @newton1372

I know this has been answered, and you're now chasing something else, but I'll double-up.

To identify your distro:
Desktop > Applications (lwr left button) > System > Pup-SysInfo.

In Pup-SysInfo: Sys-Specs (-menu-) > distro specs.
You will see lots of things, including something like (-on my 32-bit uPup-)

Linux Kernel: 4.9.163-lxpup-32-pae (i686)
Kernel Version: #1 SMP Thu Mar 14 15:41:19 GMT 2019
Build GCC: 8.3.0
PAE Enabled: Yes
AND
Distro: BionicPup32 19.03
Window Manager: JWM v2.3.7
Desktop Start: xwin jwm

Pup32 tells me (of course) I am struggling along, barely making, it running a 'toy' 32-bit OS.

Sad, but true.

cobaka

[newton1372]

Sorry can't understand nothing. I don't find any "Applications" icon in Desktop....
Did you have my same issue? Did you solve it?

[newton1372]

I have found PupSysInfo. I'm just putting to you the output, hoping that could be useful

▶—— Distro Specifications ——◀

Distro: bionicpup64 8.0
Window Manager: JWM v2.3.7
Desktop Start: xwin jwm

Development:
Bash: 4.4.19
Geany: 1.33
Gtkdialog: 0.8.4
Perl: 5.26.1
Python: 2.7.15rc1
Yad: 0.40.0 (GTK+ 2.24.32)
--
busybox: 1.29.3
dhcpcd: 6.6.2
Glibc: 2.27
OpenSSL: 1.1.0g 2 Nov 2017, built on: reproducible build, date unspecified
wpa_supplicant: 2.6

▶—— /etc/DISTRO_SPECS ——◀

One or more words that identify this distribution:
• DISTRO_NAME='bionicpup64'

Version number of this distribution:
• DISTRO_VERSION=8.0

The distro whose binary packages were used to build this distribution:
• DISTRO_BINARY_COMPAT='ubuntu'

Prefix for some filenames: exs: bionicpup64save.2fs, bionicpup64-7.9.8.sfs
• DISTRO_FILE_PREFIX='bionicpup64'

The version of the distro whose binary packages were used to build this distro:
• DISTRO_COMPAT_VERSION='bionic'

Read by /usr/bin/xwin to bypass Xorg Wizard at first boot:
• DISTRO_XORG_AUTO='yes'

• DISTRO_KERNEL_PET='Huge_Kernel'

• DISTRO_DB_SUBNAME='bionic64'

• WOOF_VERSION=8

• DISTRO_TARGETARCH='x86_64'

• BUILD_FROM_WOOF='testing;c3552eef;2019-02-25 04:50:55 +0800'

Puppy default filenames...
Note, the 'SFS' files below are what the 'init' script in initrd.gz searches for,
For the partition, path and actual files loaded, see PUPSFS and ZDRV in /etc/rc.d/PUPSTATE
• DISTRO_PUPPYSFS='puppy_bionicpup64_8.0.sfs'

• DISTRO_ZDRVSFS='zdrv_bionicpup64_8.0.sfs'

• DISTRO_FDRVSFS='fdrv_bionicpup64_8.0.sfs'

• DISTRO_ADRVSFS='adrv_bionicpup64_8.0.sfs'

• DISTRO_YDRVSFS='ydrv_bionicpup64_8.0.sfs'

• DISTRO_PUPPYDATE='Feb 2019'

Multiarch distros, such as Ubuntu, will have this. ex: /usr/lib/i386-linux-gnu, so DISTRO_ARCHDIR=i386-linux-gnu
• DISTRO_ARCHDIR='x86_64-linux-gnu'

▶—— /etc/os-release ——◀

NAME=Puppy
VERSION="8.0"
ID=puppy_bionicpup64
VERSION_ID=8.0
PRETTY_NAME="bionicpup64 8.0"
ANSI_COLOR="0;34"
CPE_NAME="cpe:/o:puppy:puppy_linux:8.0"
HOME_URL="http://puppylinux.com/"
SUPPORT_URL="http://www.murga-linux.com/puppy/index.php"
BUG_REPORT_URL="https://github.com/puppylinux-woof-CE/woof-CE"

[newton1372]

Do you think it would be better to change the section of this question?
I'd still need help
Could someone help me?
Sorry for upping

[mikeslr]

I can only emphasize and explain what taersh previously wrote. Start from scratch. Delete your current 'Full Install' and re-install as Frugal.
Full & Frugal are misleading terms. Puppies were created to run as 'Frugal' --which only means to frugally use your storage space = does not require its own drive/partition, can share the partition used by Windows or any OS that actually requires an entire partition. Of course, you can deploy a Puppy to its own partition; or one shared with a bunch of other Puppies. Puppies were designed to 'co-exist' on a hard-drive with Windows: co-existent was the alternate name for frugal but, regretfully, didn't catch on. A frugal install is exactly the same operating system, includes the same files, as a Full install. It's just deployed differently, as 'squashed-file-systems', SFSes, rather than by extracting their contents and writing each file to your storage medium (drive). Extraction is what choosing 'Full Install' does. That's why it requires its own entire partition.
On bootup what a frugal Puppy does is copy the files from the SFSes on storage into RAM and, thereafter, run in RAM, only writing back to Storage (the Puppy-Save File/folder you can create on Shut-down) periodically and/or on command.
A dozen years ago, when computers were sold with 128 Mbs of RAM and rarely had over 256 Mbs of RAM, it was discovered that by extracting a Puppy's files to an entire partition you could still boot into it and doing so would 'shave-off' a second or two of the time it took to boot or open applications. On today's computers the speed difference is measured in micro-seconds: only significant in RAM intensive operations such as compiling applications.

Since the 'Full Install' technique was developed there has been no effort to remove its limitations nor any reason to do so. The main reason for its existence had ceased to exist: expensive RAM and computers which could only manage a limited amount, anyway. Perhaps the major limitation of a Full install is that if you make a mistake you're basically screwed: there rarely is a way to fix it; and even when there is it requires you to devote a lot of time manually removing/replacing files. But you've already discovered another limitation: it can't use SFSes. Frugal Puppies copy files into RAM creating a 'Merge File System'. A frugal Puppy can set priorities among file systems being copied into RAM: specify which of identically named files is to be used. A Full Install can only extract the contents of an SFS and copy it into the same folders on storage being used by the rest of your operating system. One possible result of doing so is "Wrong ELF class".

There's not much we --who answer questions on the Forum can-- do about what wording was written into the ISOs of the thousands of old versions of Puppies which have been published. We have many times mentioned that Full and Frugal should be renamed --perhaps to 'legacy' and 'standard'-- and a warning notice as to 'legacy' be included. There is no valid reason for new Puppy ISOs to continue to present this stumbling block. Devs appear not to pay attention. If I had dictatorial authority I would require Devs to spend their own time and money personally fixing the resulting problems.

[peebee]

There is no valid reason for new Puppy ISOs to continue to present this stumbling block. Devs appear not to pay attention. If I had dictatorial authority I would require Devs to spend their own time and money personally fixing the resulting problems.

Full install has already been "hidden" for new Woof-CE builds - but BionicPup64 is an "old" build so still offers full install - not much anybody can do about all the "old" Pups out there sadly......

[newton1372]

Maybe you've just convinced me, so i'm going ro reinstall puppy with frugal installation.
At this point i've just a problem. I have actually no other operative systems, apart from puppy.
Doing frugal installation, is required that everytime i turn my pc on i have to put the cd?
Do I have to insall other operative systems?

Thanks

[rockedge]

No! Once you have the Puppy Linux installed frugally and the boot method is set up you will not need to insert the CD-ROM every time.

[newton1372]

ok i reinstall puppy from the beginning and i will make you know