On 2019.01.21 13:41, Jacques Montier wrote:
Le lun. 21 janv. 2019 à 19:19, Jack <ostrof...@users.sourceforge.net>
a
écrit :
>
> 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
>
Jack,
- I don't manually build bash. Just : #emerge bash
- CTRL+Alt+F1 to get out of X and go to TTY1
- logged as root with the root password
- emerge bash stops at password required.
Since you are logged in as root, have you tried the root password when
sudo asks? I wonder if it's looking for the portage password, which I
don't think exists. As someone else said - there is really no reason
for sudo to be used if you are root. However, during the emerge, I
believe the effective UID is changed to portage. Does this give anyone
else any further ideas of what to check?
