unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Paul Eggert <eggert@cs.ucla.edu>
To: Pip Cet <pipcet@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: [EXPERIMENT] Emacs with the SpiderMonkey garbage collector
Date: Fri, 24 Nov 2017 16:21:41 -0800	[thread overview]
Message-ID: <0da2cda4-707c-5d1d-9b19-f9312595cb74@cs.ucla.edu> (raw)
In-Reply-To: <CAOqdjBerV-T6gwFN+gT-txsNDAQhzZXTBFERJpx=Vh8dhjtTVw@mail.gmail.com>

Pip Cet wrote:

> I have to remove the memrchr prototype.

Why just memrchr? I would think that if it has problems, other gnulib functions 
will have similar problems.

? Editing gnulib.mk seems like
> it should help, but for some reason it doesn't; is gnulib.mk
> regenerated by autogen.sh, and, if so, how do I change its options?

lib/gnulib.mk is regenerated by 'configure'. You can change how this happens by 
changing 'configure.ac', which is the source code for 'configure'.

'configure' creates lib/gnulib.mk by using lib/gnulib.mk.in as a template. This 
template file is created by admin/merge-gnulib, a script that is so obscure and 
so slow that we put its output into the repository (so most developers don't 
have to worry about it or run it).

admin/merge-gnulib gets the template text by running ../gnulib/gnulib-tool, 
which in turn gets the template text from files in ../gnulib/modules/*. Here I'm 
ssuming the Gnulib source code is in a sibling directory to the Emacs source code.

>>> The other issues are minor (a union and a typedef sharing a name, C++
>>> keywords, enums treated as ints),
> ...
> So let's do the first and maybe the keywords, but leave the enums in.

Sounds good.




  reply	other threads:[~2017-11-25  0:21 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-23 19:01 [EXPERIMENT] Emacs with the SpiderMonkey garbage collector Pip Cet
2017-11-24  8:07 ` Paul Eggert
2017-11-24 16:23   ` Pip Cet
2017-11-24 18:20     ` Paul Eggert
2017-11-24 23:27       ` Pip Cet
2017-11-25  0:21         ` Paul Eggert [this message]
2017-11-25 23:50           ` Pip Cet
2017-11-24 22:13 ` Stefan Monnier
2017-11-24 23:05   ` Pip Cet
2017-11-25  4:15     ` Stefan Monnier
2017-11-25 23:50       ` Pip Cet
2017-11-26  1:20         ` Stefan Monnier
2017-11-26  4:20           ` Paul Eggert
2017-11-26  5:11             ` Stefan Monnier
2017-11-26 10:27         ` martin rudalics
     [not found]         ` <jwva7z9rgqh.fsf&#45;monnier+Inbox@gnu.org>
     [not found]           ` <9d7be625&#45;85ae&#45;54d5&#45;3897&#45;6f701c8ea124@cs.ucla.edu>
     [not found]             ` <jwvo9npprfw.fsf&#45;monnier+emacs@gnu.org>
2017-12-01  1:03               ` Steve Fink
     [not found] <CAOqdjBe98BpWE&#45; Ey8fPY1DmfCiLYnB06d30Xqf_KMm_muvKbDg@mail.gmail.com>
2017-12-01 17:57 ` Steve Fink
2017-12-03  0:37   ` Pip Cet
2017-12-03  5:24     ` Steve Fink

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=0da2cda4-707c-5d1d-9b19-f9312595cb74@cs.ucla.edu \
    --to=eggert@cs.ucla.edu \
    --cc=emacs-devel@gnu.org \
    --cc=pipcet@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).