Re: configure checking for csh hash hack

2015-05-08 Thread Paul Eggert
Michael wrote: i am looking at the same problem compiling groff and found his report to them, in their reply they directed him to come here I assume their reply means Werner Lemberg's message here: http://lists.gnu.org/archive/html/bug-groff/2014-10/msg8.html i'm not seeing a solution

Re: configure checking for csh hash hack

2015-05-08 Thread Werner LEMBERG
It's a problem related to the groff source code, and it's not something Autoconf can fix. :-) The attached patch might fix it. I haven't tested this patch, as I stopped using csh over 35 years ago and never want to go back. I think groff would be better off if it didn't worry about csh

configure checking for csh hash hack

2014-10-22 Thread Goldberg, Jon (Jon)
When used in the context of groff-1.22, the script does the following: if echo ./conftest.sh | (csh /dev/null 21) /dev/null 21; On my PC, the script hangs at that line (csh doesn't exit). Admittedly, its my fault: I've modified my .cshrc to do this: if ( $?prompt ) exec /bin/bash -i

Re: configure checking for csh hash hack

2014-10-22 Thread Paul Eggert
Goldberg, Jon (Jon) wrote: When used in the context of groff-1.22, the script does the following: if echo ./conftest.sh | (csh /dev/null 21) /dev/null 21; That's not from autoconf; it's something groff itself does, so please report the bug to bug-gr...@gnu.org instead.