Linux PARISC architecture development
 help / color / mirror / Atom feed
From: dann frazier <dannf@dannf.org>
To: Carlos O'Donell <carlos@systemhalted.org>
Cc: Debian HPPA Port List <debian-hppa@lists.debian.org>,
	linux-parisc <linux-parisc@vger.kernel.org>
Subject: Re: NTPL transition
Date: Thu, 4 Sep 2008 11:49:00 -0600	[thread overview]
Message-ID: <20080904174859.GA19630@colo.lackof.org> (raw)
In-Reply-To: <119aab440809041029v6d7592bau15a2307099e5f02e@mail.gmail.com>

On Thu, Sep 04, 2008 at 01:29:06PM -0400, Carlos O'Donell wrote:
> On Thu, Sep 4, 2008 at 12:04 PM, dann frazier <dannf@dannf.org> wrote:
> > If we continue to use libc6 as the package name as we're currently
> > doing, at some point libc will get upgraded to the NPTL interface and
> > things will start crashing immediately. I asked if we could just do
> > "whatever x86 did", and kyle said that we have a problem they didn't -
> > our data nptl/lt data structures are incompatible.
> >
> > We can deal with that to an extent by adding a second libc package,
> > e.g., libc6.1. But, jejb pointed out that, since most libs depend on
> > libc, we'll need to be able to have libs for both interfaces at the
> > same time to support a transitional upgrade - and that implies an
> > SONAME bump for every C library.
> >
> > Hopefully there's an easier way, but I don't know of one.
> 
> How far away is queeze?

There's no set timeframe - but I think we can easily assume it will
be at least 1 year after lenny, which is frozen for release now.

> I have to go write some, code, and test some changes, and get back to
> the list with some options.
> 
> Namely:
> 
> Is it possible to change the pthread structures such that writing the
> compatibility code is easy?
> - Leave padding where the old lock words were and detect statically
> initialized locks by looking at these words?
> - Does this break Gentoo? I think they just emerge world.
> - Does this break Ubuntu hppa? Probably.

thanks Carlos

-- 
dann frazier


  reply	other threads:[~2008-09-04 17:49 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20080904114551.GA18877@tilt.dandreoli.com>
2008-09-04 14:13 ` NTPL transition Carlos O'Donell
2008-09-04 15:23   ` dann frazier
2008-09-04 15:31     ` Carlos O'Donell
2008-09-04 16:04       ` dann frazier
2008-09-04 17:29         ` Carlos O'Donell
2008-09-04 17:49           ` dann frazier [this message]
2008-09-04 17:52         ` James Bottomley
2008-09-04 23:26           ` Domenico Andreoli
2008-09-05 12:17           ` Carlos O'Donell
2008-09-05 14:07             ` James Bottomley
2008-09-05 14:20               ` Kyle McMartin
2008-09-05 14:58                 ` Carlos O'Donell
2008-09-04 23:22         ` Domenico Andreoli
2008-09-06  8:24 Petr Salinger
2008-09-06 15:31 ` Carlos O'Donell
2008-09-06 20:16   ` Petr Salinger
2008-09-06 21:36     ` Carlos O'Donell
2008-10-24  5:45 ` Carlos O'Donell

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20080904174859.GA19630@colo.lackof.org \
    --to=dannf@dannf.org \
    --cc=carlos@systemhalted.org \
    --cc=debian-hppa@lists.debian.org \
    --cc=linux-parisc@vger.kernel.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