This is the mail archive of the binutils@sources.redhat.com mailing list for the binutils project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: Bad ELF header when mixing MIPS II with MIPS I

From: "H . J . Lu" <hjl at lucon dot org>
To: Eric Christopher <echristo at redhat dot com>
Cc: binutils at sources dot redhat dot com
Date: Thu, 31 Jan 2002 12:36:55 -0800
Subject: Re: Bad ELF header when mixing MIPS II with MIPS I
References: <20020131092536.A19466@lucon.org> <1012508838.1399.4.camel@ghostwheel.cygnus.com> <20020131123213.A22701@lucon.org> <1012509235.1399.6.camel@ghostwheel.cygnus.com>

On Thu, Jan 31, 2002 at 12:33:54PM -0800, Eric Christopher wrote:
> 
> > Because the resulting binary contains the MIPS II instructions and it
> > won't run on MIPS I machines.
> 
> Where did you get crti.o from? If it has mips II instructions...

It doesn't matter. You can use foo.o which only contains MIPS I
instructions.


H.J.

Follow-Ups:
- Re: Bad ELF header when mixing MIPS II with MIPS I
  - From: Jason R Thorpe

References:
- Bad ELF header when mixing MIPS II with MIPS I
  - From: H . J . Lu
- Re: Bad ELF header when mixing MIPS II with MIPS I
  - From: Eric Christopher
- Re: Bad ELF header when mixing MIPS II with MIPS I
  - From: H . J . Lu
- Re: Bad ELF header when mixing MIPS II with MIPS I
  - From: Eric Christopher

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]