From: Neal Becker <neal@ctd.comsat.com>
To: egcs@cygnus.com
Subject: hpux10 egcs1.0 --with-gnu-as broken
Date: Thu, 11 Dec 1997 08:28:00 -0000 [thread overview]
Message-ID: <E0xgBTJ-0004dx-00@laforge.ctd.comsat.com> (raw)
CC='gcc -B/usr/local/lib/gcc-lib/hppa1.1-hp-hpux10/2.7.2.2/'
/hosts/data/src/egcs-1.0/configure --with-gnu-as --enable-shared
--host=hppa1.1-hp-hpux10 --verbose
make
[...]
/cae/src/hppa1.1-hpux10/egcs-1.0/gcc/xgcc -B/cae/src/hppa1.1-hpux10/egcs-1.0/gcc/ -DIN_GCC -g -I./include -I. -I/hosts/data/src/egcs-1.0/gcc -I/hosts/data/src/egcs-1.0/gcc/config \
-c /hosts/data/src/egcs-1.0/gcc/objc/hash.c -o objc/hash.o
as: "/var/tmp/cca17843.s", line 10: error 1052: Directive name not recognized - FILE
as: "/var/tmp/cca17843.s", line 12: error 1052: Directive name not recognized - STABS
as: "/var/tmp/cca17843.s", line 13: error 1052: Directive name not recognized - STABS
as: "/var/tmp/cca17843.s", line 18: error 1052: Directive name not recognized - STABS
[...]
I believe there is a problem with pa-hpux10.h. It is setting
#ifndef CROSS_COMPILE
#undef MD_EXEC_PREFIX
#define MD_EXEC_PREFIX "/usr/ccs/bin/"
#endif
But I asked for gas. I don't want to use /usr/ccs/bin.
next reply other threads:[~1997-12-11 8:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-12-11 8:28 Neal Becker [this message]
1997-12-11 10:01 ` Jeffrey A Law
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=E0xgBTJ-0004dx-00@laforge.ctd.comsat.com \
--to=neal@ctd.comsat.com \
--cc=egcs@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).