| 1 |
On Dec 23, 2010, at 12:45 AM, Michael Haubenwallner wrote: |
| 2 |
|
| 3 |
> |
| 4 |
> On 12/23/10 01:37, Perry Smith wrote: |
| 5 |
>> When my bootstrap process was trying to build openssl-1.0.0c, I got stuck at: |
| 6 |
>> |
| 7 |
>> WARNING! If you wish to build 64-bit kit, then you have to |
| 8 |
>> invoke './Configure aix64-cc' *manually*. |
| 9 |
>> You have ~5 seconds to press Ctrl-C to abort |
| 10 |
>> |
| 11 |
>> The tty was set with -icanon but I believe the problem is the config script says '#! /bin/sh'. |
| 12 |
>> On AIX, /bin/sh is actually ksh and ksh mucks with the tty settings between commands. |
| 13 |
> |
| 14 |
> I've not seen such problems since I do </dev/null. |
| 15 |
> Does it help to redirect stdin from /dev/null for you too? |
| 16 |
|
| 17 |
I'm not sure when you are suggesting to do the redirect. It would cause the stty to fail and the read |
| 18 |
would return immediately so it would avoid hanging forever. |
| 19 |
|
| 20 |
I've never seen this before (a configure script that pauses or expects input). Given that Portage is a 'batch' type |
| 21 |
concept, maybe the redirect should be part of Portage. |
| 22 |
|
| 23 |
> |
| 24 |
>> I changed it to use /bin/bsh directly (see below). |
| 25 |
>> This could work but I'm a Gentoo Portage Prefix moron so when I started the bootstrap back up, |
| 26 |
>> it re-fetched the openssl package and spoiled my fun. |
| 27 |
>> I ended up gently killing the youngest copy of sh from another window and that caused things to get rolling again. |
| 28 |
>> This may be something to do with my ksh set up too. |
| 29 |
>> I don't use ksh but I might have it set so it defaults to emacs mode rather than vi mode. |
| 30 |
>> In any case, the script needs to avoid using ksh (on AIX at least). |
| 31 |
> |
| 32 |
> Anyway, nice hint, thank you! |
| 33 |
|
| 34 |
I passed this up to the openssl guys too (if I get through their mailer). |
Archives