unofficial mirror of bug-guile@gnu.org 
 help / color / mirror / Atom feed
From: Andy Wingo <wingo@pobox.com>
To: Nick Cripps <nick.cripps@gmail.com>
Cc: bug-guile@gnu.org, Neil Jerram <neiljerram@gmail.com>
Subject: Re: Test fail in Guile-1.8.5
Date: Wed, 08 Dec 2010 11:26:03 +0100	[thread overview]
Message-ID: <m3sjy8ef2c.fsf@unquote.localdomain> (raw)
In-Reply-To: <B16142FB-7DC4-45F8-88BC-2DC6C218BAF3@gmail.com> (Nick Cripps's message of "Wed, 8 Dec 2010 05:08:49 +0000")

On Wed 08 Dec 2010 06:08, Nick Cripps <nick.cripps@gmail.com> writes:

> I tried building 1.8.7 on the same debian installation but, had the same
> problem as before. The same test fails.

Thanks for testing. Looking harder, I found:

    a0aa1e5b69d6ef0311aeea8e4b9a94eae18a1aaf
    Author: Ludovic Courtès <ludo@gnu.org>  2009-12-14 10:59:25

    Fix test environment issue with ltdl from Libtool 2.2.6b.
    
    Earlier versions of ltdl would look for extensions under $PWD; this
    behavior changed in 2.2.6b.
    
    * test-suite/standalone/Makefile.am (TESTS_ENVIRONMENT): Define
      $builddir.
    
    * test-suite/standalone/test-asmobs: Specify the full path to
      `libtest-asmobs', using $builddir.

It seems we haven't released a 1.8 since last july; we need to do that
now, I guess.

Andy
-- 
http://wingolog.org/



  reply	other threads:[~2010-12-08 10:26 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-04 22:12 Test fail in Guile-1.8.5 Nick Cripps
2010-12-07  9:34 ` Andy Wingo
2010-12-08  5:08   ` Nick Cripps
2010-12-08 10:26     ` Andy Wingo [this message]
2010-12-07 10:43 ` 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=m3sjy8ef2c.fsf@unquote.localdomain \
    --to=wingo@pobox.com \
    --cc=bug-guile@gnu.org \
    --cc=neiljerram@gmail.com \
    --cc=nick.cripps@gmail.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).