All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jim Wilson <wilson@cygnus.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] Problem compiling latest gcc (001024 snapshot)
Date: Wed, 15 Nov 2000 20:02:30 +0000	[thread overview]
Message-ID: <marc-linux-ia64-105590678205727@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590678205721@msgid-missing>

>../../gcc/config/ia64/lib1funcs.asm:655: Error: Unknown opcode `mov.ret.sptk

Somehow gcc accidentally used an out-of-date assembler.

>/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

The -B options here are in the wrong order.  If you have an old assembler in
/usr/ia64-mandrake-linux/bin/, then gcc will accidentally use this old
assembler instead of the new assembler in /usr/src/.../builddir/gcc.
This can be fixed by doing a "make install-gas" as Jes suggested, or by
renaming the old /usr/ia64-mandrake-linux tree to move it out of the way as
Bill suggested.

We've had a lot of problems with ordering of these -B options.  It has been
broken and fixed several times this year.  The current stable compiler I am
maintaining was made from a FSF gcc snapshot when this was broken.  This
is only a problem when there is an ABI change though, so hopefully you only
have to deal with this once.

>Oh, and BTW, .033 is unreadable, it's 600 on the FTP site.

Fixed.

Jim


      parent reply	other threads:[~2000-11-15 20:02 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-11-15  9:30 [Linux-ia64] Problem compiling latest gcc (001024 snapshot) Francis Galiegue
2000-11-15 14:51 ` Jes Sorensen
2000-11-15 20:02 ` Jim Wilson [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=marc-linux-ia64-105590678205727@msgid-missing \
    --to=wilson@cygnus.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.