unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Neil Jerram <neil@ossau.uklinux.net>
To: Andy Wingo <wingo@pobox.com>
Cc: guile-devel <guile-devel@gnu.org>
Subject: Re: what do to if there is no %nil
Date: Mon, 18 Jan 2010 20:23:50 +0000	[thread overview]
Message-ID: <87fx63f9gp.fsf@ossau.uklinux.net> (raw)
In-Reply-To: <m34omjii1u.fsf@pobox.com> (Andy Wingo's message of "Mon, 18 Jan 2010 15:50:05 +0100")

Andy Wingo <wingo@pobox.com> writes:

> On Mon 18 Jan 2010 15:23, Mike Gran <spk121@yahoo.com> writes:
>
>> I tried building master with the --disable-elisp configure option.
>> When that option is enabled, libguile no longer contains the %nil value.
>> The assembler expects %nil to always exist.
>>
>> I made a quick and dirty modification in 
>> 7beae9f15ac49f144a15d3ebfe80c2f29e43b3ff just to get it to build; but,
>> I'm sure that a prettier solution should implemented.
>
> I saw that patch, and it looked fine to me. I'd also be fine with just
> always building with %nil support (because that's basically all that
> --enable-elisp does, right?), but maybe that's just me...

Yes, I agree.  There are a couple of details in the reader that depend
on SCM_ENABLE_ELISP, that someone should check out.  Subject to
those being OK, I think we could remove the --disable-elisp option.

            Neil




      reply	other threads:[~2010-01-18 20:23 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-18 14:23 what do to if there is no %nil Mike Gran
2010-01-18 14:50 ` Andy Wingo
2010-01-18 20:23   ` Neil Jerram [this message]

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=87fx63f9gp.fsf@ossau.uklinux.net \
    --to=neil@ossau.uklinux.net \
    --cc=guile-devel@gnu.org \
    --cc=wingo@pobox.com \
    /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).