Re: [gentoo-user] Re: bash upgrading problem

[Raffaele Belardi]

Jacques Montier wrote:
> checking whether /dev/fd is available... ERROR: ld.so: object 'libsandbox.so' 
> from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored.

Just a guess. configure here is trying to read /dev/fd which is a symlink to
/proc/self/fd. Do you see anything strange with those two directories or 
directory entries?

$ ll /dev/fd
lrwxrwxrwx 1 root root 13 Jan 21 07:10 /dev/fd -> /proc/self/fd


# ll /proc/self/fd
total 0
lrwx-- 1 root root 64 Jan 21 07:53 0 -> /dev/pts/3
lrwx-- 1 root root 64 Jan 21 07:53 1 -> /dev/pts/3
lrwx-- 1 root root 64 Jan 21 07:53 2 -> /dev/pts/3
lr-x-- 1 root root 64 Jan 21 07:53 3 -> /proc/3744/fd

# ll /proc/self/
total 0
dr-x-- 2 root root 0 Jan 21 07:54 fd
(snip)

Re: [gentoo-user] Re: bash upgrading problem

[Jacques Montier]

Le sam. 19 janv. 2019 à 19:42, Jacques Montier  a
écrit :

>
> Thanks Jack,
>
> Le sam. 19 janv. 2019 à 19:03, Jack  a
> écrit :
>
>>
>> --quoted attachment
>> “app-shells:bash-4.4_p23-r1:20190119-102517.log”--
>> [snip much of emerge log]
>> So the problem occurs at the end of the ./configure stage.  You did not
>> include this in your original post.
>> > checking which library has the termcap functions... (cached) using
>> > libcurses
>> > checking whether /dev/fd is available...
>> > ERROR: ld.so: object 'libsandbox.so' from LD_PRELOAD cannot be
>> > preloaded (cannot open shared object file): ignored.
>> So this is the real error - portage can't (pre)load libsandbox.so.
>> 1) When is the last time you did a full upgrade?  I'm now wondering if
>> you have inconsistent versions of different packages installed.
>> 2) Try re-emerging sys-apps/sandbox.
>>
>
>  - I just did a full upgrade by : emerge -auvDN --with-bdeps=y
> --keep-going world => so i have to upgrade bash
> [ebuild U  ] app-shells/bash-4.4_p23-r1::gentoo [4.4_p12::gentoo]
> USE="net nls (readline) -afs -bashlogger -examples -mem-scramble -plugins"
> 0 KiB
> - Then emerge sandbox => OK
> - Then emerge bash => it stops asking for passwd. :-(
>
> 3) If that does not work, try running revdep-rebuild.  It should not
>> normally be necessary, but there are times.  Did an emerge world ever
>> get interrupted?
>>
>>
> - revdep-rebuild done without any error
>
>
> --
> Jacques
>


Hello all,

As i was backing up my gentoo system to an external USB drive via
SystemRescueCD, i tried one thing :

- i mounted all the partitions (/ , boot, home, etc.) and /dev, /sys, /proc
and chroot into the system

then
#emerge bash
and...it works ! No password asked !

After umounting all that stuff, reboot.

- I tried to re-emerge bash ; password : ? and it stops.

Anyone could explain that to me ? It would be great !

Thanks a lot !


*--*
*Jacques*

*https://sites.google.com/site/jacquesfr35/
*

Re: [gentoo-user] emerge --changed-use @world : how to interpret its output?

[Neil Bothwick]

On Sun, 20 Jan 2019 12:34:08 +0100, Helmut Jarausch wrote:

> nice -19 emerge -av1 --update --keep-going --tree --changed-use \
>   --unordered-display --verbose-conflicts @world
> 
> I get LOTS of request to change package.use to include abi_x86_32.
> 
> It looks like emerge wants to change half of system (which is nearly  
> abi_x86_64 only)
> to use the 32 bit ABI, as well.
> 
> How can I find out which packages triggers this chain of re-emerges?

The output from emerge should tell you which packages cause this. They
don't tell us because you haven't included it.

Hint: Don't use -v, it only clutter up the output with extra noise.
Without it you just get the error and warning messages.


-- 
Neil Bothwick

Roses are red, violets are blue; I'm schizophrenic and so am I.


pgpsJPcjufUXo.pgp
Description: OpenPGP digital signature

[gentoo-user] emerge --changed-use @world : how to interpret its output?

[Helmut Jarausch]

Hi,
I have difficulties to interpret the output of

nice -19 emerge -av1 --update --keep-going --tree --changed-use \
 --unordered-display --verbose-conflicts @world

I get LOTS of request to change package.use to include abi_x86_32.

It looks like emerge wants to change half of system (which is nearly  
abi_x86_64 only)

to use the 32 bit ABI, as well.

How can I find out which packages triggers this chain of re-emerges?

Many thanks for a hint,
Helmut