From: Andy Wingo <wingo@pobox.com>
To: Mike Gran <spk121@yahoo.com>
Cc: guile-devel <guile-devel@gnu.org>
Subject: Re: [PATCH] more descriptive error for dynamic-pointer
Date: Thu, 31 Mar 2011 12:28:44 +0200 [thread overview]
Message-ID: <m339m3ziqr.fsf@unquote.localdomain> (raw)
In-Reply-To: <585637.53972.qm@web37902.mail.mud.yahoo.com> (Mike Gran's message of "Wed, 30 Mar 2011 20:51:14 -0700 (PDT)")
On Thu 31 Mar 2011 05:51, Mike Gran <spk121@yahoo.com> writes:
> dynamic-pointer relies on lt_dlerror for its error message, and that
> procedure can return the unhelpful string "No Error" when lt_dlsym
> fails to find a symbol. You might fix it like I did in the following
> patch.
Cool. Applied something similar.
Thanks,
Andy
--
http://wingolog.org/
next prev parent reply other threads:[~2011-03-31 10:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-31 3:51 [PATCH] more descriptive error for dynamic-pointer Mike Gran
2011-03-31 10:28 ` Andy Wingo [this message]
2011-03-31 14:32 ` Ludovic Courtès
2011-03-31 14:56 ` Andy Wingo
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=m339m3ziqr.fsf@unquote.localdomain \
--to=wingo@pobox.com \
--cc=guile-devel@gnu.org \
--cc=spk121@yahoo.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).