| 1 |
On Thu, Aug 29, 2013 at 6:54 PM, Steven Trogdon <strogdon@×××××.edu> wrote: |
| 2 |
> |
| 3 |
> On Thu, Aug 29, 2013 at 6:13 PM, Zac Medico <zmedico@g.o> wrote: |
| 4 |
>> |
| 5 |
>> On Thu, Aug 29, 2013 at 3:12 PM, Steven Trogdon <strogdon@×××××.edu> |
| 6 |
wrote: |
| 7 |
>> > On Thu, Aug 29, 2013 at 12:35 PM, Zac Medico <zmedico@g.o> |
| 8 |
wrote: |
| 9 |
>> >> |
| 10 |
>> >> |
| 11 |
>> >> The unprivileged/chown wrapper captures all of the output from the |
| 12 |
real |
| 13 |
>> >> chown program and uses it to generate an ewarn message. You might get |
| 14 |
a |
| 15 |
>> >> clue if you temporarily rename the wrapper so that the real chown |
| 16 |
>> >> program is called directly. |
| 17 |
>> >> -- |
| 18 |
>> >> Thanks, |
| 19 |
>> >> Zac |
| 20 |
>> >> |
| 21 |
>> > |
| 22 |
>> > Instead of killing the process I did a Ctrl-C in the terminal to stop |
| 23 |
>> > things, moved unprivileged/chown out of the way and restarted stage3. |
| 24 |
The |
| 25 |
>> > headers installed, I suppose correctly, and building is now continuing. |
| 26 |
>> |
| 27 |
>> It may be possible for the wrapper to go into an infinite exec loop if |
| 28 |
>> ${BASH_SOURCE[0]} doesn't work correctly (maybe a problem with older |
| 29 |
>> bash). What version of bash did you have? |
| 30 |
>> |
| 31 |
> From the logs I have |
| 32 |
> *** emerge --oneshot --nodeps --verbose <app-shells/bash-4.2_p20 |
| 33 |
> and then |
| 34 |
> >>> emerge (1 of 1) app-shells/bash-4.1_p11 to |
| 35 |
/storage/strogdon/gentoo-test/ |
| 36 |
> This is prior to the linux-header hang. So I presume bash-4.1_p11 was |
| 37 |
installed. |
| 38 |
> |
| 39 |
Yes, it is bash-4.1_p11 that's causing the hang. One can test this an an |
| 40 |
already-installed Prefix. |
| 41 |
I'm unable to go <bash-4.1_p11 without downgrading portage. |
Archives