From: Keith Owens <kaos@ocs.com.au>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] Announce: IA-64 cross compiler on IA-32 available
Date: Wed, 24 Jan 2001 23:27:05 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590693005091@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590693005089@msgid-missing>
On Wed, 24 Jan 2001 10:49:39 -0700 (MST),
Khalid Aziz <khalid@lyra.fc.hp.com> wrote:
>I recently built the latest version of IA-64 cross compiler on IA-32
>with all of the patches that have been posted on this mailing list. I
>have made the binaries available at
><ftp://puffin.external.hp.com/pub/ia64/gcc-2.96-ia64-000717-snap001117-build2.tar.gz>.
>The compiler is configured to be installed under /opt/ia64. I have built
>and tested kernels with it. I have also built a few applications which
>worked. Let me know if anything is missing from this package.
This version of gcc invokes 'as' without a path name so it picks up the
standard ia32 assembler instead of the cross assembler. This is
strange, it invokes 'cc1' with the correct path but not 'as'.
/opt/ia64/bin/ia64-cygnus-linux-gcc -v -D__KERNEL__ -I/build/kaos/2.4.0-kdb-ia64/include -Wall -Wstrict-prototypes -O2 -fno-strict-aliasing -fomit-frame-pointer -pipe -ffixed-r13 -mfixed-rangeñ0-f15,f32-f127 -funwind-tables -falign-functions2 -mb-step -mconstant-gp -c -o init/main.o init/main.c
Reading specs from /opt/ia64/lib/gcc-lib/ia64-cygnus-linux/2.96-ia64-000717/specs
gcc version 2.96-ia64-000717 snap 001117
/opt/ia64/lib/gcc-lib/ia64-cygnus-linux/2.96-ia64-000717/cpp -lang-c -v -I/build/kaos/2.4.0-kdb-ia64/include -D__GNUC__=2 -D__GNUC_MINOR__– -D__GNUC_PATCHLEVEL__=0 -D__ia64 -D__ia64__ -D__linux -D__linux__ -D_LONGLONG -Dlinux -Dunix -D__LP64__ -D__ELF__ -D__ia64 -D__ia64__ -D__linux -D__linux__ -D_LONGLONG -D__linux__ -D__unix__ -D__LP64__ -D__ELF__ -D__linux -D__unix -Asystem(linux) -Acpu(ia64) -Amachine(ia64) -D__OPTIMIZE__ -Wall -Wstrict-prototypes -D__LONG_MAX__’23372036854775807L -D__KERNEL__ init/main.c |
/opt/ia64/lib/gcc-lib/ia64-cygnus-linux/2.96-ia64-000717/cc1 -quiet -dumpbase main.c -mfixed-rangeñ0-f15,f32-f127 -mb-step -mconstant-gp -O2 -Wall -Wstrict-prototypes -version -fno-strict-aliasing -fomit-frame-pointer -ffixed-r13 -funwind-tables -falign-functions2 -o - |
as -x -mconstant-gp -o init/main.o -
GNU CPP version 2.96-ia64-000717 snap 001117 (cpplib)
(IA-64)
ignoring nonexistent directory "/opt/ia64/ia64-cygnus-linux/include"
#include "..." search starts here:
#include <...> search starts here:
/build/kaos/2.4.0-kdb-ia64/include
/opt/ia64/lib/gcc-lib/ia64-cygnus-linux/2.96-ia64-000717/include
/opt/ia64/ia64-cygnus-linux/sys-include
End of search list.
GNU C version 2.96-ia64-000717 snap 001117 (ia64-cygnus-linux) compiled by GNU C version 2.95.2 20000220 (Debian GNU/Linux).
as: unrecognized option `-x'
init/main.c:207: output pipe has been closed
ia64-cygnus-linux-gcc: Internal compiler error: program cpp got fatal signal 13
next prev parent reply other threads:[~2001-01-24 23:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-24 17:49 [Linux-ia64] Announce: IA-64 cross compiler on IA-32 available Khalid Aziz
2001-01-24 23:27 ` Keith Owens [this message]
2001-01-24 23:52 ` Keith Owens
2001-01-25 1:12 ` Khalid Aziz
2001-01-25 6:43 ` Mark Goodwin
2001-01-25 16:44 ` Khalid Aziz
2001-01-30 20:56 ` Khalid Aziz
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=marc-linux-ia64-105590693005091@msgid-missing \
--to=kaos@ocs.com.au \
--cc=linux-ia64@vger.kernel.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