> Correct. It's a parameter name in two or so function prototypes in
> pthread.h in woody's glibc. Fixincludes fixes this, but Debian doesn't
> package the fixed includes (wisely).
Excellent, that took care of it. It would appear my backports are working
now. Thanks!
Later,
Dale
--
D
On Sat, Apr 24, 2004 at 05:16:14PM -0400, Dale E Martin wrote:
> > You could fix the header - it's just that one place that uses the
> > reserved __thread keyword.
>
> So the problem is that __thread is (now?) a keyword but it's been used as
> an identifier? I didn't realize that was the issue if
> You could fix the header - it's just that one place that uses the
> reserved __thread keyword.
So the problem is that __thread is (now?) a keyword but it's been used as
an identifier? I didn't realize that was the issue if that's it.
Thanks!
Dale
--
Dale E. Martin, Clifton Labs, Inc.
On Fri, Apr 23, 2004 at 10:55:21AM -0400, Dale E Martin wrote:
> (I'm not subscribed to this list, please Cc me.)
>
> I managed to get the experimental gcc/g++ 3.4 packages to build on a
> woody+backports box. Now when I go to compile "hello world" with g++-3.4,
> I get this error:
> ~> cd test/c
(I'm not subscribed to this list, please Cc me.)
I managed to get the experimental gcc/g++ 3.4 packages to build on a
woody+backports box. Now when I go to compile "hello world" with g++-3.4,
I get this error:
~> cd test/c++/
~/test/c++> g++-3.4 hello.cc
In file included from
/usr/include/c++/3.4
5 matches
Mail list logo
