From: Thien-Thi Nguyen <ttn@gnuvola.org>
To: rvclayton@acm.org (r. clayton)
Cc: bug-guile@gnu.org
Subject: Re: guile-www 1.1.1 & 2.16 problems under guile 1.8.
Date: Fri, 11 May 2007 14:28:52 +0200 [thread overview]
Message-ID: <87irazh7cr.fsf@ambire.localdomain> (raw)
In-Reply-To: <87ps57hltc.fsf@laas.fr> ("Ludovic Courtès"'s message of "Fri\, 11 May 2007 09\:16\:31 +0200")
() ludovic.courtes@laas.fr (Ludovic Courtès)
() Fri, 11 May 2007 09:16:31 +0200
So your fix seems reasonable, _provided_ `guile-www' doesn't rely on
string mutations and interactions between substrings and their parent
string.
the easy way is to use configure script option --disable-shsub. i have
updated the README to mention this for the next release (2.19), like so:
You can use the configure script option `--disable-shsub' to
explicitly build a version where `make-shared-substring' is
replaced w/ simply `substring'. By default, configure arranges
for the replacement only if it can't detect that your Guile has
`make-shared-substring'.
if the configure script is NOT detecting missing `make-shared-substring',
then that's a bug -- please post the output of the ./configure run (w/o
the `--disable-shsub' option).
Maybe you could provide him with a patch allowing `guile-www'
to be used with both Guile versions?
this should likewise be handled automatically by configure (if not,
that's a bug). in the configure run output, there should be something
like "acts like (ice-9 optargs-kw) ...yes", and the installation script
module-install will read `need_optargs_kludge="no"'.
improvements to the detection routines welcome, in any case!
thi
_______________________________________________
Bug-guile mailing list
Bug-guile@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-guile
next prev parent reply other threads:[~2007-05-11 12:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-11 1:13 guile-www 1.1.1 & 2.16 problems under guile 1.8 r. clayton
2007-05-11 7:16 ` Ludovic Courtès
2007-05-11 12:28 ` Thien-Thi Nguyen [this message]
2007-05-11 14:43 ` Ludovic Courtès
2007-05-11 15:25 ` Thien-Thi Nguyen
2007-05-11 23:25 ` r. clayton
2007-05-12 14:06 ` Thien-Thi Nguyen
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=87irazh7cr.fsf@ambire.localdomain \
--to=ttn@gnuvola.org \
--cc=bug-guile@gnu.org \
--cc=rvclayton@acm.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).