Removing chrome removed few files needed for other programs as well

[user1234]

I have loaded devx.sfs but cannot find ar, though gcc can be found. Is ar not included in devx in fossapup, or I need to re-download devx.

[mikewalsh]

@user1234 :-

I have loaded devx.sfs but cannot find ar, though gcc can be found. Is ar not included in devx in fossapup, or I need to re-download devx.

It is there - in /usr/bin - but it's a symlink to x86_64-linux-gnu-ar. Do you not see it at all?

(If you're wanting this for the Chrome-portable's updater, under Tahrpup64, Xenialpup64, Bionicpup64 and Fossapup64 you don't need to load the devX. For these 4 Puppies, the necessary deps & mechanism are all built-in to Chrome-portable as it comes.)

Mike.

[user1234]

It is there - in /usr/bin - but it's a symlink to x86_64-linux-gnu-ar. Do you not see it at all?

I can't see it in my device (I have attached two images). I can see the x86_64-linux-gnu-ar though, so I will create a symlink myself.

(If you're wanting this for the Chrome-portable's updater, under Tahrpup64, Xenialpup64, Bionicpup64 and Fossapup64 you don't need to load the devX. For these 4 Puppies, the necessary deps & mechanism are all built-in to Chrome-portable as it comes.)

I know that, that's why I am not re-downloading devx. But I wanted to check if it really wasn't included in fossapup's devx, or is not found at my side only.

[bigpup]

Do a fresh new download of the fossapup64 devx sfs
http://distro.ibiblio.org/puppylinux/pe ... 64_9.5.sfs
make sure it is loaded by using SFS-load-on-the-fly

ar is in my install of Fossapup64 9.5 with the fossapup64 devx sfs loaded

[bigpup]

You sure you are using Fossapup64 9.5 Puppy Linux?

The tray at the bottom of your images does not look like Fossapup64 9.5's tray.

[user1234]

You sure you are using Fossapup64 9.5 Puppy Linux?

The tray at the bottom of your images does not look like Fossapup64 9.5's tray.

100% sure. I have used theme maker to create that theme and use some icon theme provided by puppy itself (in JWMdesk manager). I also use konsole.

I now know why did this happen. I wanted to download and install mike's portable chrome and thought to uninstall previously installed one (installed from quickpet). When compiling a c file today, I was getting error message that a certain .so file was not found. I used find command and found a similar one in portable chrome. So I copied it over to where it was needed for gcc to work (it displayed the name of the folder in error message).

There must be a lot more files which need to be copied. Should I just copy them over manually from mike's portable chrome or just re-downloading devx would overwrite those changes made.

(I remember once running pwd > /etc/rc.d/rc.local instead of pwd >> /etc/rc.d/rc.local, which overwrote the file. To restore the file, I opened my puppy save file (in another puppy) and deleted it from there. Will a same kind of trick be useful in this situation?)

[user1234]

Anyone who knows which files need to be copied or reinstalled from ppm???

Should I just reinstall the google chrome from quickpet and leave it there and use portable chrome? But I'm afraid it might even worsen the situation, since portable chrome has made few files in /opt and at other places as well (my portable chrome is in /root/Downloads/Google_Chrome-portable).

[mikewalsh]

@user1234 :-

Anyone who knows which files need to be copied or reinstalled from ppm???

Should I just reinstall the google chrome from quickpet and leave it there and use portable chrome? But I'm afraid it might even worsen the situation, since portable chrome has made few files in /opt and at other places as well (my portable chrome is in /root/Downloads/Google_Chrome-portable).

Mm. How do you know that you have "missing files"? Also - and I'm just curious about this - what "extra" files has Chrome-portable created in /opt? To the best of my knowledge, the portable will only create one additional file, and that's in /root/.config - the "Crash Reports" directory. Chrome creates this directory in every install, and even the portable can't keep it self-contained (I know this, because I've tried. But it never contains anything except for a few empty directories, and is only a few kb in size, so I just leave it where it is).

My /opt looks like this (this is Quirky April 7.0.1 'lite', but the kennels are all pretty much the same:-

No sign of a 'google' directory, as you can see.....or anything else related to Chrome. (If you've removed a 'built-in' Chrome, an empty 'google' directory will often get left behind.)

Mike.

[user1234]

Mm. How do you know that you have "missing files"?

I feel like that. As I posted, gcc was giving error while compiling a program that a certain .so file was missing (I don't remember the name of the .so). So there might be a lot more.

VSCode is also notifying me on startup that the opened files have been changed and makes me compare both versions by opening them side-by-side. I then see that both the versions are completely similar. It might be due to some different reason, but this error has started popping up after I uninstalled chrome. I might be wrong since previously VSCode didn't even keep its tabs open after a reboot (but did in kubuntu). After all I must say, I am just assuming it all, and it might be wrong.

My /opt looks like this (this is Quirky April 7.0.1 'lite', but the kennels are all pretty much the same:-

No sign of a 'google' directory, as you can see.....or anything else related to Chrome. (If you've removed a 'built-in' Chrome, an empty 'google' directory will often get left behind.)

I do have google directory in /opt (which might be of older chrome, PPM must have left it).

Can I just update my LD_LIBRARY_PATH to include portable-chrome's lib directory? That way all the files necessary for other applications which might have been deleted can be found again.

[mikewalsh]

Can I just update my LD_LIBRARY_PATH to include portable-chrome's lib directory? That way all the files necessary for other applications which might have been deleted can be found again.

For Fossapup, it's not necessary. Fossapup already has newer versions of everything in that 'lib' directory. This is what was giving me massive problems with Chrome under Fossapup, until member baraka realised what was going on, and advised me about this last year.

That lib directory was put together some 4 years ago, with major assistance from member battleshooter. baraka realised that one dependency, libpangoft2, was conflicting with the one in the lib directory, and everything just snowballed from that point.....and went downhill. Gtk-3.0 was being a particular sore point as well.

As things stand at the moment, Fossapup64, Bionicpup64, and Xenialpup64 all use their own versions of what the lib directory contains. The only reason it still remains is for those members still running the older Tahrpup64, which does require most of those libs to run Chrome.

-----------------------------------

If you want to check that you have everything that directory contains, the only way I can see to do it would be to look inside the main SFS from the Fossapup ISO. Compare these with what you have yourself, cross-referencing the contents of the Chrome-portable lib directory to make sure you get every one.

For peace of mind, swap over every relevant lib in your Fossapup install with the same ones from the ISO. That way, you'll know for definite you've got the correct ones. Unfortunately, this will have to be a manual job; I wish I could tell you otherwise, but there just is no quick, simple 'fix' here, I'm afraid.

(Some might think you can just swap over both the main Fossapup SFS and the adrv, too.....but this won't work, because your save' will still contain data which indicates that certain files have 'whiteouts' over them, indicating to Puppy that those files no longer 'exist'. And before you ask, no; I have no idea how you can 'delete' or remove these 'whiteouts'.)

Mike.

[bigpup]

What are you trying to compile?
Be specific, details?

When I get compiling errors.
Usually the programs compiling process is coded to want to only use newer stuff, than is in the Puppy version.
So it will not compile in that version of Puppy Linux.

I get an older version of the program or a newer version of Puppy Linux to use.

Fossapup64 9.5 has been OK for compiling, but maybe it is starting to show it's age for compiling very new coded programs.

[bigpup]

How to find and recover files that are white listed in the save.
viewtopic.php?t=1636

[user1234]

What are you trying to compile?
Be specific, details?

When I get compiling errors.
Usually the programs compiling process is coded to want to only use newer stuff, than is in the Puppy version.
So it will not compile in that version of Puppy Linux.

I get an older version of the program or a newer version of Puppy Linux to use.

Fossapup64 9.5 has been OK for compiling, but maybe it is starting to show it's age for compiling very new coded programs.

I was trying to compile hello world c program. BTW as was giving me error.... gcc's assembler I think.

How to find and recover files that are white listed in the save.
viewtopic.php?t=1636

If manually doing everything is the last option left , I will do it. I don't think it will be a process of more than an hour .

Thank you everyone .

[bigpup]

I was trying to compile hello world c program.

Isn't that Windows OS code not Linux code?

[user1234]

I was trying to compile hello world c program.

Isn't that Windows OS code not Linux code?

I don't understand what you're trying to say. I mean I do, but am not sure if I understood it rightly.

I wanna ask have you learnt c?. I think you haven't by what I understand this question is.

I am just posting the code-

Code: Select all

#include <stdio.h>

int main() {
    printf("Hello World!");
    return 0;
}

It just prints Hello World! to the screen (and each os supports it, or rather c supports this for all os).

[bigpup]

sorry, I was having a brain fart when I asked that question.

I have never messed with c code.

[bigpup]

I wonder if you could boot not using the save.
Setup with basic settings.
Shutdown making a new save, with just that setup, giving this save a specific name.
Boot and when asked, select this new save to use.
then load the devx and kernel sources with any other stuff that would help in compiling.

Make it a special save and setup, to boot into, for compiling, only.

Do you know how to boot, not using the save, so on shutdown, you will be asked to make a save?

[user1234]

Yes I know that all. But you don't need to bother much now, I copied the file that was printed missing from chrome-portable (it was available there). I can well compile my c files now.

(One more correction- kernel sources are not necessary to compile c code, kernel themselves are written in c, which can be compiled. Just for your information about c )

[user1234]

I am having new problem. Few .so files are getting whitelisted regularly, I don't know why. They are libbfd*.so and libsvd/sdv*.so (whatever it is) or maybe some else. How can I find what is causing the problem?.

[rockedge]

Fossapup64 9.5 has been OK for compiling, but maybe it is starting to show it's age for compiling very new coded programs.

I just compiled a huge kernel 5.16.14-klvx using Fossapup64. A stock version with the devx and 32 bit compatibility lib's loaded.

Also compiled pure-ftpd for the same Fossapup64 since my PET file didn't install because it's in some strange compression all of a sudden it seems and needs to be repackaged.

My favorite compiling platform is a Bionic64