unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Rob Browning <rlb@defaultvalue.org>
Subject: Guile 1.5.7 beta available for testing.
Date: Tue, 20 Aug 2002 13:20:43 -0500	[thread overview]
Message-ID: <87n0rh2xz8.fsf@raven.i.defaultvalue.org> (raw)


We are pleased to annouce the availability of Guile 1.5.7 for testing.
Please report problems to guile-devel@gnu.org or bug-guile@gnu.org.

Note that the 1.5.X series is a BETA series, intended only for
testing, so please don't put it into a distribution or anything
similar.  If after two weeks, no agreed upon release-critical bugs
have been found, then the first 1.6 stable version, 1.6.1, will be
released.

You can find the file here:

  ftp://ftp.dt.e-technik.uni-dortmund.de/pub/guile/

If you're interested in testing, please try as much of the following
as is convenient:

        - Unset GUILE_LOAD_PATH.

        - Remove automake and autoconf from your path, or turn off
          their execute bits, or something.  (Users must be able to
          build from the tarfile without installing those tools.)  As
          an example, you could disable the tools during the test like
          so:

            mkdir /tmp/stub
            cat > /tmp/stub/do-nothing <<EOF
            #!/bin/sh
            echo warning: $0 called
            sleep 10
            exit 0
            EOF
            chmod +x /tmp/stub/do-nothing
            ln /tmp/stub/do-nothing /tmp/stub/automake
            ln /tmp/stub/do-nothing /tmp/stub/autoconf	# etc
            PATH=/tmp/stub:$PATH

        - Configure, "make", "make check", and "make install".  Make
          sure to remove your previous install tree before the "make
          install".

        - Make sure LD_LIBRARY_PATH doesn't include anything
          unnecessary -- though at the moment it (or
          LTDL_LIBRARY_PATH) will need to include guile's lib
          directory if that directory is not already in the normal
          places libltdl looks.

        - Run the test suite on the installed version.
            ./check-guile -i [INSTALL_PATH]/bin/guile

        - Look at the install tree (with "find | sort" or similar) and
          make sure nothing seems obviously amiss.

        - Check that the dependencies in guile-readline/Makefile look
          OK.  (We currently use a kludge which edits the dependencies
          generated by automake so that Guile can be built in a
          directory separate from the source tree also with non-GNU
          make programs.)

        - Make sure readline works.

        - You might try the example code in the doc directory.

Thanks

-- 
Rob Browning
rlb @defaultvalue.org, @linuxdevel.com, and @debian.org
Previously @cs.utexas.edu
GPG=1C58 8B2C FB5E 3F64 EA5C  64AE 78FE E5FE F0CB A0AD


_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel


             reply	other threads:[~2002-08-20 18:20 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-08-20 18:20 Rob Browning [this message]
2002-08-20 18:38 ` Guile 1.5.7 beta available for testing Rob Browning
2002-08-20 19:16   ` Marius Vollmer
     [not found]   ` <87wuqluyrj.fsf@zagadka.ping.de>
2002-08-20 19:54     ` Rob Browning
2002-08-20 20:33 ` Han-Wen Nienhuys
2002-08-20 20:50   ` Rob Browning
2002-08-22 11:56 ` Martin Grabmueller
2002-08-26 18:16   ` Dale P. Smith
2002-08-26 21:47   ` Marius Vollmer
2002-08-26 21:52   ` Marius Vollmer
     [not found]   ` <87bs7p70fo.fsf@zagadka.ping.de>
2002-08-29  9:24     ` Martin Grabmueller
2002-08-29 16:24       ` Rob Browning
2002-08-30  9:09         ` Martin Grabmueller
     [not found]         ` <200208300909.g7U99IG10890@pepita.cs.tu-berlin.de>
2002-08-30 13:17           ` tomas
2002-08-22 20:21 ` 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=87n0rh2xz8.fsf@raven.i.defaultvalue.org \
    --to=rlb@defaultvalue.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).