From: Wilfred Hughes <me@wilfred.me.uk>
To: Stefan Husmann <stefan-husmann@t-online.de>, guile-devel@gnu.org
Subject: Re: Building Guilemacs
Date: Sat, 3 Sep 2016 19:57:33 -0400 [thread overview]
Message-ID: <CAFXAjY4F_FzLdcdq7E9p9aS+Aeh-gD1i3c=YsT1vkO475vkbJA@mail.gmail.com> (raw)
In-Reply-To: <CAFXAjY5kDjP3Ez718kCrPCgjSivTcpxHzGx_1ZuYE8xpa3A+2A@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2187 bytes --]
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:
> > I think the variables you mentioned are for building in your home
> > directory only. If you build system-wide, for instance under /usr/local
> > -- and your mail makes me think you do so -- you should not need them.
>
> I wanted to build them in my home directory. I already have Guile installed
> and I didn't want to get things confused.
>
> > I have made some packaging recipes for Arch Linux, and there it works
> > without specifing these variables.
> >
> > https://aur.archlinux.org/packages/guile-emacs-git/ (for emacs)
> > https://aur.archlinux.org/packages/guile4emacs-git/ (for guile)
>
> Oh, that's really useful, thanks. I'll have a look at those for
> reference (and I've documented them on the GuileEmacsBuild wiki
> build).
>
[-- Attachment #2: Type: text/html, Size: 3051 bytes --]
next prev parent reply other threads:[~2016-09-03 23:57 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 [this message]
2016-09-04 8:48 ` Stefan Husmann
2016-09-05 4:37 ` Wilfred Hughes
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='CAFXAjY4F_FzLdcdq7E9p9aS+Aeh-gD1i3c=YsT1vkO475vkbJA@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).