From: rm@fabula.de
Cc: Rob Browning <rlb@defaultvalue.org>,
Han-Wen Nienhuys <hanwen@cs.uu.nl>,
Dirk Herrmann <dirk@sallust.ida.ing.tu-bs.de>,
guile-devel@gnu.org
Subject: Re: Release Guile, now ;-) [was:] Re: GC rewrite, first version.
Date: Fri, 2 Aug 2002 13:59:15 +0200 [thread overview]
Message-ID: <20020802115915.GA9364@www> (raw)
In-Reply-To: <20020802093547.GA8943@www>
On Fri, Aug 02, 2002 at 11:35:47AM +0200, rm@fabula.de wrote:
> [...]
> and then have it processed by autoheader with an invocation like this:
>
> autoheader public_defines.ac
>
> that's all that's needed, as far as i understand.
Hit me on the forehead with the elsip manual for not testing this --
it doesn't work. Autoheader insists on emitting the offending #defines
even if given a custom input file (the offending macro is AC_INIT).
But browsing through the autoconf mailing list i found
http://mail.gnu.org/pipermail/autoconf/2002-June/013361.html
which seems to describe our problem. There's a reference to
http://ac-archive.sourceforge.net/Miscellaneous/ac_create_prefix_config_h.html
an autoconf macro that might just do what we want.
> >
> > But this looks like a non-trivial amount of work. I've already done
> > all the steps but the last in a test tree, but that's the big one.
> > So the question is, does this have to be done before 1.6.1?
>
> May i offer my help?
Since the aforementioned doen't exactly do what we need (it creates
a file prefixed with 'libguile-' rather than a file 'scmconfig.h.in')
i can offer to modify it so we have another guile macro (would
GUILE_CREATE_PUBLIC_HEADER be apropriate?).
Ralf Mattes
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2002-08-02 11:59 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-27 22:54 GC rewrite, first version Han-Wen
2002-07-28 16:40 ` Rob Browning
2002-07-29 20:11 ` Dirk Herrmann
2002-07-29 21:04 ` Rob Browning
2002-07-29 22:05 ` Han-Wen
2002-07-31 17:03 ` Dirk Herrmann
2002-07-31 18:02 ` Han-Wen Nienhuys
2002-07-31 21:15 ` Rob Browning
2002-08-01 9:20 ` Release Guile, now ;-) [was:] " rm
2002-08-01 16:27 ` Rob Browning
2002-08-01 16:44 ` rm
2002-08-01 18:37 ` Sergey Poznyakoff
2002-08-01 22:21 ` Rob Browning
2002-08-02 6:09 ` Sergey Poznyakoff
2002-08-02 14:36 ` Rob Browning
2002-08-02 17:29 ` Sergey Poznyakoff
2002-08-02 18:10 ` Bruce Korb
2002-08-02 19:50 ` Rob Browning
2002-08-03 7:13 ` Sergey Poznyakoff
2002-08-04 20:43 ` Bruce Korb
2002-08-04 20:57 ` Sergey Poznyakoff
2002-08-01 22:40 ` Rob Browning
2002-08-02 9:35 ` rm
2002-08-02 11:59 ` rm [this message]
2002-08-02 15:00 ` Rob Browning
2002-08-02 14:50 ` Rob Browning
2002-08-01 9:59 ` Han-Wen Nienhuys
2002-08-01 8:46 ` Marius Vollmer
2002-07-31 18:46 ` Neil Jerram
2002-08-01 9:58 ` Han-Wen Nienhuys
2002-07-28 16:51 ` Michael Livshin
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=20020802115915.GA9364@www \
--to=rm@fabula.de \
--cc=dirk@sallust.ida.ing.tu-bs.de \
--cc=guile-devel@gnu.org \
--cc=hanwen@cs.uu.nl \
--cc=rlb@defaultvalue.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.
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).