From: <dsmich@roadrunner.com>
To: Neil Jerram <neiljerram@googlemail.com>
Cc: bug-guile@gnu.org, Kannan Vijayan <INVALID.NOREPLY@gnu.org>,
Kannan Vijayan <kannan.vij@gmail.com>
Subject: Re: [bug #24554] Pthreads and Stack overflow in guile (reopen bug 20814?) (guile 1.8.5)
Date: Wed, 15 Oct 2008 14:43:27 -0400 [thread overview]
Message-ID: <19657238.1231071224096207567.JavaMail.root@cdptpa-web28-z01> (raw)
---- Neil Jerram <neiljerram@googlemail.com> wrote:
> 2008/10/14 <dsmich@roadrunner.com>:
> >
> > I would imagine that --with-threads will not be turned back on until a 1.10.x (or 2.0.0 ?) release of Guile.
> >
> > My limited understanding of the situation (possibly incorrect): Using --without-threads changes the sizes of some data structures (I'm guessing they are smaller, with some pthreads stuff #ifdef'ed out), so that code compiled for one way will segfault when linked with code compiled for the other way.
> >
> > As far as just releasing new packages --with-threads, It's just not possible to go back an recompile all the currently existing packages on already existing systems.
>
> Really? Isn't that what happens normally in "transitions"? There are
> only 28 packages depending (directly) on guile-1.8-libs.
>
> Or is the issue about non-Debian applications that people have built
> themselves? Does Debian policy require a package's ABI always to stay
> back-compatible?
It's not about non-debian applications. It's about preserving ABI compatability. Here is more information: http://www.netfort.gr.jp/~dancer/column/libpkg-guide/libpkg-guide.html#sonameapiabi
In any case, Rob Browning is the one who knows what can (and can't) be done.
> (Another option would be creating new packages with --with-threads
> support. The current guile 1.8 packages are named guile-1.8 and
> guile-1.8-libs, and it must be the case that everything currently in
> Debian that depends on these does _not_ require support for multiple
> threads. It should be possible to create packages with new names,
> e.g. guile-1.8-mt and guile-1.8-mt-libs, that were built
> --with-threads, and these would initially have no packages depending
> on them.
>
> The problem with that, though, is that the existing and -mt packages
> could not coexist, so a Debian user would have to choose between the
> existing packages (+ the option of everything that depends on them)
> and the -mt packages.)
Yes. It's gets complicated quickly.
-Dale
next reply other threads:[~2008-10-15 18:43 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-15 18:43 dsmich [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-10-14 16:50 [bug #24554] Pthreads and Stack overflow in guile (reopen bug 20814?) (guile 1.8.5) dsmich
2008-10-14 21:48 ` Neil Jerram
2008-10-14 1:39 Kannan Vijayan
2008-10-14 3:05 ` Kannan Vijayan
2008-10-14 8:53 ` Neil Jerram
2008-10-14 15:07 ` Kannan Vijayan
2008-11-30 18:42 ` Ludovic Courtès
2009-07-20 21:51 ` Ludovic Courtès
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=19657238.1231071224096207567.JavaMail.root@cdptpa-web28-z01 \
--to=dsmich@roadrunner.com \
--cc=INVALID.NOREPLY@gnu.org \
--cc=bug-guile@gnu.org \
--cc=kannan.vij@gmail.com \
--cc=neiljerram@googlemail.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).