From: Wilfred Hughes <me@wilfred.me.uk>
To: Stefan Husmann <stefan-husmann@t-online.de>
Cc: guile-devel@gnu.org
Subject: Re: Building Guilemacs
Date: Mon, 5 Sep 2016 00:37:57 -0400 [thread overview]
Message-ID: <CAFXAjY4KNVmNaTy3oZphXmfhxm_bGOBU9=K4EJAGuj7EZ27Tqg@mail.gmail.com> (raw)
In-Reply-To: <8737lggif0.fsf@frege.i-did-not-set--mail-host-address--so-tickle-me>
[-- Attachment #1: Type: text/plain, Size: 2488 bytes --]
Digging some more, I think the issue is
http://debbugs.gnu.org/cgi/bugreport.cgi?bug=24065 . Emacs trunk is
depending on undefined C behaviour, which gcc 5 has started optimising,
breaking the code.
I've updated https://www.emacswiki.org/emacs/GuileEmacsBuild to note this.
You can work around with -fno-builtin-malloc or simply compile with clang
(my current solution).
Emacs trunk has fixed this (in 4b1436b702d56eedd27a0777fc7232cdfb7ac4f6
IIUC), but I believe that commit does not exist in the guile-emacs fork.
Wilfred
On 4 September 2016 at 04:48, Stefan Husmann <stefan-husmann@t-online.de>
wrote:
> Wilfred Hughes <me@wilfred.me.uk> writes:
>
> > I've had a play with the AUR packages too. The guile4emacs PKGBUILD works
> > perfectly, but the guile-emacs build process segfaults when
> bootstrap-emacs
> > attempts to load calendar/cal-loaddefs.el:
> >
> > make[2]: Leaving directory
> > '/home/wilfred/aur/guile-emacs-git/src/guilemacs/lisp'
> > if test "yes" = "yes"; then \
> > rm -f bootstrap-emacs; \
> > ln temacs bootstrap-emacs; \
> > else \
> > ./temacs --batch --load loadup bootstrap || exit 1; \
> > test "X" = X || -zex emacs; \
> > mv -f emacs bootstrap-emacs; \
> > fi
> > make -C ../lisp autoloads EMACS="../src/bootstrap-emacs"
> > make[2]: Entering directory
> > '/home/wilfred/aur/guile-emacs-git/src/guilemacs/lisp'
> > EMACSLOADPATH= '../src/bootstrap-emacs' -batch --no-site-file
> > --no-site-lisp -l autoload \
> > --eval "(setq generate-autoload-cookie \";;;###cal-autoload\")" \
> > --eval "(setq generated-autoload-file (expand-file-name
> > (unmsys--file-name \"calendar/cal-loaddefs.el\")))" \
> > -f batch-update-autoloads ./calendar
> > make[2]: *** [Makefile:466: calendar/cal-loaddefs.el] Segmentation fault
> > (core dumped)
> > make[2]: Leaving directory
> > '/home/wilfred/aur/guile-emacs-git/src/guilemacs/lisp'
> > make[1]: *** [Makefile:805: ../lisp/loaddefs.el] Error 2
> > make[1]: Leaving directory
> > '/home/wilfred/aur/guile-emacs-git/src/guilemacs/src'
> > make: *** [Makefile:376: src] Error 2
> > ==> ERROR: A failure occurred in build().
> > Aborting...
> >
> > Any suggestions?
> >
> > On 30 August 2016 at 20:32, Wilfred Hughes <me@wilfred.me.uk> wrote:
> >
> Hello,
>
> I can confirm this, but currently have no ideas what is going on
> here. This definitely used to work, but gcc was updated since then.
>
> Sorry for inconveniance. I will try to dig deeper into it.
>
> Best Regards
>
> Stefan
>
[-- Attachment #2: Type: text/html, Size: 3605 bytes --]
next prev parent reply other threads:[~2016-09-05 4:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-30 4:37 Building Guilemacs Wilfred Hughes
2016-08-30 16:07 ` Christopher Allan Webber
[not found] ` <87wpixnbyi.fsf@frege.i-did-not-set--mail-host-address--so-tickle-me>
2016-08-31 0:32 ` Wilfred Hughes
2016-09-03 23:57 ` Wilfred Hughes
2016-09-04 8:48 ` Stefan Husmann
2016-09-05 4:37 ` Wilfred Hughes [this message]
2016-09-05 18:04 ` Christopher Allan Webber
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/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAFXAjY4KNVmNaTy3oZphXmfhxm_bGOBU9=K4EJAGuj7EZ27Tqg@mail.gmail.com' \
--to=me@wilfred.me.uk \
--cc=guile-devel@gnu.org \
--cc=stefan-husmann@t-online.de \
/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.
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).