From: Mike Frysinger <vapier@gentoo.org>
To: parisc-linux@lists.parisc-linux.org
Cc: John David Anglin <dave@hiauly1.hia.nrc.ca>, dave.anglin@nrc.ca
Subject: Re: [parisc-linux] Re: 64-bit long double support.
Date: Thu, 16 Nov 2006 23:59:03 -0500 [thread overview]
Message-ID: <200611162359.05014.vapier@gentoo.org> (raw)
In-Reply-To: <200611162316.26872.vapier@gentoo.org>
[-- Attachment #1.1: Type: text/plain, Size: 1056 bytes --]
On Thursday 16 November 2006 23:16, Mike Frysinger wrote:
> ok, just tried glibc-2.5 + hppa + linuxthreads and that is for sure broken
> (the defines for handling locking is all broken in the release)
yeah glibc-2.5 fails as well:
... -o /var/tmp/portage/cross-hppa2.0-unknown-linux-gnu/glibc-2.5
/work/build-default-hppa2.0-unknown-linux-gnu-nptl/csu/crtn.o
In file included from ../nptl/descr.h:30,
from ../ports/sysdeps/hppa/nptl/tls.h:63,
from ../include/tls.h:6,
from <stdin>:2:
../ports/sysdeps/unix/sysv/linux/hppa/nptl/lowlevellock.h: In
function '__lll_mutex_trylock':
../ports/sysdeps/unix/sysv/linux/hppa/nptl/lowlevellock.h:113: error:
expected ':' or ')' before '-' token
...
i leave adding snap updates to GMsoft ... i try to stick with releases since i
have to help so many arches :/
> what is the minimal binutils/gcc versions for TLS support ? binutils-2.17
> + gcc-4.1.1 == no hppa TLS
upgraded to binutils-2.17.50.0.6 and i got TLS with gcc-4.1.1
-mike
[-- Attachment #1.2: Type: application/pgp-signature, Size: 827 bytes --]
[-- Attachment #2: Type: text/plain, Size: 169 bytes --]
_______________________________________________
parisc-linux mailing list
parisc-linux@lists.parisc-linux.org
http://lists.parisc-linux.org/mailman/listinfo/parisc-linux
next prev parent reply other threads:[~2006-11-17 4:59 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <119aab440611161731p47779d1hdc7e7dbd336eb23c@mail.gmail.com>
2006-11-17 1:48 ` [parisc-linux] Re: 64-bit long double support John David Anglin
[not found] ` <200611170148.kAH1moG4028180@hiauly1.hia.nrc.ca>
2006-11-17 3:48 ` Carlos O'Donell
2006-11-17 4:10 ` Mike Frysinger
2006-11-17 4:16 ` Mike Frysinger
2006-11-17 4:59 ` Mike Frysinger [this message]
2006-11-17 19:16 ` Jeff Bailey
2006-11-17 5:35 ` John David Anglin
2006-11-17 6:29 ` Mike Frysinger
2006-11-17 16:48 ` John David Anglin
[not found] ` <200611171502.49875.vapier@gentoo.org>
2006-11-17 20:51 ` [parisc-linux] gcc ICE PR29114 (was: 64-bit long double support.) John David Anglin
2006-11-17 21:12 ` Mike Frysinger
2006-11-17 21:16 ` Mike Frysinger
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=200611162359.05014.vapier@gentoo.org \
--to=vapier@gentoo.org \
--cc=dave.anglin@nrc.ca \
--cc=dave@hiauly1.hia.nrc.ca \
--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 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.