Re: Where is patch?

2006-01-04 Thread Stepan Kasal
ch or ftp://ftp.gnu.org/gnu/diffutils ? Have a nice day, Stepan Kasal -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/

resolv.h test proposal

2004-10-25 Thread Stepan Kasal
Hello, the text below seems to relly be a bug report with a proposed fix. So I take the liberty to forward it to the bug report address. Regards, Stepan Kasal - Forwarded message from "Gerrit P. Haase" - Date: Mon, 25 Oct 2004 13:46:43 +0200 From: "Gerrit P.

Re: resolv.h test proposal

2004-10-26 Thread Stepan Kasal
there are problems with it.) Thank you, Stepan Kasal # AC_HEADER_RESOLV # AN_HEADER(resolv.h, AC_HEADER_RESOLV) AC_DEFUN(AC_HEADER_RESOLV, [AC_CHECK_HEADERS(sys/types.h netinet/in.h arpa/nameser.h sys/socket.h) AC_CACHE_CHECK(for resolv.h, ac_cv_header_r

Re: resolv.h test proposal

2004-10-26 Thread Stepan Kasal
Hello, On Mon, Oct 25, 2004 at 06:16:40PM +0200, Reini Urban wrote: > I'd better fix it upstream so they'll get it without any notice. even if it gets to autoconf and they upgrade, they sill have to put AC_HEADER_RESOLV to their configure.ac (unless they use autoscan). Stepan -- Unsubscribe inf

Re: check for resolv.h

2004-12-03 Thread Stepan Kasal
help, Stepan Kasal AC_DEFUN([AC_HEADER_RESOLV], [AC_CHECK_HEADERS(sys/types.h netinet/in.h arpa/nameser.h netdb.h resolv.h, [], [], [[#if HAVE_SYS_TYPES_H # include #endif #ifdef HAVE_NETINET_IN_H # include/* inet_ functions / structs */ #endif #ifdef HAVE_ARPA_NAME

Re: check for resolv.h

2004-12-17 Thread Stepan Kasal
Hello, I have commited the check for resolv.h as posted in http://lists.gnu.org/archive/html/autoconf-patches/2004-12/msg2.html Noone reported any test results, but we can back it out if a problem appears. I added one more URL to the comment http://www.chemie.fu-berlin.de/cgi-bin/man/sgi_ir

Re: Fw: bug in texi2dvi, and hack patch

2005-01-24 Thread Stepan Kasal
Hi, On Sun, Jan 23, 2005 at 08:15:32PM -0500, Karl Berry wrote: > Regarding texi2dvi and cygwin, please see if the new version (below) works. > for dir in $PATH; do > # use test -x rather than test -f for DJGPP, where test -x checks > # for .exe. But test -x will also return true for d

Re: Fw: bug in texi2dvi, and hack patch

2005-01-25 Thread Stepan Kasal
Hi, On Mon, Jan 24, 2005 at 09:58:16PM +0200, Eli Zaretskii wrote: > > AC_SUBST(TESTF, "test -f") > > testfile=conf$$.exe > > touch $testfile > > if test -x $testfile; then > > test -f $testfile || TESTF=: > > fi > > rm -f $testfile this code was full of silly

Re: _AS_DETECT_BETTER_SHELL speedup

2005-01-29 Thread Stepan Kasal
ial speedup of ./configure on Cygwin, that would be a strong reason to accept it. So, Cygwin folk, it's your turn now. (This patch is Ralf's original patch, minus the parts which have been addressed by Paul's ``even more conservative patch''. Again. I have verifie

Re: _AS_DETECT_BETTER_SHELL speedup

2005-01-30 Thread Stepan Kasal
x27;{ foo; } 2>/dev/null' 2>&1 | grep fork with my Linux 2.4.x kernel. But yes, this proves that "{ ...; }" has no advantage over "(exec ...)". This also means that we don't need any benchmark from the Cygwin people. (I apologize to cygwin subscribers.) Th

Re: Fw: bug in texi2dvi, and hack patch

2005-05-24 Thread Stepan Kasal
what Autoconf does.) See the attached patch. I hope I haven't screwed anything. Have a nice day, Stepan Kasal PS: if ebb9 or dave can actually fwd this to the cygwin list, that might be a good idea; I'm not subscribed there. 2005-05-24 Stepan Kasal <[EMAIL PROTECTED]>

Re: Fw: bug in texi2dvi, and hack patch

2005-05-24 Thread Stepan Kasal
Hi, On Tue, May 24, 2005 at 06:32:58AM -0600, Eric Blake wrote: > Now, if both tex and tex.exe exist, but tex is not executable, > then you just failed to find tex.exe on cygwin. OK. But later on, command "tex" is called. If both tex and tex.exe exist in the same directory in path, what does bas

Re: Fw: bug in texi2dvi, and hack patch

2005-05-25 Thread Stepan Kasal
Hello, On Tue, May 24, 2005 at 01:35:38PM -0400, Karl Berry wrote: > if { test -x "$dir/$1" && test -f "$dir/$1"; } || >{ test -x "$dir/$1.exe" && test -f "$dir/$1.exe"; }; then > > Stepan, do you have an objection to it? OK, this will be the cleanest solution, after all. I commited