[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
string.h + strings.h
string.h + strings.h
Fri, 22 Sep 2000 12:55:18 +0200 (CEST)
A few weeks ago I've reported that the latest version of ANSI C also
contains strings.h which means that the old test (loading either
string.h or strings.h but not both) is no longer a correct assumption
for autoconf tests -- many ANSI C compliant compilers (like cc on AIX
and Sinix) have BSD-like functions in strings.h which is not
automatically included by string.h.
Is there a solution already available in autoconf? Looking at the
latest ChangeLog entries, I can't find something into this direction.
Please Cc to my address since I'm not on this list.
>From address@hidden Mon Sep 25 11:47:36 2000
Received: from term-21.ltionline.com ([188.8.131.52]
by fencepost.gnu.org with esmtp (Exim 3.16 #1 (Debian))
id 13daTe-00070M-00; Mon, 25 Sep 2000 11:47:34 -0400
Received: (from address@hidden)
by coopercc.netheaven.com (8.9.3/8.9.3) id LAA01067;
Mon, 25 Sep 2000 11:44:52 -0400
Date: Mon, 25 Sep 2000 11:44:52 -0400
X-Authentication-Warning: coopercc.netheaven.com: ccc set sender to
address@hidden using -f
From: Clark Cooper <address@hidden>
To: address@hidden, address@hidden, address@hidden
Subject: Bug in sed that causes configure script problem (Windows NT - cygwin)
List-Id: Bug reports for autoconf, the GNU build system <bug-autoconf.gnu.org>
I'm working on a project at SourceForge that is using the autoconf
utility. The generated configure script uses the sed utility heavily.
In some places, the configure script writes sed operations to a file
and then calls sed with the '-f' switch which reads the file.
My configuration script was generated using autoconf 2.13 on a Linux system.
(Red Hat 6.2, kernel 2.2.14).
On Windows NT, using cgwin 1.0.6 and sed version 3.02 this script fails since
sed interprets the carriage return (as part of the CRLF line ending under
Windows) as an unrecognized operator/flag. I verified this by taking the
same sed script file and replacing CRLF with just LF. The script then
I'm amazed and skeptical that I would be the first to run into this problem.
Have I perhaps missed some autoconf macro or failed to set up the environment
on the NT system properly?
If not and I'm truly the first to report this, here's a patch to sed
that should fix the problem. I can't tell if it really fixes the problem
since sed itself uses a configure script that fails in exactly the same way.
*** compile.c.orig Mon Sep 25 11:43:16 2000
--- compile.c Mon Sep 25 11:05:46 2000
*** 938,943 ****
--- 938,944 ----
+ case '\r':
Clark Cooper Software Engineer Home: address@hidden
Schenectady, NY USA Work: address@hidden
|[Prev in Thread]
||[Next in Thread]|
- string.h + strings.h,
Werner LEMBERG <=