From: n8tm@aol.comnojunk (Tim Prince)
To: help-gcc@gnu.org
Subject: Re: problem using gcc 2.8.1 on HP ( directive not recognized NSUBSPA )
Date: Thu, 07 Oct 1999 05:55:00 -0000 [thread overview]
Message-ID: <19991007085425.03791.00000028@ng-fb1.aol.com> (raw)
In-Reply-To: <37FC6863.B665A878@veritas.com>
> .NSUBSPA $CODE$,QUAD=0,ALIGN=8,ACCESS=44,CODE_ONLY
>
> and do
> # gcc test.s
>
> It works fine.
>
> Should I have to use gnu assembler to get rid of this problem ?
Yes, the porting site ought to have a compatible version of binutils. It is
possible also to construct the current binutils and gnu compilers using only
the basic hpux tools, and it's worth the effort, even if you don't use g++.
Tim Prince
tprince@computer.org
WARNING: multiple messages have this Message-ID
From: n8tm@aol.comnojunk (Tim Prince)
To: help-gcc@gnu.org
Subject: Re: problem using gcc 2.8.1 on HP ( directive not recognized NSUBSPA )
Date: Sun, 31 Oct 1999 13:57:00 -0000 [thread overview]
Message-ID: <19991007085425.03791.00000028@ng-fb1.aol.com> (raw)
Message-ID: <19991031135700.DkITuldItE9pG3tsj55lk-ebZ87_R8gqiAPvDhfIxY0@z> (raw)
In-Reply-To: <37FC6863.B665A878@veritas.com>
> .NSUBSPA $CODE$,QUAD=0,ALIGN=8,ACCESS=44,CODE_ONLY
>
> and do
> # gcc test.s
>
> It works fine.
>
> Should I have to use gnu assembler to get rid of this problem ?
Yes, the porting site ought to have a compatible version of binutils. It is
possible also to construct the current binutils and gnu compilers using only
the basic hpux tools, and it's worth the effort, even if you don't use g++.
Tim Prince
tprince@computer.org
next prev parent reply other threads:[~1999-10-07 5:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-10-07 0:35 Uday Birajdar
1999-10-07 1:10 ` Jeffrey A Law
1999-10-31 13:57 ` Jeffrey A Law
1999-10-07 5:55 ` Tim Prince [this message]
1999-10-31 13:57 ` Tim Prince
1999-10-31 13:57 ` Uday Birajdar
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=19991007085425.03791.00000028@ng-fb1.aol.com \
--to=n8tm@aol.comnojunk \
--cc=help-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).