Linux PARISC architecture development
 help / color / mirror / Atom feed
From: Randolph Chung <randolph@tausq.org>
To: "FARINATI,LEANDRO (HP-Brazil,ex1)" <leandro.farinati@hp.com>
Cc: parisc-linux@lists.parisc-linux.org
Subject: Re: [parisc-linux] pa-risc assembler
Date: Fri, 22 Nov 2002 08:14:55 -0800	[thread overview]
Message-ID: <20021122161455.GI21187@tausq.org> (raw)
In-Reply-To: <CB813811CBF6D3118DCC00902740BB4A0B8665D5@xsp01.brazil.hp.com>

> 	I would like to know about usage of .subspa, because I am converting
> some asm sourcecodes in hp-ux to linux.
> 	When iI will try to compile the source code with "cc --hppa-linux
> -std=iso9899:1990 -march=2.0 -mpa-risc-2-0 -D__KERNEL__ -I../../include -I.
> -c -o myfile.o myfile.s, the result is always" the same "Error: unknown
> pseudo-op: `.subspa'".
> 	Why this happens?

hppa-linux doesn't use the .subspa directive. depending on the
particular construct it will need to be translated into .text, .rodata,
.bss, etc...

HTH,
randolph
-- 
Randolph Chung
Debian GNU/Linux Developer, hppa/ia64 ports
http://www.tausq.org/

      reply	other threads:[~2002-11-22 16:12 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-22 12:11 [parisc-linux] pa-risc assembler FARINATI,LEANDRO (HP-Brazil,ex1)
2002-11-22 16:14 ` Randolph Chung [this message]

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=20021122161455.GI21187@tausq.org \
    --to=randolph@tausq.org \
    --cc=leandro.farinati@hp.com \
    --cc=parisc-linux@lists.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