unofficial mirror of bug-guile@gnu.org 
 help / color / mirror / Atom feed
From: Mark Harig <idirectscm@aim.com>
To: haberg-1@telia.com
Cc: bug-guile@gnu.org
Subject: Re: Guile 2.0.0 manual extensions example
Date: Fri, 25 Mar 2011 13:25:57 -0400	[thread overview]
Message-ID: <8CDB928D630C74A-AF0-2C504@Webmail-m109.sysops.aol.com> (raw)
In-Reply-To: <B9F832FB-5DDB-4619-8BEF-8DEF20AD572A@telia.com>

On Fri, Mar 25, 2011 at 05:50:58PM +0100, Hans Aberg wrote:

> The example in the Guile 2.0.0 manual, "Writing Guile
> Extensions", sec. 2.4, uses deprecated code, and does not
> indicate correct compiling options.
>
> Below is a modified code, which I compiled (Mac OS X
> 10.6.6) using
>  gcc `guile-config compile` `guile-config link` \
>  -dynamiclib -o libguile-bessel.so bessel.c
>
> Here, the guile-config part is necessary, as the headers
> are now in a subdirectory.  If excluded one will use the
> header from 1.8.
>

Andy Wingo reported that he had fixed the deprecated code in this
message (after Guile 2.0 was released):

http://lists.gnu.org/archive/html/bug-guile/2011-02/msg00114.html

Also, there has been some discussion of using "guile-config"
versus "pkg-config".  Bruno Haible asked the question
"guile-config deprecated or not?", starting here:

http://lists.gnu.org/archive/html/bug-guile/2011-02/msg00117.html

---



  reply	other threads:[~2011-03-25 17:25 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-25 16:50 Guile 2.0.0 manual extensions example Hans Aberg
2011-03-25 17:25 ` Mark Harig [this message]
2011-03-25 19:29   ` Hans Aberg

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=8CDB928D630C74A-AF0-2C504@Webmail-m109.sysops.aol.com \
    --to=idirectscm@aim.com \
    --cc=bug-guile@gnu.org \
    --cc=haberg-1@telia.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).