From: Joel Soete <joel.soete@freebel.net>
To: John David Anglin <dave@hiauly1.hia.nrc.ca>
Cc: parisc-linux@parisc-linux.org
Subject: Re: [parisc-linux] gcc-cvs problem
Date: Sat, 01 Jun 2002 19:11:04 +0000 [thread overview]
Message-ID: <3CF91C48.5000008@freebel.net> (raw)
In-Reply-To: 200205311715.g4VHF4Pu006500@hiauly1.hia.nrc.ca
John David Anglin wrote:
>>It seems to be well comited in last cvs update this morming I got in
>>src/gcc/gcc/fixinc/inclhack.def:
>>...
>>/*
>> * __thread is now a keyword.
>> */
>
>
>>But do not seems to be applied as I got the same error?
>>
>>What do I wrong or forget to do?
>
>
> You should see the following in your build output:
>
> Applying thread_keyword to pthread.h
> Fixed: pthread.h
>
> A fixed pthread.h should appear in the {build}/gcc/include directory.
> This seems to work ok for me in a native hppa-linux build. However,
> it appears that you are trying to do a cross build.
AFAIK gcc bootstrap does not work for hppa?
> If the header
> is not being fixed, you will need to examine your build log carefully
> to determine why the fix isn't being done or doesn't work.
>
I will have a detailed look but as newbee in gcc stuff it will take a time.
Thank again for attention and help,
Joel
next prev parent reply other threads:[~2002-06-01 19:10 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-30 17:22 [parisc-linux] gcc-cvs problem joel.soete
2002-05-30 17:51 ` John David Anglin
2002-05-31 15:14 ` joel.soete
2002-05-31 17:15 ` John David Anglin
2002-06-01 19:11 ` Joel Soete [this message]
2002-06-02 0:45 ` John David Anglin
2002-06-03 15:47 ` joel.soete
2002-06-03 14:58 ` joel.soete
2002-06-03 15:12 ` John David Anglin
2002-06-03 17:09 ` joel.soete
2002-06-03 17:38 ` John David Anglin
2002-06-04 6:32 ` joel.soete
2002-06-04 16:52 ` joel.soete
2002-06-05 16:11 ` joel.soete
2002-06-05 17:17 ` joel.soete
2002-06-05 17:34 ` John David Anglin
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=3CF91C48.5000008@freebel.net \
--to=joel.soete@freebel.net \
--cc=dave@hiauly1.hia.nrc.ca \
--cc=parisc-linux@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