From: tomas@fabula.de
Cc: rm@fabula.de
Subject: How to replace a function
Date: Fri, 7 Mar 2003 13:37:07 +0100 [thread overview]
Message-ID: <20030307123707.GA8811@www> (raw)
Hi, lists
we are trying to build a guile extension which should link
smoothly against 1.6 and 1.7. If possible, we would like
to use The Blessed Function (it's scm_c_string2str(), for
the record). But alas, 1.6 hasn't got that. It seems that
AC_REPLACE_FUNCS is the right macro (first do AC_CHECK_LIB,
right?).
The problem is that AC_REPLACE_FUNCS will find one version
of the Guile library, whereas the version I'm going to link
against is the one returned by `guile-config link' or whatever.
My question: Is there a canonical way to solve this? I.e.
is there a way to tell AC_REPLACE_FUNCS *which* library to
look into? Or is it just meant to cope with ``standard system
libraries'' and am I to re-invent the wheel and do a
tentative compile?
Thanks for any hints
-- tomas
next reply other threads:[~2003-03-07 12:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-07 12:37 tomas [this message]
2003-03-07 16:38 ` How to replace a function Rob Browning
2003-03-10 12:21 ` tomas
2003-03-07 16:44 ` Rob Browning
2003-03-10 12:25 ` tomas
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=20030307123707.GA8811@www \
--to=tomas@fabula.de \
--cc=rm@fabula.de \
/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).