Linux PARISC architecture development
 help / color / mirror / Atom feed
From: Carlos O'Donell <carlos@systemhalted.org>
To: Randolph Chung <tausq@debian.org>,
	John David Anglin <dave.anglin@nrc-cnrc.gc.ca>
Cc: parisc-linux@lists.parisc-linux.org
Subject: [parisc-linux] Next steps? hppa tls toolchain and packaging in debian.
Date: Sun, 17 Jul 2005 12:31:40 -0400	[thread overview]
Message-ID: <20050717163140.GM5314@systemhalted.org> (raw)


Gentlemen,

We seem to have a working TLS implementation for hppa. What are some of
the next steps we want to take?

a. Submit a plabel 21/14, dir 21/14 patch to debian glibc.
   Submit the same patch to Ubuntu.

b. Submit TLS patch to binutils.

c. Submit OPD patch to binutils.
   - There may still be some issues about this patch with regards
     to the behvious of --export-dynamic.

d. Submit patches to upstream glibc for TLS
   - Linuxthread patches are being handled by drow.
   - Sysdep patches are handled by Roland/Ulrich.
   - Luckily no core changes required.

e. Work at futex implementation.
   - Mockup and test.

f. Work at NPTL implementation
   - Already started thanks to Randolph.

Any extra entries to add to the list?

How do we handle this:

1. Packages built with a newer toolchain can emit OPD's
2. These packages should require a newer glibc.

Can we make debian-binutils depend on a newer libc?
I still don't see how we can stop someone from isntalling a package that
has these relocs but not a new libc?

Cheers,
Carlos.

_______________________________________________
parisc-linux mailing list
parisc-linux@lists.parisc-linux.org
http://lists.parisc-linux.org/mailman/listinfo/parisc-linux

                 reply	other threads:[~2005-07-17 16:31 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20050717163140.GM5314@systemhalted.org \
    --to=carlos@systemhalted.org \
    --cc=dave.anglin@nrc-cnrc.gc.ca \
    --cc=parisc-linux@lists.parisc-linux.org \
    --cc=tausq@debian.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