unofficial mirror of bug-guile@gnu.org 
 help / color / mirror / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: bug-guile@gnu.org
Subject: Re: [PATCH] Declare `GC_dump' ourselves if <gc/gc.h> doesn't.
Date: Tue, 12 Jan 2010 18:19:44 +0100	[thread overview]
Message-ID: <87my0jfdfz.fsf@gnu.org> (raw)
In-Reply-To: 87hbqrmj2d.fsf@ambire.localdomain

Hi,

Thien-Thi Nguyen <ttn@gnuvola.org> writes:

> () ludo@gnu.org (Ludovic Courtès)
> () Tue, 12 Jan 2010 15:17:06 +0100
>
>    So how did ‘configure’ find your libgc?
>
> I've modified configure.ac (see "Don't clobber..." patch) to look like:
>
> | dnl See note for PKG_CHECK_MODULES in aclocal.m4.
> | PKG_PROG_PKG_CONFIG
> | if test "$BDW_GC_CFLAGS" || test "$BDW_GC_LIBS" ; then :
> |   dnl We don't need to declare those env vars precious;
> |   dnl PKG_CHECK_MODULES does that.
> | else
> |   PKG_CHECK_MODULES([BDW_GC], [bdw-gc])
> | fi

This patch shouldn’t be necessary since it duplicates what
‘PKG_CHECK_MODULES’ does.

> Then, i call configure like so:
>
> $ .../configure -C \
>       --with-threads \
>       --prefix /tmp/a/b/z \
>       BDW_GC_LIBS='-lgc' \

... without reading ‘README’, so you basically shoot yourself in the
foot and there’s not much we can do.  :-)

Thanks,
Ludo’.





  reply	other threads:[~2010-01-12 17:19 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-09 13:28 [PATCH] Declare `GC_dump' ourselves if <gc/gc.h> doesn't Thien-Thi Nguyen
2010-01-09 22:30 ` Andy Wingo
2010-01-10  2:37   ` Ken Raeburn
2010-01-11 22:09   ` Ludovic Courtès
2010-01-11 22:32     ` Ludovic Courtès
2010-01-12  4:51       ` Thien-Thi Nguyen
2010-01-12  4:40     ` Thien-Thi Nguyen
2010-01-12 14:17       ` Ludovic Courtès
2010-01-12 15:36         ` Thien-Thi Nguyen
2010-01-12 17:19           ` Ludovic Courtès [this message]
2010-01-12 18:51             ` Thien-Thi Nguyen
2010-01-12 19:33               ` Andy Wingo
2010-01-12 19:29     ` Andy Wingo
2010-01-12 22:42       ` Ludovic Courtès
2010-01-17 22:01   ` Neil Jerram

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=87my0jfdfz.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=bug-guile@gnu.org \
    /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).