unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Greg Troxel <gdt@ir.bbn.com>
To: Andy Wingo <wingo@pobox.com>
Cc: guile-devel@gnu.org
Subject: Re: build of master now fails much earlier
Date: Mon, 21 Sep 2009 09:26:47 -0400	[thread overview]
Message-ID: <rmid45ke8dk.fsf@fnord.ir.bbn.com> (raw)
In-Reply-To: <m3ljkc9vfe.fsf@pobox.com> (Andy Wingo's message of "Fri, 18 Sep 2009 16:31:01 +0200")

[-- Attachment #1: Type: text/plain, Size: 2184 bytes --]


  > are we really adding dependencies while we are 'frozen'???
  >
  > checking for BDW_GC... configure: error: Package requirements (bdw-gc)
  > were not met:

  Sorry if we did not communicate clearly; the plan was definitely to
  merge in bdw-gc before the release, and possibly during the freeze
  period.

Probably you did.  I am just barely able to pay attention, and likely
forgot - while I see the point this kind of change in freeze is unusual.

I installed pkgsrc/devel/boehm-gc and then:


gmake[3]: Entering directory `/home/gdt/BUILD-GUILE-master/guile/libguile'
/bin/ksh ../libtool --tag=CC   --mode=link gcc -I/usr/pkg/include -I/usr/y0/include -pthread -Wall -Wmissing-prototypes -Werror -fvisibility=hidden -I/usr/pkg
include   -g -O2 -I/usr/pkg/include -I/usr/y0/include -pthread -L/usr/pkg/lib -R/usr/pkg/lib -L/usr/y0/lib -R/usr/y0/lib -Wl,-z -Wl,relro -o guile guile-guile
o libguile.la -L/usr/pkg/lib -lgc   -L/usr/y0/lib -lunistring -R/usr/y0/lib -lcrypt -lm -lltdl 
gcc -I/usr/pkg/include -I/usr/y0/include -pthread -Wall -Wmissing-prototypes -Werror -fvisibility=hidden -I/usr/pkg/include -g -O2 -I/usr/pkg/include -I/usr/y
/include -pthread -Wl,-z -Wl,relro -o .libs/guile guile-guile.o  -L/usr/pkg/lib -L/usr/y0/lib ./.libs/libguile.so /usr/pkg/lib/libintl.so -lc /usr/pkg/lib/lib
mp.so /usr/pkg/lib/libgc.so /usr/y0/lib/libunistring.so -lcrypt -lm /usr/pkg/lib/libltdl.so  -Wl,--rpath -Wl,/usr/local/lib -Wl,--rpath -Wl,/usr/pkg/lib -Wl,-
rpath -Wl,/usr/y0/lib
./.libs/libguile.so: warning: warning: tmpnam() possibly used unsafely, use mkstemp() or mkdtemp()
./.libs/libguile.so: undefined reference to `GC_pthread_detach'
./.libs/libguile.so: undefined reference to `GC_pthread_create'
./.libs/libguile.so: undefined reference to `GC_pthread_sigmask'
gmake[3]: *** [guile] Error 1



Perhaps boehm-gc can be built with thread support?  The guile README
doesn't seem to say anything about this.  pkgsrc does have the ability
to configure with thread support, but by default doesn't.  I don't know
why - but usually there are programs that want it and programs that
can't have it, leading to trouble.  I will inquire.

[-- Attachment #2: Type: application/pgp-signature, Size: 193 bytes --]

      parent reply	other threads:[~2009-09-21 13:26 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-18 11:29 build of master now fails much earlier Greg Troxel
2009-09-18 14:31 ` Andy Wingo
2009-09-18 20:36   ` Neil Jerram
2009-09-21 13:26   ` Greg Troxel [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=rmid45ke8dk.fsf@fnord.ir.bbn.com \
    --to=gdt@ir.bbn.com \
    --cc=guile-devel@gnu.org \
    --cc=wingo@pobox.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).