unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: David Pirotte <david@altosw.be>
To: Mark H Weaver <mhw@netris.org>
Cc: guile-devel@gnu.org
Subject: Re: debian squeeze/sid - guile-master-20100617 [fails] now it's working
Date: Mon, 11 Oct 2010 16:12:06 -0300	[thread overview]
Message-ID: <20101011161206.08202c8e@rascar> (raw)
In-Reply-To: <87sk2b36bt.fsf@freedomincluded.MIT.EDU>

Hello,

	debian squeeze/sid - git clone of october the 12th, 2010
		...
		gcc			4:4.4.4-2
		libgc-dev 	1:7.1-3
		libgc1c2        	1:7.1-3
		...

Very sorry for the lonnnng delay! For me your suggestion didn't work. What worked is
the following [also manually defining LIBFFI_xxx vars]:

	export PKG_CONFIG=true
	export BDW_GC_CFLAGS=
	export BDW_GC_LIBS=-lgc
	export LIBFFI_CFLAGS=
	export LIBFFI_LIBS=-lffi
	./configure
	make

Thanks,
David

;; --

Le Wed, 18 Aug 2010 18:27:02 -0400,
Mark H Weaver <mhw@netris.org> a écrit :

> Reviving an old thread...
> 
> Recall that David Pirotte had trouble linking libguile-2.0.so because
> -lffi was not included in the link command, despite the fact that
> `pkg-config --libs libffi' did the right thing.
> 
> I ran into the same problem trying to build guile on gNewSense/mipsel.
> 
> In my case, the problem was that I had set PKG_CONFIG=true while running
> configure.  I did this because it was recommended by the README in the
> section on setting the BDW_GC_* variables.
> 
> Perhaps that was David's problem as well?
> 
>      Mark



      parent reply	other threads:[~2010-10-11 19:12 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-22 21:24 debian squeeze/sid - guile-master-20100617 fails David Pirotte
2010-07-02 13:03 ` Ludovic Courtès
2010-07-02 14:31   ` David Pirotte
2010-07-02 16:27     ` Ludovic Courtès
2010-07-04 12:15       ` David Pirotte
2010-08-18 22:27 ` Mark H Weaver
2010-08-28 17:42   ` Andy Wingo
2010-10-11 19:12   ` David Pirotte [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=20101011161206.08202c8e@rascar \
    --to=david@altosw.be \
    --cc=guile-devel@gnu.org \
    --cc=mhw@netris.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).