From: Andy Wingo <wingo@pobox.com>
To: ludo@gnu.org (Ludovic Courtès)
Cc: bug-guile@gnu.org
Subject: Re: [1.9.12][OpenBSD] run time failure ...
Date: Sun, 12 Sep 2010 22:26:15 +0200 [thread overview]
Message-ID: <m3aanmemjc.fsf@unquote.localdomain> (raw)
In-Reply-To: <87pqwi6eqq.fsf@gnu.org> ("Ludovic Courtès"'s message of "Sun, 12 Sep 2010 19:41:49 +0200")
Heya,
On Sun 12 Sep 2010 19:41, ludo@gnu.org (Ludovic Courtès) writes:
>> This is a bit ridiculous. Let's just pull all that srfi C code into the
>> core.
>
> Yes, but some projects might link directly against libguile-srfi-srfi*,
> so we may need to keep them around (that was my thinking for SRFI-1.)
You know what, I don't think we do. Currently to link to e.g. srfi-1,
one needs to do a `-lguile-srfi-srfi-1-v-4'. guile-config doesn't
provide this information, especially the "-v-4", and it isn't encoded
anywhere within Guile as far as I can tell, and certainly not in the
manual. I can't pull up any uses on any of the code search sites.
So that means no one is using it. We may safely remove those libs, and
those header files.
I'm not usually so rash regarding removing interfaces, but I would be
surprised if this affected anyone at all.
Andy
--
http://wingolog.org/
next prev parent reply other threads:[~2010-09-12 20:26 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-08 19:21 [1.9.12][OpenBSD] run time failure primus
2010-09-08 19:46 ` Andy Wingo
2010-09-08 20:07 ` primus
2010-09-08 21:58 ` Ludovic Courtès
2010-09-08 22:12 ` primus
2010-09-10 8:39 ` Andy Wingo
2010-09-10 13:47 ` primus
2010-09-10 14:35 ` Andy Wingo
2010-09-10 15:44 ` primus
2010-09-10 21:37 ` Ludovic Courtès
2010-09-10 16:44 ` [1.9.12][OpenBSD] [SOLUTION] " primus
2010-09-10 21:29 ` [1.9.12][OpenBSD] " Ludovic Courtès
2010-09-12 11:32 ` Andy Wingo
2010-09-12 17:41 ` Ludovic Courtès
2010-09-12 20:26 ` Andy Wingo [this message]
2010-09-12 20:38 ` Ludovic Courtès
2010-09-12 21:41 ` Andy Wingo
2010-09-08 23:06 ` [1.9.12][OpenBSD] CFLAGS="-g -O0" " primus
2010-09-10 8:41 ` Andy Wingo
2010-09-10 13:53 ` primus
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=m3aanmemjc.fsf@unquote.localdomain \
--to=wingo@pobox.com \
--cc=bug-guile@gnu.org \
--cc=ludo@gnu.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).