From: Glenn Morris <rgm@gnu.org>
To: emacs-devel@gnu.org
Cc: Paul Eggert <eggert@cs.ucla.edu>
Subject: Re: emacs-26 9e59de9: Use GCALIGNED properly for GCC
Date: Thu, 09 Nov 2017 18:31:59 -0500 [thread overview]
Message-ID: <r8o9ob58r4.fsf@fencepost.gnu.org> (raw)
In-Reply-To: 20171109031208.D2CAF2033E@vcs0.savannah.gnu.org
Paul Eggert wrote:
> branch: emacs-26
> commit 9e59de9449b53c3ecd85b624c11360ba9cafee75
[...]
> Use GCALIGNED properly for GCC
This seems to cause build failure on 32-bit GNU/Linux.
build.i686-linux on hydra fails since this commit was merged to master:
https://hydra.nixos.org/eval/1408828
(Sadly the hydra build logs seem to be missing at the moment, so there's
nothing informative there.)
I reproduced the issue on 64-bit RHEL7 building the emacs-26 branch with
./configure --without-all --without-x CC="gcc -m32"
The command "./temacs --batch --load loadup bootstrap" simply exits
immediately with no output and status 0.
With 9e59de9 reverted, the same build completes ok.
next parent reply other threads:[~2017-11-09 23:31 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20171109031206.7056.28312@vcs0.savannah.gnu.org>
[not found] ` <20171109031208.D2CAF2033E@vcs0.savannah.gnu.org>
2017-11-09 23:31 ` Glenn Morris [this message]
2017-11-10 7:10 ` emacs-26 9e59de9: Use GCALIGNED properly for GCC martin rudalics
2017-11-10 8:06 ` Eli Zaretskii
2017-11-10 8:26 ` Paul Eggert
2017-11-10 9:57 ` Eli Zaretskii
2017-11-10 16:23 ` Stefan Monnier
2017-11-10 17:58 ` Paul Eggert
2017-11-10 18:02 ` Stefan Monnier
2017-11-10 18:11 ` Philipp Stephani
2017-11-10 19:19 ` Paul Eggert
2017-11-10 20:31 ` Stefan Monnier
2017-11-10 20:45 ` Paul Eggert
2017-11-11 7:08 ` Paul Eggert
2017-11-11 7:57 ` Paul Eggert
2017-11-11 8:34 ` martin rudalics
2017-11-11 8:50 ` Paul Eggert
2017-11-11 9:46 ` martin rudalics
2017-11-11 8:33 ` martin rudalics
2017-11-13 18:19 ` Paul Eggert
2017-11-13 18:45 ` martin rudalics
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=r8o9ob58r4.fsf@fencepost.gnu.org \
--to=rgm@gnu.org \
--cc=eggert@cs.ucla.edu \
--cc=emacs-devel@gnu.org \
/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).