On 2019.01.21 11:44, Jacques Montier wrote:
Le lun. 21 janv. 2019 à 15:37, Alexander Kapshuk <
[email protected]> a écrit :
>
> (1). Are you attempting to build bash as yourself or as user root?
> (2). If the latter, what's in LD_PRELOAD and LD_LIBRARY_PATH?
>
> (3). What's the output of:
> ls -l /path/to/libsandbox.so?
> (4). And:
> file /path/to/libsandbox.so
>
>
(1) I always build bash as user root (su then password)
(2) there's no output with echo $LD_PRELOAD or $LD_LIBRARY_PATH
(3) libsandbox.so is located in /usr/lib32 and /usr/lib64
ls -al /usr/lib32/libsandbox.so
-rwxr-xr-x 1 root root 91720 19 janv. 19:14 /usr/lib32/libsandbox.so*
ls -al /usr/lib64/libsandbox.so
-rwxr-xr-x 1 root root 84520 19 janv. 19:14 /usr/lib64/libsandbox.so*
file /usr/lib32/libsandbox.so
/usr/lib32/libsandbox.so: ELF 32-bit LSB pie executable, Intel 80386,
version 1 (SYSV), dynamically linked, stripped
file /usr/lib64/libsandbox.so
/usr/lib64/libsandbox.so: ELF 64-bit LSB pie executable, x86-64,
version 1
(SYSV), dynamically linked, stripped
-----------------------
BUT, i think the error is NOT libsandbox related.
As i said in a previous post, i could successfully emerge bash with a
live
SystemRescuecd.
Here is the log (attached file) :
We could see the same error many times (>10) :
..... snip
checking whether /dev/fd is available... ERROR: ld.so: object
'libsandbox.so' from LD_PRELOAD cannot be preloaded (cannot open
shared
object file): ignored.
We trust you have received the usual lecture from the local System
Administrator. It usually boils down to these three things:
#1) Respect the privacy of others.
#2) Think before you type.
#3) With great power comes great responsibility.
sudo: no tty present and no askpass program specified
.....snip
Now the difference is : sudo: no tty present and no askpass program
specified
Does that mean that the problem comes from sudo (see the attached
sudoers
file )?
Thanks again,
--
Jacques
I have a suspicion that this really might be sandbox related.
/dev/fd/whatever are all in the live system, and if I understand
correctly, emerge works within the sandbox, so you should not be able
to get at those files (certainly not write to them, but it isn't clear
what the ebuild is trying to do there.)
However, if you are running the emerge (please do clarify that your are
trying to emerge bash, not just manually build it) as root, I don't see
any reason it should try to use sudo for anything.
Just for a change, try logging in as root, not doing su, and see if the
emerge works.
Jack
