unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Rob Browning <rlb@defaultvalue.org>
To: Neil Jerram <neil@ossau.homelinux.net>
Cc: Andy Wingo <wingo@pobox.com>, guile-devel@gnu.org
Subject: Re: Thread+GC issues on ARM
Date: Sat, 11 Feb 2012 11:38:59 -0600	[thread overview]
Message-ID: <87ipjdclsc.fsf@trouble.defaultvalue.org> (raw)
In-Reply-To: <878vk9669u.fsf@neil-laptop.ossau.uklinux.net> (Neil Jerram's message of "Sat, 11 Feb 2012 09:58:21 +0000")

Neil Jerram <neil@ossau.homelinux.net> writes:

> First of all, thanks for pushing 2.0.5 into Debian so quickly!

After a decent bit of work last year, I integrated my Debian development
directly into the Guile git tree (including much of the older history).
That, the fact that I don't have to split 2.0, and git-dpm/git-dch have
made things like shifting to a new version *much* easier.

> Out of interest, what are your criteria for dropping 1.8?

I want guile-2.0 to build (and pass make check) on all of the
architectures that guile-1.8 does:

  https://buildd.debian.org/status/package.php?p=guile-1.8&suite=sid

And I want all of the (relevant) packages that depend on Guile to work
with guile-2.0.

I think we're pretty close now.  Most of the remaining arch problems
(aside from arm) may be GC/timing related test failures, and I'm
planning to just mark those UNRESOLVED.

> Is / should there be any consideration for continuing to provide
> guile-1.8 as a legacy programming environment?  Personally I'd feel
> comfortable if the answer to that was "no" - because I think it's
> positive overall to concentrate everyone's mindshare on the present
> and future, and because I'm not aware of any significant support
> having been lost - but just wondering.

My impression is that we wouldn't be losing much by dropping 2.0, but
feel free to correct me.  The thing that makes me more inclined to drop
1.8 is a Debian specific issue -- guile-1.8 has never (and will never)
have thread support, and that seems like a fairly significant
limitation.

> I don't know.  Would you like me to provide you with my current libgc
> and guile changes, which give a successful build on armel, so that you
> can see if they work on armhf too?

Given your next message, I think I might just wait for a fixed Debian
libgc.  We can't really proceed without that anyway.

Thanks
-- 
Rob Browning
rlb @defaultvalue.org and @debian.org
GPG as of 2002-11-03 14DD 432F AE39 534D B592 F9A0 25C8 D377 8C7E 73A4



  parent reply	other threads:[~2012-02-11 17:38 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-24 12:50 Thread+GC issues on ARM Neil Jerram
2012-01-07  1:39 ` Andy Wingo
2012-01-07  3:32   ` Rob Browning
2012-01-07 12:01     ` Neil Jerram
2012-01-07 12:35       ` Neil Jerram
2012-01-07 17:52         ` Rob Browning
2012-01-08 10:28           ` Neil Jerram
2012-02-11  3:39             ` Rob Browning
2012-02-11  9:58               ` Neil Jerram
2012-02-11 13:10                 ` Neil Jerram
2012-02-11 17:39                   ` Rob Browning
2012-02-13 22:22                     ` Neil Jerram
2012-02-11 17:38                 ` Rob Browning [this message]
2013-01-16 10:28               ` Andy Wingo
2012-01-07 16:48       ` Rob Browning

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=87ipjdclsc.fsf@trouble.defaultvalue.org \
    --to=rlb@defaultvalue.org \
    --cc=guile-devel@gnu.org \
    --cc=neil@ossau.homelinux.net \
    --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).