unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Mark H Weaver <mhw@netris.org>
Cc: Andy Wingo <wingo@pobox.com>, guile-devel@gnu.org
Subject: Re: About Guile crypto support
Date: Sat, 09 Feb 2013 22:53:06 +0100	[thread overview]
Message-ID: <87zjzd9mt9.fsf@gnu.org> (raw)
In-Reply-To: <87zjzd4br8.fsf@tines.lan> (Mark H. Weaver's message of "Sat, 09 Feb 2013 12:50:51 -0500")

Mark H Weaver <mhw@netris.org> skribis:

> Andy Wingo <wingo@pobox.com> writes:
>
>> On Sat 09 Feb 2013 16:12, ludo@gnu.org (Ludovic Courtès) writes:
>>
>>> An issue with the FFI is distros where .la and .so files are only
>>> available in the -dev package, because then ‘dynamic-link’ won’t work
>>> unless that -dev package is installed (as recently discussed on
>>> guile-user.)
>>
>> I have the feeling that we should implement our own dynamic-link
>> function without libltdl.  It would eliminate a dependency and allow us
>> to use other search path rules, like ones that could deal with this
>> case.  I think the situation would actually be better on other
>> architectures because we wouldn't have to deal with bugs like this one:
>>
>>   http://thread.gmane.org/gmane.lisp.guile.bugs/5269
>
> The problems we're having with libltdl are likely affecting many other
> projects.  Wouldn't it be better to fix these problems in libltdl,

Agreed.

On one hand, that will take more time than rolling our own.  On the
other, that will save us many headaches (incompatibility with previous
Guile versions, maintenance of our own stuff, proliferation of search
path rules, etc.)

Ludo’.



  parent reply	other threads:[~2013-02-09 21:53 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 [this message]
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
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=87zjzd9mt9.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=guile-devel@gnu.org \
    --cc=mhw@netris.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).