public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: Bill Nottingham <notting@redhat.com>
To: linux-ia64@vger.kernel.org
Subject: [Linux-ia64] Re: Problem compiling latest gcc (001024 snapshot)
Date: Wed, 15 Nov 2000 14:52:00 +0000	[thread overview]
Message-ID: <marc-linux-ia64-105590678205724@msgid-missing> (raw)

Francis Galiegue (fg@mandrakesoft.com) said: 
> I tried to get the latest snapshot of gcc on cygnus to compile... but it fails
> with this error:
> 
> /usr/src/RPM/BUILD/src/builddir/gcc/xgcc -B/usr/src/RPM/BUILD/src/builddir/gcc/
> -B/usr/ia64-mandrake-linux/bin/ -I/usr/ia64-mandrake-linux/include -O2
> -DIN_GCC    -O2 -isystem ./include  -fPIC -g1
> -DIN_LIBGCC2 -D__GCC_FLOAT_NOT_NEEDED  -I. -I../../gcc -I../../gcc/config
> -I../../gcc/../include -DL__nonlocal_goto -xassembler-with-cpp -c
> ../../gcc/config/ia64/lib1funcs.asm -o libgcc/./__nonlocal_goto.o
> ../../gcc/config/ia64/lib1funcs.asm: Assembler messages:
> ../../gcc/config/ia64/lib1funcs.asm:655: Error: Unknown opcode `mov.ret.sptk
> rp=in0,.L0'
> make[2]: *** [libgcc/./__nonlocal_goto.o] Error 1
> 
> Machine is a BigSur, A0 stepping CPU. Glibc is 2.1.3 (and 2.1.3 patch is
> applied), gcc is 2.9-ia64-000216-final. Kernel is 2.4.0-test7 with ia64 patch.
> I also tried to compile with RCS patches present in the snap directory, up to
> 031, but to no avail, still the same error. READMEs in the sources don't help.

mv /usr/ia64-mandrake-linux /usr/foo ; rebuild.

It accidentally started using the wrong assembler.

Bill


             reply	other threads:[~2000-11-15 14:52 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-11-15 14:52 Bill Nottingham [this message]
2000-11-16  2:59 ` [Linux-ia64] Re: Problem compiling latest gcc (001024 snapshot) H . J . Lu

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-105590678205724@msgid-missing \
    --to=notting@redhat.com \
    --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