SGI: Development

GNU Bash and CTRL-C/SIGINT

Hey All,

GNU Bash 4.2.x seems to compile without fatal errors, but the resulting `bash` binary doesn't produce a ^C when you hit CTRL+C in winterm.

Have tried 3.2.56, 4.2, 4.2.10, 4.2.53 and 4.4-beta. All generate a non ^C producing binary.

Am calling configure as:

CC=c99 CFLAGS="-O2" ./configure

Can somebody hold my hand please?

PS. I know the Nekoware bash 4.2.10 notes state that it was compiled with -O1. Tried that, no dice.
:Fuel: redbox 800Mhz 4Gb V12
I can confirm that 4.2.10 on my system produces the ^C, not much help with your problem, but I suppose at least we know that version SHOULD work?

Any chance it's your environment, keyboard etc etc?
-----------------------------------------------------------------------
Hey Ho! Pip & Dandy!
MyDungeon() << :Fuel: :Octane2: :Octane2: :Octane2: :Octane: :Indy: MyLoft() << :540: :Octane: MyWork() << :Indy: :Indy: :O2: :O2: :O2: :Indigo: :Indigo:
just use zsh if you like it fancy :P
r-a-c.de
Nevermind this post, it seems I've twiddled with the file in question.
:Octane: halo , oct ane Image knightrider , d i g i t a l AlphaPC164, pond , soekris net6501, misc cool stuff in a rack
N.B.: I tend to talk out of my ass. Do not take it too seriously.
Solved by adding:

stty intr '^C' echoe

to .bashrc from .profile