public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Joel Sherrill <joel.sherrill@OARcorp.com>
To: binutils@sourceware.cygnus.com
Subject: hppa1.1-rtems grepossible failure ?\x03
Date: Tue, 05 Oct 1999 09:32:00 -0000	[thread overview]
Message-ID: <37FA2EF7.1977EBE8@OARcorp.com> (raw)
In-Reply-To: <19991005013145.18030.qmail@daffy.airs.com>

I got this trying to compile:

gcc-2.95.1, newlib 1.8.2, and binutils 990901.  

touch stmp-headers
echo "void __foo () {}" > dummy.c
/usr1/rtems/work/tools/build-hppa1.1-tools/gcc/xgcc
-B/usr1/rtems/work/tools/build-hppa1.1-tools/gcc/
-B/usr2/tools_install/gcc-2.95.1-binutils-990901-newlib-1.8.2-1099/hppa1.1-rtems/hppa1.1-rtems/bin/
-I/usr2/tools_install/gcc-2.95.1-binutils-990901-newlib-1.8.2-1099/hppa1.1-rtems/hppa1.1-rtems/include
-DCROSS_COMPILE -DIN_GCC -DHAIFA    -O2 -g -I./include  -c dummy.c
/tmp/ccMjORtk.s: Assembler messages:
/tmp/ccMjORtk.s:2: Error: Unknown pseudo-op:  `.subspa'
/tmp/ccMjORtk.s:3: Error: Unknown pseudo-op:  `.subspa'
/tmp/ccMjORtk.s:5: Error: Unknown pseudo-op:  `.subspa'
/tmp/ccMjORtk.s:6: Error: Unknown pseudo-op:  `.subspa'
/tmp/ccMjORtk.s:14: Error: Unknown pseudo-op:  `.subspa'
/tmp/ccMjORtk.s:50: Error: Unknown pseudo-op:  `.subspa'

Any ideas?  In the RTEMS source, the hppa port uses .SUBSPA.

-- 
Joel Sherrill, Ph.D.             Director of Research & Development
joel@OARcorp.com                 On-Line Applications Research
Ask me about RTEMS: a free RTOS  Huntsville AL 35805
   Support Available             (256) 722-9985

  reply	other threads:[~1999-10-05  9:32 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-10-04 18:20 linker memory footprint J.T. Conklin
1999-10-04 18:32 ` Ian Lance Taylor
1999-10-05  9:32   ` Joel Sherrill [this message]
1999-10-06  7:30     ` hppa1.1-rtems grepossible failure ? Jeffrey A Law
1999-10-06  9:38       ` Joel Sherrill

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=37FA2EF7.1977EBE8@OARcorp.com \
    --to=joel.sherrill@oarcorp.com \
    --cc=binutils@sourceware.cygnus.com \
    /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).