All of lore.kernel.org
 help / color / mirror / Atom feed
From: Joel Soete <soete.joel@tiscali.be>
To: Randolph Chung <randolph@tausq.org>
Cc: Joel Soete <soete.joel@scarlet.be>,
	parisc-linux <parisc-linux@lists.parisc-linux.org>
Subject: Re: [parisc-linux] HPPA NPTL Support committed to libc-ports,help needed!
Date: Sat, 15 Jul 2006 13:32:32 +0000	[thread overview]
Message-ID: <44B8EE70.8080602@tiscali.be> (raw)
In-Reply-To: <44B8441A.4030200@tausq.org>

Hello parisc-linux,

Randolph Chung wrote:
>>>gcc cvs head newer than 2005-07-05 with TLS turned on.
>>
>>Just to be sure: is it well 2005?
>>if yes latest gcc-4.1 would be good enough (if rebuild with previous binutils)?
> 
> 
> July 2005 sounds correct. Yes, it has been merged for some time. Make
> sure you build gcc with the correct binutils, and that gcc is configured
> to enable TLS.

I have check to <http://buildd.debian.org/build.php?arch=hppa&pkg=gcc-4.1>

and afaik debian gcc-4.1 release >= 4.1.1-6 should be ok
(iirc no gcc configure option to build it with tls support but a check if used binutils supports it)

[snip]
bzip2: missing
binutils: already installed (2.17-1 >= 2.16.1cvs20051214 is satisfied)
binutils-hppa64: missing
[snip]

(still need to check if this pb:
<http://lists.parisc-linux.org/pipermail/parisc-linux/2006-May/029185.html>
is not any more in 4.1.1, i will advise?)

> See the build script Carlos referenced for appropriate
> configure parameters.
> 
> randolph
Many thanks,
	Joel
_______________________________________________
parisc-linux mailing list
parisc-linux@lists.parisc-linux.org
http://lists.parisc-linux.org/mailman/listinfo/parisc-linux

       reply	other threads:[~2006-07-15 13:32 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <J2EH4I$3077C4C25049A3D92E390FB82AA610CA@scarlet.be>
     [not found] ` <44B8441A.4030200@tausq.org>
2006-07-15 13:32   ` Joel Soete [this message]
2006-07-14 14:56 [parisc-linux] HPPA NPTL Support committed to libc-ports, help needed! Carlos O'Donell
2006-07-15 13:49 ` Randolph Chung

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=44B8EE70.8080602@tiscali.be \
    --to=soete.joel@tiscali.be \
    --cc=parisc-linux@lists.parisc-linux.org \
    --cc=randolph@tausq.org \
    --cc=soete.joel@scarlet.be \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.