| 1 |
On 2019.01.21 11:44, Jacques Montier wrote: |
| 2 |
> Le lun. 21 janv. 2019 à 15:37, Alexander Kapshuk < |
| 3 |
> alexander.kapshuk@×××××.com> a écrit : |
| 4 |
> |
| 5 |
> > |
| 6 |
> > (1). Are you attempting to build bash as yourself or as user root? |
| 7 |
> > (2). If the latter, what's in LD_PRELOAD and LD_LIBRARY_PATH? |
| 8 |
> > |
| 9 |
> > (3). What's the output of: |
| 10 |
> > ls -l /path/to/libsandbox.so? |
| 11 |
> > (4). And: |
| 12 |
> > file /path/to/libsandbox.so |
| 13 |
> > |
| 14 |
> > |
| 15 |
> (1) I always build bash as user root (su then password) |
| 16 |
> (2) there's no output with echo $LD_PRELOAD or $LD_LIBRARY_PATH |
| 17 |
> (3) libsandbox.so is located in /usr/lib32 and /usr/lib64 |
| 18 |
> ls -al /usr/lib32/libsandbox.so |
| 19 |
> -rwxr-xr-x 1 root root 91720 19 janv. 19:14 /usr/lib32/libsandbox.so* |
| 20 |
> ls -al /usr/lib64/libsandbox.so |
| 21 |
> -rwxr-xr-x 1 root root 84520 19 janv. 19:14 /usr/lib64/libsandbox.so* |
| 22 |
> |
| 23 |
> file /usr/lib32/libsandbox.so |
| 24 |
> /usr/lib32/libsandbox.so: ELF 32-bit LSB pie executable, Intel 80386, |
| 25 |
> version 1 (SYSV), dynamically linked, stripped |
| 26 |
> file /usr/lib64/libsandbox.so |
| 27 |
> /usr/lib64/libsandbox.so: ELF 64-bit LSB pie executable, x86-64, |
| 28 |
> version 1 |
| 29 |
> (SYSV), dynamically linked, stripped |
| 30 |
> |
| 31 |
> ----------------------- |
| 32 |
> |
| 33 |
> BUT, i think the error is NOT libsandbox related. |
| 34 |
> As i said in a previous post, i could successfully emerge bash with a |
| 35 |
> live |
| 36 |
> SystemRescuecd. |
| 37 |
> Here is the log (attached file) : |
| 38 |
> We could see the same error many times (>10) : |
| 39 |
> |
| 40 |
> ..... snip |
| 41 |
> checking whether /dev/fd is available... ERROR: ld.so: object |
| 42 |
> 'libsandbox.so' from LD_PRELOAD cannot be preloaded (cannot open |
| 43 |
> shared |
| 44 |
> object file): ignored. |
| 45 |
> |
| 46 |
> We trust you have received the usual lecture from the local System |
| 47 |
> Administrator. It usually boils down to these three things: |
| 48 |
> |
| 49 |
> #1) Respect the privacy of others. |
| 50 |
> #2) Think before you type. |
| 51 |
> #3) With great power comes great responsibility. |
| 52 |
> |
| 53 |
> sudo: no tty present and no askpass program specified |
| 54 |
> |
| 55 |
> .....snip |
| 56 |
> |
| 57 |
> Now the difference is : sudo: no tty present and no askpass program |
| 58 |
> specified |
| 59 |
> |
| 60 |
> Does that mean that the problem comes from sudo (see the attached |
| 61 |
> sudoers |
| 62 |
> file )? |
| 63 |
> |
| 64 |
> Thanks again, |
| 65 |
> |
| 66 |
> -- |
| 67 |
> Jacques |
| 68 |
I have a suspicion that this really might be sandbox related. |
| 69 |
/dev/fd/whatever are all in the live system, and if I understand |
| 70 |
correctly, emerge works within the sandbox, so you should not be able |
| 71 |
to get at those files (certainly not write to them, but it isn't clear |
| 72 |
what the ebuild is trying to do there.) |
| 73 |
|
| 74 |
However, if you are running the emerge (please do clarify that your are |
| 75 |
trying to emerge bash, not just manually build it) as root, I don't see |
| 76 |
any reason it should try to use sudo for anything. |
| 77 |
|
| 78 |
Just for a change, try logging in as root, not doing su, and see if the |
| 79 |
emerge works. |
| 80 |
|
| 81 |
Jack |
Archives