unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Darren Hoo <darren.hoo@gmail.com>
To: guile-devel@gnu.org
Subject: Re: [PATCH] Fix linker error on Debian sid
Date: Mon, 28 Feb 2011 16:35:37 +0800	[thread overview]
Message-ID: <878vx08skm.fsf@gmail.com> (raw)
In-Reply-To: 87vd0515g1.fsf@gmx.at

Andreas Rottmann <a.rottmann@gmx.at> writes:

> Hi!
>
> Attached is a patch that fixes a linker error in the test suite when
> using the default toolchain on Debian sid.  It should be applied to both
> master and stable-2.0, I think.
>

Thanks for the patch! 
I really should have checked the mailinglist first before I struggled
with the compiling of unreleased BDWGC.

Is using  the CVS version of BDWGC a must in order to get Guile
multithread  support? with your patch, I can successfully build it with
libgc 1:7.1-6 in Debian unstable now,  but check-TESTS can not pass
gc.test, I Ctrl-C it when it stucks. 





      parent reply	other threads:[~2011-02-28  8:35 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-27 22:24 [PATCH] Fix linker error on Debian sid Andreas Rottmann
2011-02-27 23:41 ` Ludovic Courtès
2011-02-28  8:35 ` Darren Hoo [this message]

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=878vx08skm.fsf@gmail.com \
    --to=darren.hoo@gmail.com \
    --cc=guile-devel@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).