From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: Supporting parameters that include the = character in configure.bat Date: Thu, 14 Apr 2011 01:11:47 -0400 Message-ID: References: <83lizirrli.fsf@gnu.org> Reply-To: Eli Zaretskii NNTP-Posting-Host: lo.gmane.org X-Trace: dough.gmane.org 1302757923 14229 80.91.229.12 (14 Apr 2011 05:12:03 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Thu, 14 Apr 2011 05:12:03 +0000 (UTC) Cc: Emacs-devel@gnu.org To: Ben Key Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Thu Apr 14 07:11:53 2011 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([140.186.70.17]) by lo.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1QAEqP-0002cF-4k for ged-emacs-devel@m.gmane.org; Thu, 14 Apr 2011 07:11:53 +0200 Original-Received: from localhost ([::1]:57296 helo=lists2.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QAEqO-0003ZR-Jq for ged-emacs-devel@m.gmane.org; Thu, 14 Apr 2011 01:11:52 -0400 Original-Received: from eggs.gnu.org ([140.186.70.92]:35781) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QAEqL-0003ZM-Kt for Emacs-devel@gnu.org; Thu, 14 Apr 2011 01:11:50 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1QAEqK-0007mT-9p for Emacs-devel@gnu.org; Thu, 14 Apr 2011 01:11:49 -0400 Original-Received: from fencepost.gnu.org ([140.186.70.10]:35027) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QAEqK-0007mP-72 for Emacs-devel@gnu.org; Thu, 14 Apr 2011 01:11:48 -0400 Original-Received: from eliz by fencepost.gnu.org with local (Exim 4.71) (envelope-from ) id 1QAEqJ-0002pC-UT; Thu, 14 Apr 2011 01:11:47 -0400 In-reply-to: (message from Ben Key on Wed, 13 Apr 2011 18:17:29 -0500) X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.6 (newer, 3) X-Received-From: 140.186.70.10 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:138470 Archived-At: > From: Ben Key > Date: Wed, 13 Apr 2011 18:17:29 -0500 > Cc: Emacs-devel@gnu.org > > The following is my first attempt at rewriting the section in nt/INSTALL > that used to warn against using quotes, backslashes and equal signs. Be > forewarned that writing documentation is not one of my strong points. Thanks. I suggest a slight rewording as follows: Because of limitations of the stock Windows command shells, special care is needed to pass some characters in the arguments of the --cflags and --ldflags options. Backslashes should not be used in file names passed to the compiler and linker via these options. Use forward slashes instead. If the arguments to these two options include the `=' character, like when passing a -DFOO=bar preprocessor option, the argument with the `=' character should be enclosed in quotes, like this: configure --cflags "-DFOO=bar" Support for options that include the `=' character require "command extensions" to be enabled. (They are enabled by default, but your system administrator could have changed that. See "cmd /?" for details.) If command extensions are disabled, a warning message might be displayed informing you that "using parameters that include the = character by enclosing them in quotes will not be supported." > Also, I need to know if the following comments in configure.bat are still > valid. > > Rem WARNING -- COMMAND.COM on some systems only looks at the first > Rem 8 characters of a label. So do NOT be tempted to change > Rem chkapi* into something fancier like checkw32api > Rem You HAVE been warned! You can delete that warning. You can also delete the parts of the batch file which probe the environment for enough space, that problem is also specific to command.com. But please make these two changes a separate commit, because they are unrelated to the issue of passing options with the `=' characters. > I would like to know if I can safely use labels that are longer than 8 > characters now. Yes, you can. But don't feel compelled to do that if you don't have to ;-) Thanks again for working on this.