From: Jeff Bailey <jbailey@raspberryginger.com>
To: "Carlos O'Donell" <carlos@systemhalted.org>
Cc: parisc-linux <parisc-linux@lists.parisc-linux.org>
Subject: [parisc-linux] Re: NPTL fixes.
Date: Sat, 22 Jul 2006 11:54:23 -0700 [thread overview]
Message-ID: <20060722185423.GA30156@titanium.v3.ca> (raw)
In-Reply-To: <119aab440607221000w687c2d8v9afa5fb7d7bdd12b@mail.gmail.com>
(restoring cc:'s dropped by accident)
On Sat, Jul 22, 2006 at 01:00:58PM -0400, Carlos O'Donell wrote:
> On 7/22/06, Carlos O'Donell <carlos@systemhalted.org> wrote:
> >> If yes, I'll make it a priority next week so that I can get some initial
> >> bootstrapping stuff done.
> >
> >It's not high-prio, I don't care about the ABI break, I care primarily
> >about reducing the number of failures. After the failures are reduced
> >we *might* be able to tackle ABI compatibility... but again I doubt
> >this, since it would require similar patches to Linuxthreads which
> >were rejected before and will be rejected again. Not to mention it
> >causes weird headaches with all the other arches that put
> >uninitialized locks in .bss.
>
> Is an alternative that we bump the .so number in the thread library?
Yes an no. That solves the problem from an upstream perspective, but it
will make upgrading to NPTL for current parisc users hard. The problem
is that we don't version libpthreads itself, we only version libc6. The
packaging system doesn't then provide any hints that the version of
libpthreads that the packages are looking for doesn't exist anymore.
If you're going to bump the version number of pthreads, I'd recommend
taking this time to do a break on glibc as well and get any changes done
that you might need to.
Tks,
Jeff Bailey
--
I do not agree with a word you say, but I will defend to the death your
right to say it.
- Voltaire
_______________________________________________
parisc-linux mailing list
parisc-linux@lists.parisc-linux.org
http://lists.parisc-linux.org/mailman/listinfo/parisc-linux
prev parent reply other threads:[~2006-07-22 18:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-18 22:47 [parisc-linux] NPTL fixes Carlos O'Donell
[not found] ` <20060720221634.GA25514@titanium.v3.ca>
[not found] ` <119aab440607210834u7761a7e2w54e3990fedaa995c@mail.gmail.com>
[not found] ` <20060721155009.GA18291@titanium.v3.ca>
[not found] ` <119aab440607221000w6cf467c2k8d16edf20e7791c4@mail.gmail.com>
[not found] ` <119aab440607221000w687c2d8v9afa5fb7d7bdd12b@mail.gmail.com>
2006-07-22 18:54 ` Jeff Bailey [this message]
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=20060722185423.GA30156@titanium.v3.ca \
--to=jbailey@raspberryginger.com \
--cc=carlos@systemhalted.org \
--cc=parisc-linux@lists.parisc-linux.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