public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: "Billinghurst, David \(CRTS\)" <David.Billinghurst@riotinto.com>
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: Fri, 01 Mar 2002 22:46:00 -0000	[thread overview]
Message-ID: <20020302064602.13761.qmail@sources.redhat.com> (raw)

The following reply was made to PR libgcj/5789; it has been noted by GNATS.

From: "Billinghurst, David (CRTS)" <David.Billinghurst@riotinto.com>
To: <java@gcc.gnu.org>
Cc: <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: Sat, 2 Mar 2002 09:53:54 +0800

 Version:  3.1 and 3.2
 System: mips-sgi-irix6.5
 
 The problem
 
 Error compiling boehm-gc/mips_sgi_mach_dep.S
 
 as: Error: /usr/include/sys/regdef.h, line 17: Expected cpp-generated =
 line number
 as INTERNAL ERROR:  /usr/lib32/cmplrs/asm returned non-zero status 1
 
 
 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.  If the lines are removed from the .s
 file it can be assembled.
 
 The irix cpp removes #ident lines.
 
 
 Work around
 
 Renaming the file to .s works in this case, as irix assembler=20
 runs the irix cpp on the file by default.  This was the case for=20
 gcc-3.0.
 
 
 Proper fix
 
 Don't know.  Perhaps:
   - get gcc cpp to remove #ident lines
   - fix headers


             reply	other threads:[~2002-03-02  6:46 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-03-01 22:46 Billinghurst, David (CRTS) [this message]
2002-03-03 23:46 Bryce McKinlay
2002-03-04  8:36 Zack Weinberg
2002-03-04 12:26 Neil Booth
2002-03-04 15:16 Billinghurst, David (CRTS)
2002-03-04 15:36 Zack Weinberg

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=20020302064602.13761.qmail@sources.redhat.com \
    --to=david.billinghurst@riotinto.com \
    --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: 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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).