From: ludo@gnu.org (Ludovic Courtès)
To: Mike Gran <spk121@yahoo.com>
Cc: Andy Wingo <wingo@pobox.com>,
"guile-devel@gnu.org" <guile-devel@gnu.org>
Subject: Re: About Guile crypto support
Date: Mon, 11 Feb 2013 14:14:53 +0100 [thread overview]
Message-ID: <87pq07yotu.fsf@gnu.org> (raw)
In-Reply-To: <1360579612.97436.YahooMailNeo@web120404.mail.ne1.yahoo.com> (Mike Gran's message of "Mon, 11 Feb 2013 02:46:52 -0800 (PST)")
Mike Gran <spk121@yahoo.com> skribis:
> Right now, the Guile project does a poor job of testing Guile on
> multiple platforms. Hydra does check that i686-linux, x86_64-linux
> and x86_64-darwin compile, but, that's about the extent of multi-platform
> testing. (There are Hydra jobs for Cygwin and Solaris, but, they are
> broken; and FreeBSD hasn't built successfully in a year or so on 2.0)
Actually --without-threads builds work on FreeBSD, but there’s a known
problem in the tracker about threading there.
I see the Darwin machines at hydra.nixos.org are currently down, I’ll
ping the admins (Darwin builds have been fairly reliable over the
years.)
I admit that Solaris and Cygwin are more problematic, though I did some
work in the past to help with those.
> Guile has some talented hackers, and maybe they could write a better
> dynamic linker than libtool, but, history suggests that Guile might
> lose interest in maintaining such code for non-GNU systems.
I tend to agree. This is typically where ltdl is supposed to help.
Ludo’.
next prev parent reply other threads:[~2013-02-11 13:14 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-03 12:55 About Guile crypto support Nala Ginrut
2013-02-03 15:37 ` Thien-Thi Nguyen
2013-02-04 1:14 ` Daniel Hartwig
2013-02-04 3:12 ` Nala Ginrut
2013-02-04 3:35 ` Daniel Hartwig
2013-02-04 4:15 ` Nala Ginrut
2013-02-04 23:03 ` Ludovic Courtès
2013-02-05 2:43 ` Nala Ginrut
2013-02-05 2:57 ` Noah Lavine
2013-02-06 13:58 ` Nala Ginrut
2013-02-05 15:48 ` Ludovic Courtès
2013-02-06 4:18 ` Daniel Hartwig
2013-02-06 4:28 ` Daniel Hartwig
2013-02-08 16:21 ` Ludovic Courtès
2013-02-09 1:37 ` Daniel Hartwig
2013-02-09 15:12 ` Ludovic Courtès
2013-02-09 17:02 ` Andy Wingo
2013-02-09 17:50 ` Mark H Weaver
2013-02-09 20:44 ` Noah Lavine
2013-02-09 21:53 ` Ludovic Courtès
2013-02-11 8:20 ` Andy Wingo
2013-02-11 9:15 ` Thien-Thi Nguyen
2013-02-11 10:46 ` Mike Gran
2013-02-11 13:14 ` Ludovic Courtès [this message]
2013-02-11 9:51 ` Nala Ginrut
2013-02-11 15:23 ` Greg Troxel
2013-02-12 1:12 ` Daniel Hartwig
2013-02-12 4:20 ` Nala Ginrut
2013-02-12 5:21 ` Daniel Hartwig
2013-02-12 7:40 ` Dynamic FFI vs Static FFI (was Re: About Guile crypto support) Mark H Weaver
2013-02-12 13:52 ` Ludovic Courtès
2013-02-12 18:24 ` Mark H Weaver
2013-02-12 21:49 ` Ludovic Courtès
2013-02-14 7:21 ` William ML Leslie
2013-02-15 13:34 ` Nala Ginrut
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=87pq07yotu.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guile-devel@gnu.org \
--cc=spk121@yahoo.com \
--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).