* Guile 1.7.91 has been released.
@ 2006-02-12 23:15 Marius Vollmer
2006-02-13 8:37 ` Han-Wen Nienhuys
2006-02-14 11:35 ` Han-Wen Nienhuys
0 siblings, 2 replies; 5+ messages in thread
From: Marius Vollmer @ 2006-02-12 23:15 UTC (permalink / raw)
We are pleased to announce the release of Guile 1.7.91. This is a
release candidate for Guile 1.8. It can be found here:
ftp://alpha.gnu.org/gnu/guile/guile-1.7.91.tar.gz
Its MD5 checksum is
b2106c1b574e22ec67c4c2178074b5ec guile-1.7.91.tar.gz
The plan is to release version 1.8.0 next weekend, 2006-01-19, if all
goes well.
The NEWS file is quite long. Here are the most interesting entries:
Changes since 1.6:
* Guile is now licensed with the GNU Lesser General Public License.
* The manual is now licensed with the GNU Free Documentation License.
* We now use GNU MP for bignums.
* We now have exact rationals, such as 1/3.
* We now use native POSIX threads for real concurrent threads.
* There is a new way to initalize Guile that allows one to use Guile
from threads that have not been created by Guile.
* Mutexes and condition variables are now always fair. A recursive
mutex must be requested explicitely.
* The low-level thread API has been removed.
* There is now support for copy-on-write substrings and
mutation-sharing substrings.
* A new family of functions for converting between C values and
Scheme values has been added that is future-proof and thread-safe.
* The INUM macros like SCM_MAKINUM have been deprecated.
* The macros SCM_STRINGP, SCM_STRING_CHARS, SCM_STRING_LENGTH,
SCM_SYMBOL_CHARS, and SCM_SYMBOL_LENGTH have been deprecated.
* There is a new way to deal with non-local exits and re-entries in
C code, which is nicer than scm_internal_dynamic_wind.
* There are new malloc-like functions that work better than
scm_must_malloc, etc.
* There is a new way to access all kinds of vectors and arrays from
C that is efficient and thread-safe.
* The concept of dynamic roots has been factored into continuation
barriers and dynamic states.
See NEWS and the manual for more details.
--
GPG: D5D4E405 - 2F9B BCCC 8527 692A 04E3 331E FAF8 226A D5D4 E405
_______________________________________________
Guile-user mailing list
Guile-user@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-user
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: Guile 1.7.91 has been released.
2006-02-12 23:15 Guile 1.7.91 has been released Marius Vollmer
@ 2006-02-13 8:37 ` Han-Wen Nienhuys
2006-02-13 21:48 ` Kevin Ryde
2006-02-14 11:35 ` Han-Wen Nienhuys
1 sibling, 1 reply; 5+ messages in thread
From: Han-Wen Nienhuys @ 2006-02-13 8:37 UTC (permalink / raw)
Cc: guile-devel
In article <87y80gyxrq.fsf@zagadka.de>, Marius Vollmer <mvo@zagadka.de> wrote:
>We are pleased to announce the release of Guile 1.7.91. This is a
>release candidate for Guile 1.8. It can be found here:
cross-compiling from Linux/x86 to Mingw/x86:
Making all in libguile
make[2]: Entering directory `/home/hanwen/vc/gub/target/mingw/build/guile-1.7.91/libguile'
make[2]: *** Geen regel voor aanmaken doel `fileblocks.x', nodig voor `all'. Stop.
make[2]: Leaving directory `/home/hanwen/vc/gub/target/mingw/build/guile-1.7.91/libguile'
make[1]: *** [all-recursive] Fout 1
make[1]: Leaving directory `/home/hanwen/vc/gub/target/mingw/build/guile-1.7.91'm
there is no fileblocks.* anywhere. Configure mentions
## Remove fileblocks.o from the object list. This file gets added by
## the Autoconf macro AC_STRUCT_ST_BLOCKS. But there is no need.
#LIBOBJS="`echo ${LIBOBJS} | sed 's/fileblocks\.o//g'`"
I got this when configuring with
/home/hanwen/vc/gub/target/mingw/src/guile-1.7.91/configure
--config-cache --enable-shared --disable-static
--build=i386-redhat-linux --host=i686-mingw32 --target=i686-mingw32
--prefix=/usr --sysconfdir=/usr/etc --includedir=/usr/include
--libdir=/usr/lib --without-threads --with-gnu-ld --enable-deprecated
--enable-discouraged --disable-error-on-warning --enable-relocation
--disable-rpath PATH_SEPARATOR=;
LDFLAGS=-L/home/hanwen/vc/gub/target/mingw/system/usr/lib
CC_FOR_BUILD= C_INCLUDE_PATH= CPPFLAGS= LIBRARY_PATH= LDFLAGS= cc
-I/home/hanwen/vc/gub/target/mingw/build/guile-1.7.91
-I/home/hanwen/vc/gub/target/mingw/src/guile-1.7.91
-I/home/hanwen/vc/gub/target/mingw/build/guile-1.7.91/libguile
-I. -I/home/hanwen/vc/gub/target/mingw/src/guile-1.7.91/libguile
_______________________________________________
Guile-user mailing list
Guile-user@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-user
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: Guile 1.7.91 has been released.
2006-02-13 8:37 ` Han-Wen Nienhuys
@ 2006-02-13 21:48 ` Kevin Ryde
0 siblings, 0 replies; 5+ messages in thread
From: Kevin Ryde @ 2006-02-13 21:48 UTC (permalink / raw)
Cc: guile-user
hanwen@byrd.xs4all.nl (Han-Wen Nienhuys) writes:
>
> ## Remove fileblocks.o from the object list. This file gets added by
> ## the Autoconf macro AC_STRUCT_ST_BLOCKS. But there is no need.
> #LIBOBJS="`echo ${LIBOBJS} | sed 's/fileblocks\.o//g'`"
Actually, the bit preceding that seems relevant,
## NOTE the code below sets LIBOBJS directly and so is now forbidden
## -- I'm disabling it for now in the hopes that the newer autoconf
## will DTRT -- if not, we need to fix up the sed command to match the
## others...
I guess AC_STRUCT_ST_BLOCKS should be changed to
AC_CHECK_MEMBERS([struct stat.st_blocks])
if we only want the field test, not the libobj.
_______________________________________________
Guile-user mailing list
Guile-user@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-user
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: Guile 1.7.91 has been released.
2006-02-12 23:15 Guile 1.7.91 has been released Marius Vollmer
2006-02-13 8:37 ` Han-Wen Nienhuys
@ 2006-02-14 11:35 ` Han-Wen Nienhuys
2006-02-14 21:32 ` Marius Vollmer
1 sibling, 1 reply; 5+ messages in thread
From: Han-Wen Nienhuys @ 2006-02-14 11:35 UTC (permalink / raw)
Cc: guile-devel
In article <87y80gyxrq.fsf@zagadka.de>, Marius Vollmer <mvo@zagadka.de> wrote:
>We are pleased to announce the release of Guile 1.7.91. This is a
>release candidate for Guile 1.8. It can be found here:
>
> ftp://alpha.gnu.org/gnu/guile/guile-1.7.91.tar.gz
>
>Its MD5 checksum is
>
> b2106c1b574e22ec67c4c2178074b5ec guile-1.7.91.tar.gz
Hi Marius,
what is your plan for maintaining the branches? I've just put Ludovic's
scm_t_sweep_statistics patch in HEAD, can I also put it 1.8?
_______________________________________________
Guile-user mailing list
Guile-user@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-user
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: Guile 1.7.91 has been released.
2006-02-14 11:35 ` Han-Wen Nienhuys
@ 2006-02-14 21:32 ` Marius Vollmer
0 siblings, 0 replies; 5+ messages in thread
From: Marius Vollmer @ 2006-02-14 21:32 UTC (permalink / raw)
Cc: guile-user, guile-devel
hanwen@byrd.xs4all.nl (Han-Wen Nienhuys) writes:
> what is your plan for maintaining the branches?
The release-1-6 branch remains stable of course, and the release-1-8
branch will be stable after 1.8.0 has been released, and is now in
feature freeze. "Stable" should mean "we try very hard to not
regress and to remain binary compatible".
> I've just put Ludovic's scm_t_sweep_statistics patch in HEAD, can I
> also put it 1.8?
No. :-) I will look at it more closely, tho. Maybe it makes sense to
put it into 1.8.1.
--
GPG: D5D4E405 - 2F9B BCCC 8527 692A 04E3 331E FAF8 226A D5D4 E405
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-devel
^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2006-02-14 21:32 UTC | newest]
Thread overview: 5+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2006-02-12 23:15 Guile 1.7.91 has been released Marius Vollmer
2006-02-13 8:37 ` Han-Wen Nienhuys
2006-02-13 21:48 ` Kevin Ryde
2006-02-14 11:35 ` Han-Wen Nienhuys
2006-02-14 21:32 ` Marius Vollmer
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).