From: Stefan Monnier <monnier@IRO.UMontreal.CA>
To: Paul Eggert <eggert@cs.ucla.edu>
Cc: 31118@debbugs.gnu.org
Subject: bug#31118: 27.0.50; Can't load/compile websocket in 32bit master
Date: Sun, 15 Apr 2018 21:26:54 -0400 [thread overview]
Message-ID: <jwvfu3wq715.fsf-monnier+emacsbugs@gnu.org> (raw)
In-Reply-To: <80fbbf82-c20f-6a01-b257-45caa4a87fdf@cs.ucla.edu> (Paul Eggert's message of "Sun, 15 Apr 2018 15:11:50 -0700")
> Although I still can't build ELPA (see Bug#31118#31), I took a shot at
> making ELPA build for 32-bit Emacs on master by installing the attached
> patches into the xelb and exwm packages, respectively.
I think a major problem remains: these problems in GNU ELPA packages
probably also affect other packages that we can't patch so easily.
So I think we should reconsider whether reading something like
#xffffffff in a 32bit build should signal an error.
More specifically, I think we should first make it emit a warning, while
keeping the old broken behavior. Then in a later release we can make it
signal an error.
Stefan
next prev parent reply other threads:[~2018-04-16 1:26 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-10 3:03 bug#31118: 27.0.50; Can't load/compile websocket in 32bit master Stefan Monnier
2018-04-10 22:41 ` Paul Eggert
2018-04-11 1:56 ` Stefan Monnier
2018-04-11 8:07 ` Paul Eggert
[not found] ` <mvmwoxe40f3.fsf@suse.de>
2018-04-11 8:35 ` Paul Eggert
2018-04-11 12:19 ` Stefan Monnier
2018-04-11 12:47 ` Basil L. Contovounesios
2018-04-11 16:22 ` Paul Eggert
2018-04-11 18:37 ` Stefan Monnier
2018-04-11 19:47 ` Glenn Morris
2018-04-15 22:11 ` Paul Eggert
2018-04-16 1:26 ` Stefan Monnier [this message]
2018-04-17 7:50 ` Paul Eggert
2018-04-17 12:18 ` Stefan Monnier
2018-04-17 23:53 ` Paul Eggert
2018-04-18 12:22 ` Stefan Monnier
2018-04-18 19:50 ` Paul Eggert
2018-04-11 16:41 ` Eli Zaretskii
2018-04-11 18:38 ` Stefan Monnier
2018-04-12 12:50 ` Eli Zaretskii
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=jwvfu3wq715.fsf-monnier+emacsbugs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=31118@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.