SliTaz SliTaz Forum

You are not logged in.

#1 2022-09-01 20:20:30

Ceel
Administrator
Registered: 2011-04-02
Posts: 1,424

Error when updating gcc83-lib-base

...

[c]Execute pre-install commands...

cp: can't stat 'libstdc++.so.6.25/libstdc++.so.6.16': Not a directory

cp: can't stat 'libstdc++.so.6.25/libstdc++.so.6.16': Not a directory

cp: can't stat 'libstdc++.so.6.25/prev.libstdc++.so.6.16': Not a directory[/c]

...

Offline

#2 2022-09-27 18:29:33

Ceel
Administrator
Registered: 2011-04-02
Posts: 1,424

Re: Error when updating gcc83-lib-base

Hmm, this problem does not seem to excite the crowds... ;-)

But I think I know why: you can't reproduce the problem.

I just see it happens only on my lives USB; it didn't happen on my (old: october 2018) full installation.

Run a live session from the last ISO and type

[c]tazpkg -gi gcc83-lib-base --forced[/c]

Offline

#3 2022-09-28 18:32:40

shann
Administrator
Registered: 2011-04-01
Posts: 1,296
Website

Re: Error when updating gcc83-lib-base

Hi Ceel,

In case on rc3, first install of gcc83-lib-base work (because only libstdc++.so.6.0.16.

if i try to reinstall them, same issue.

Function of pre_install try to copy libstdc++.so.6.*.* with prefix "prev.", but found 2 libs (6.0.16 and 6.0.25).

[c]cp -a $lib prev.$lib[/c] concat both names.

Offline

#4 2022-10-14 16:48:42

Ceel
Administrator
Registered: 2011-04-02
Posts: 1,424

Re: Error when updating gcc83-lib-base

Hi shann,

Thank you for your reply.

Yes I can see in my lives USB the two files.

In case on rc3, first install of gcc83-lib-base work (because only libstdc++.so.6.0.16.

In my full installations there is only libstdc++.so.6.0.25, no libstdc++.so.6.0.16.

I must confess that this is not clear for me... What is really necessary, libstdc++.so.6.0.16 or  libstdc++.so.6.0.25 or both???

Well it does not seem there is any trouble despite the error message.

Offline

Registered users online in this topic: 0, guests: 1
[Bot] ClaudeBot

Board footer

Powered by FluxBB
Modified by Visman

[ Generated in 0.019 seconds, 7 queries executed - Memory usage: 1.53 MiB (Peak: 1.77 MiB) ]