public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Bryce McKinlay <bryce@waitaki.otago.ac.nz> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: libgcj/5789: boehm-gc won't build on irix - irix assembler chokes on #indent Date: Sun, 03 Mar 2002 23:46:00 -0000 [thread overview] Message-ID: <20020304074602.30553.qmail@sources.redhat.com> (raw) The following reply was made to PR libgcj/5789; it has been noted by GNATS. From: Bryce McKinlay <bryce@waitaki.otago.ac.nz> To: "Billinghurst, David (CRTS)" <David.Billinghurst@riotinto.com> Cc: java@gcc.gnu.org, hans_boehm@hp.com, gcc-gnats@gcc.gnu.org, gcc-bugs@gcc.gnu.org Subject: Re: libgcj/5789: boehm-gc won't build on irix - irix assembler chokes on #indent Date: Mon, 04 Mar 2002 20:40:42 +1300 Billinghurst, David (CRTS) wrote: >Cause > >The Irix header files > /usr/include/sys/regdef.h > /usr/include/sgidefs.h > /usr/include/sys/asm.h >contain #ident "$Revision: 3.52 $" lines. > >The gcc cpp passess these through to the .s file, and the irix >assembler chokes on them. > >Proper fix > >Don't know. Perhaps: > - get gcc cpp to remove #ident lines > - fix headers > Best fix would be to write a fixincludes haxie to fix these headers. This probibly won't be hard, but it sounds like the path of least resistance will be to just rename it back to .s (since, afaik, there is no actual problem with having it called .s on irix, apart from the lack of consistency with the other files). regards Bryce.
next reply other threads:[~2002-03-04 7:46 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-03-03 23:46 Bryce McKinlay [this message] -- strict thread matches above, loose matches on Subject: below -- 2002-03-04 15:36 Zack Weinberg 2002-03-04 15:16 Billinghurst, David (CRTS) 2002-03-04 12:26 Neil Booth 2002-03-04 8:36 Zack Weinberg 2002-03-01 22:46 Billinghurst, David (CRTS)
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=20020304074602.30553.qmail@sources.redhat.com \ --to=bryce@waitaki.otago.ac.nz \ --cc=gcc-prs@gcc.gnu.org \ --cc=nobody@gcc.gnu.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: linkBe 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; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).