From: Svante Signell <srs@kth.se>
To: 9926@debbugs.gnu.org
Cc: eggert@cs.ucla.edu
Subject: bug#9926: patch: emacs-24.0.91 FTBFS on GNU/Hurd
Date: Tue, 08 Nov 2011 13:21:43 +0100 [thread overview]
Message-ID: <1320754903.5597.30.camel@s1499.it.kth.se> (raw)
In-Reply-To: 4EB77003.9040006@cs.ucla.edu
> I installed the following patch in the trunk as bzr 106311
> to fix the fails-to-compile bug.
>
> Making GC_MAKE_GCPROS_NOOPS the default sounds good, but as
> it doesn't fix a bug and we're in feature-freeze now I left
> that for later.
>
> === modified file 'src/ChangeLog'
> --- src/ChangeLog 2011-11-07 02:00:43 +0000
> +++ src/ChangeLog 2011-11-07 05:37:49 +0000
> @@ -1,3 +1,10 @@
> +2011-11-07 Paul Eggert <address@hidden>
> +
> + * alloc.c (DEADP): New macro, for porting to GNU/Hurd (Bug#9926).
> + This is also needed for porting to any host where GC_MARK_STACK is
> + not GC_MAKE_GCPROS_NOOPS.
> + (which_symbols): Use it.
Reading your patch shows that GC_MARK_STACK will still not be set for
GNU/Hurd. However, the previous comment by Stefan Monnier says that
GC_MAKE_GCPROS_NOOPS should be set as the default. So what is wrong
with patching gnu.h??
Anyway, which are the differences/consequences of that part of the code
in which_symbols being executed compared to not when GC_MARK_STACK is
unset or set to GC_MAKE_GCPROS_NOOPS?
next prev parent reply other threads:[~2011-11-08 12:21 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-31 22:54 bug#9926: patch: emacs-24.0.91 FTBFS on GNU/Hurd Svante Signell
2011-11-01 17:42 ` Stefan Monnier
2011-11-07 5:43 ` Paul Eggert
2011-11-08 12:21 ` Svante Signell [this message]
2011-11-08 13:31 ` Stefan Monnier
2011-11-08 16:44 ` Paul Eggert
2011-11-08 17:09 ` Stefan Monnier
2011-11-08 20:18 ` Paul Eggert
2011-11-08 17:23 ` Eli Zaretskii
2011-11-08 20:36 ` Paul Eggert
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=1320754903.5597.30.camel@s1499.it.kth.se \
--to=srs@kth.se \
--cc=9926@debbugs.gnu.org \
--cc=eggert@cs.ucla.edu \
/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.