unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Juanma Barranquero <lekktu@gmail.com>
Cc: sean.sieger@gmail.com, monnier@iro.umontreal.ca, emacs-devel@gnu.org
Subject: Re: Failed to compile from last bzr repo
Date: Tue, 05 Apr 2011 19:52:44 +0300	[thread overview]
Message-ID: <83tyecvdwj.fsf@gnu.org> (raw)
In-Reply-To: <BANLkTikxzimwSjTdQyf8CszFi1CoTdjm_g@mail.gmail.com>

> From: Juanma Barranquero <lekktu@gmail.com>
> Date: Tue, 5 Apr 2011 18:36:38 +0200
> Cc: Stefan Monnier <monnier@iro.umontreal.ca>, emacs-devel@gnu.org
> 
> There are other checks you can enable, like GLYPH_DEBUG, FONT_DEBUG
> and DEBUG_GCPRO, but you have to do it by hand. This is as easy as
> passing "--cflags -DFONT_DEBUG" to configure, except in the case of
> GLYPH_DEBUG, which must be set to 1. This is currently unsupported on
> Windows (cmd.exe interprets "=" as a separator, so it doesn't grok
> -DGLYPH_DEBUG=1).

Maybe we should do on nt/config.nt

 #ifdef GLYPH_DEBUG
 # undef GLYPH_DEBUG
 # define GLYPH_DEBUG 1
 #endif

Then a simple "--cflags -DGLYPH_DEBUG" option to configure will do.

WDYT?



  reply	other threads:[~2011-04-05 16:52 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-04  9:46 Failed to compile from last bzr repo Bastien
2011-04-04 11:53 ` Eli Zaretskii
2011-04-04 12:22   ` Deniz Dogan
2011-04-04 12:38     ` Sean Sieger
2011-04-04 17:37       ` Eli Zaretskii
2011-04-04 21:19         ` Juanma Barranquero
2011-04-04 21:51           ` Stefan Monnier
2011-04-04 22:00             ` Juanma Barranquero
2011-04-05 13:14               ` Stefan Monnier
2011-04-05 15:39                 ` Sean Sieger
2011-04-05 16:36                   ` Juanma Barranquero
2011-04-05 16:52                     ` Eli Zaretskii [this message]
2011-04-05 22:45                       ` Juanma Barranquero
2011-04-06  3:01                         ` Eli Zaretskii
2011-04-06  3:22                           ` Juanma Barranquero
2011-04-06 12:57                             ` Andy Moreton
2011-04-06 13:32                               ` Eli Zaretskii
2011-04-06 14:18                                 ` Juanma Barranquero
2011-04-06 15:47                                   ` Eli Zaretskii
2011-04-06 16:08                                     ` Eli Zaretskii
2011-04-06 16:18                                     ` Juanma Barranquero
2011-04-05 15:41                 ` Sean Sieger
2011-04-05 20:57                   ` Stefan Monnier
2011-04-05  0:13             ` Sean Sieger
2011-04-05  2:59           ` Eli Zaretskii
2011-04-04 16:39     ` Stefan Monnier
2011-04-04 17:35     ` Eli Zaretskii
2011-04-04 16:26   ` Bastien

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

  List information: https://www.gnu.org/software/emacs/

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

  git send-email \
    --in-reply-to=83tyecvdwj.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=lekktu@gmail.com \
    --cc=monnier@iro.umontreal.ca \
    --cc=sean.sieger@gmail.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 public inbox

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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).