unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Christopher Allan Webber <cwebber@dustycloud.org>
To: Wilfred Hughes <me@wilfred.me.uk>
Cc: guile-devel@gnu.org
Subject: Re: Building Guilemacs
Date: Tue, 30 Aug 2016 11:07:42 -0500	[thread overview]
Message-ID: <8760qi8ckx.fsf@dustycloud.org> (raw)
In-Reply-To: <CAFXAjY6Lmo3W4Yc1HjDyU8678z=YFeU09zxTGCC_3JeeLT+DSQ@mail.gmail.com>

Wilfred Hughes writes:

> Hi folks
>
> I fancied exploring Guile with Emacs, so I've been trying to build Guile
> and Emacs as documented in https://www.emacswiki.org/emacs/GuileEmacsBuild .

Excellent!  Happy to hear of your interest.

> I've successfully built the wip-elisp branch of the main guile repo. The
> wiki page discusses http://git.hcoop.net/?p=bpt/guile.git and
> http://git.savannah.gnu.org/cgit/guile.git/log/?h=wip-elisp . I understand
> that the latter is a rebase of the hcoop commits on Guile 2.1.
>
> However, I've also noticed there's a wip-bpt-elisp branch in the main guile
> repo. This has the newest commits, but it seems to based on an older guile
> version.
>
> Which branch should I use?

wip-bpt-elisp has commits from years ago; wip-elisp is rebased on top of
relatively-recent master, with updated ChangeLog.  This was based on the
recent work of robin's from
http://git.savannah.gnu.org/cgit/guile.git/log/?h=wip-elisp

So, you want wip-elisp in origin.  That's the most up to date.

> I've also failed to compile the Emacs branch that uses Guile. I'm getting
> the error:
>
> gcc -c  -Demacs  -I. -I. -I../lib -I./../lib  [many includes elided...]
> -I/usr/local/include/guile/2.2   -g3 -O2  vm-limit.c
> In file included from vm-limit.c:21:0:
> lisp.h:33:22: fatal error: libguile.h: No such file or directory
>  #include <libguile.h>
>                       ^
> compilation terminated.
>
> This rather looks like I've screwed up with autoconf somehow. I've set the
> environment variables suggested by the wiki page:

I don't have time to look into this part, maybe someone else can help
you out!



  reply	other threads:[~2016-08-30 16:07 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 [this message]
     [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
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=8760qi8ckx.fsf@dustycloud.org \
    --to=cwebber@dustycloud.org \
    --cc=guile-devel@gnu.org \
    --cc=me@wilfred.me.uk \
    /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).