All of lore.kernel.org
 help / color / mirror / Atom feed
From: "H. J. Lu" <hjl@lucon.org>
To: linux-kernel@vger.kernel.org,
	David Mosberger <davidm@napali.hpl.hp.com>,
	"Luck, Tony" <tony.luck@intel.com>
Subject: Re: binutils 2.15.90.0.1 break ia64 kernel crosscompiling
Date: Fri, 5 Mar 2004 08:50:48 -0800	[thread overview]
Message-ID: <20040305165048.GA15858@lucon.org> (raw)
In-Reply-To: <20040305142725.GA20926@MAIL.13thfloor.at>

I will make a new release to fix it.


H.J.
---
On Fri, Mar 05, 2004 at 03:27:25PM +0100, Herbert Poetzl wrote:
> 
> Hi Folks!
> 
> upgraded my Cross Compiling Toolchain[1] to binutils 2.15.90.0.1, 
> recompiled gcc 3.3.3 (just to make sure), and now linux 2.6.3
> doesn't compile for ia64 anymore ...
> 
> here is th funny part of the complete error log[2]
> 
> ------------------------------------------------------------------
>   {standard input}: Assembler messages:
>   {standard input}:1268: Internal error!
>   Assertion failure in md_assemble at config/tc-ia64.c line 10013.
>   Please report this bug.
> ------------------------------------------------------------------
> 
> so we are now down from 6 to 5 of 20 archs which compile 2.6.3
> with default config, will soon try with 2.6.4-rc*
> 
>                     linux-2.6.3                 linux-2.4.25
>                     config  build       config  dep     kernel  modules
>                     
> alpha/alpha:        OK      OK          OK      OK      OK      OK
> arm/arm:            FAILED  FAILED      OK      OK      FAILED  FAILED
> cris/cris:          FAILED  FAILED      OK      FAILED  FAILED  FAILED
> hppa/parisc:        OK      FAILED      OK      OK      FAILED  FAILED
> hppa64/parisc:      OK      FAILED      OK      OK      FAILED  FAILED
> i386/i386:          OK      OK          OK      OK      OK      OK
> ia64/ia64:          OK      FAILED      OK      OK      FAILED  FAILED
> m68k/m68k:          OK      FAILED      OK      OK      OK      OK
> mips/mips:          OK      FAILED      OK      OK      FAILED  FAILED
> mips64/mips:        OK      FAILED      OK      OK      FAILED  FAILED
> ppc/ppc:            OK      FAILED      OK      OK      OK      OK
> ppc64/ppc64:        OK      OK          OK      FAILED  FAILED  OK
> s390/s390:          OK      FAILED      OK      OK      FAILED  FAILED
> s390x/s390:         OK      FAILED      OK      OK      OK      OK
> sh/sh:              OK      FAILED      OK      FAILED  FAILED
> sh64/sh:            OK      FAILED      OK      OK      FAILED  FAILED
> sparc/sparc:        OK      FAILED      OK      OK      FAILED  FAILED
> sparc64/sparc64:    OK      OK          OK      OK      OK      OK
> v850/v850:          FAILED  FAILED      FAILED  FAILED  FAILED  FAILED
> x86_64/x86_64:      OK      OK          OK      OK      OK      OK
> 
> 
> best,
> Herbert
> 
> [1] http://vserver.13thfloor.at/Stuff/Cross/
> [2] http://vserver.13thfloor.at/Stuff/Cross/LOGS-2.6.3-gcc3.3.3-binutils2.15.90.0.1/ia64-build.err

  reply	other threads:[~2004-03-05 16:51 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-05 14:27 binutils 2.15.90.0.1 break ia64 kernel crosscompiling Herbert Poetzl
2004-03-05 16:50 ` H. J. Lu [this message]
2004-03-05 17:08 ` H. J. Lu
     [not found] <1woEF-7Yx-7@gated-at.bofh.it>
2004-03-05 14:52 ` Pascal Schmidt

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=20040305165048.GA15858@lucon.org \
    --to=hjl@lucon.org \
    --cc=davidm@napali.hpl.hp.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tony.luck@intel.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 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.