From: Rob Browning <rlb@defaultvalue.org>
Cc: jantien@xs4all.nl, guile-devel@gnu.org
Subject: Re: any news on 1.6 yet?
Date: Mon, 01 Jul 2002 16:40:12 -0500 [thread overview]
Message-ID: <87fzz3b003.fsf@raven.i.defaultvalue.org> (raw)
In-Reply-To: <15648.13489.975604.112162@meddo.cs.uu.nl> (Han-Wen Nienhuys's message of "Mon, 1 Jul 2002 12:53:37 +0200")
Han-Wen Nienhuys <hanwen@cs.uu.nl> writes:
> Sorry for pestering you again about the guile release, but I'm
> starting to get a little impatient. The mailing list has been quite
> dead for months, and it seems that development is being halted until
> the new stable release is out of the door.
Speaking for myself, that's true -- I'm not really working on HEAD
ATM, but I do have a number of things that should go into HEAD once
I'm ready -- i.e a month or two ago I got GMP working for bignums. If
we can decide how to handle the licensing, those changes can go in.
In any case, now that various issues in my real-life have settled
down. I'm now starting back up work on the release, FWIW. I'd like
to give you a schedule, but I can't yet. However, I should have a new
status update posted in less than a week.
> Also, my friend Jan submitted a patch for building GUILE crosscompiled
> to a cygwin target,
>
> http://mail.gnu.org/pipermail/guile-devel/2002-February/004562.html
>
> which was met with
>
>>Thanks very much. I'd like to wait until the people more familiar
>>with this particular issue can check the patch out before we apply it.
>>So this fix may not make it into 1.5.7, but presuming everything's
>>fine, it should make it into 1.5.8.
>
> I'm under the distinct impression that "the people more familiar" are
> more busy with putting various air castles into workbook files instead
> of evaluating and writing code.
I will look back at this patch. I'd also like to hear if Marius (or
anyone else) has any comments.
> Can someone puleaze put in the following remark into the GUILE
> documentation?
>
>
> Be warned that the thread library (pthreads) will impose a 512k
> limit on the stack size, when compiling GUILE with thread
> support.
>
> We spent a _long_ time being flabbergasted at why our program dumped
> core on perfectly valid data and innocent instructions.
Wow, that's annoying -- do you know if this is an arch dependency, OS
dependency, etc?
--
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
next prev parent reply other threads:[~2002-07-01 21:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-01 10:53 any news on 1.6 yet? Han-Wen Nienhuys
2002-07-01 21:40 ` Rob Browning [this message]
2002-07-02 0:10 ` Han-Wen
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=87fzz3b003.fsf@raven.i.defaultvalue.org \
--to=rlb@defaultvalue.org \
--cc=guile-devel@gnu.org \
--cc=jantien@xs4all.nl \
/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).