all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Juanma Barranquero <lekktu@gmail.com>
To: Christoph <cschol2112@googlemail.com>
Cc: 6820-done@debbugs.gnu.org
Subject: bug#6820: 24.0.50; Corrupt system-configuration-options variable when using forward slashes
Date: Thu, 23 Sep 2010 01:22:45 +0200	[thread overview]
Message-ID: <AANLkTi=keq2RwtHOHS_2Hme336O0bgtfm9bZNKbaM7+O@mail.gmail.com> (raw)
In-Reply-To: <4C5EB7C3.5030705@gmail.com>

> On Windows, the following warning appears when specifying compiler flags for
> configure.bat with forward slashes:
>
> gcc -I. -c -gdwarf-2 -g3 -mno-cygwin -mtune=pentium4 -O2 -DENABLE_CHECKING
> -DXASSERTS -fno-crossjumping -IC:\Progra~2\GnuWin32\include
> -ID:\devel\emacs\libXpm-3.5.8\include -ID:\devel\emacs\libXpm-3.5.8\src
> -Demacs=1 -DHAVE_CONFIG_H -I../nt/inc -DHAVE_NTGUI=1 -DUSE_CRT_DLL=1 -o
> oo-spd/i386/w32.o w32.c

You mean backslashes. :-)

Currently we don't support passing backslashes or quotes in arguments
to the --cflags configure.bat option, because as you point out they
break compilation of w32.c:get_emacs_configuration_options.

There's no easy way to fix that from configure.bat in a simple and
portable way; the next best fix is just err out with a clear message
when running configure.bat so the user can react immediately, instead
of getting a not-so-clear error or warning during compilation.

I've implemented the check only for GCC because I don't have access to
MSVC; but it should be trivial to add if MSVC has some command option
similar to GCC's -Werror (turn any warning into an error).

    Juanma





      reply	other threads:[~2010-09-22 23:22 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-08 13:57 bug#6820: 24.0.50; Corrupt system-configuration-options variable when using forward slashes Christoph
2010-09-22 23:22 ` Juanma Barranquero [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='AANLkTi=keq2RwtHOHS_2Hme336O0bgtfm9bZNKbaM7+O@mail.gmail.com' \
    --to=lekktu@gmail.com \
    --cc=6820-done@debbugs.gnu.org \
    --cc=cschol2112@googlemail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.