All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Bradley D. LaRonde" <brad@ltc.com>
To: "Marc Karasek" <marc_karasek@ivivity.com>,
	"Linux MIPS" <linux-mips@oss.sgi.com>
Subject: Re: BE Toolchain
Date: Fri, 2 Nov 2001 10:49:58 -0500	[thread overview]
Message-ID: <00dd01c163b6$064a39d0$3501010a@ltc.com> (raw)
In-Reply-To: 1004708261.31067.6.camel@localhost.localdomain

I think it should be mips-linux, not mipseb-linux.

Regards,
Brad

----- Original Message ----- 
From: "Marc Karasek" <marc_karasek@ivivity.com>
To: "Linux MIPS" <linux-mips@oss.sgi.com>
Sent: Friday, November 02, 2001 8:37 AM
Subject: BE Toolchain


> Has anyone got the toolchain (binutils, gcc, glibc) to compile under
> BE?  I followed the instructions at Bradley D. LaRonde has put together
> and got the LE to work w/o a prolem.  I then proceeded to try the BE. 
> Binutils compiled ok, gcc says that mipseb-linux is not a valid target. 
> Looking in config.sub I saw a mips-linux, is this the BE option?  
> 
> Thanks,
> 
> -- 
> /*************************
> Marc Karasek
> Sr. Firmware Engineer
> iVivity Inc.
> marc_karasek@ivivity.com
> (770) 986-8925
> (770) 986-8926 Fax
> *************************/
> 

      parent reply	other threads:[~2001-11-02 15:49 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-02 13:37 BE Toolchain Marc Karasek
2001-11-02 14:06 ` Dan Temple
2001-11-02 14:18   ` Marc Karasek
2001-11-02 15:36     ` H . J . Lu
2001-11-13 14:49   ` Marc Karasek
2001-11-13 15:55     ` H . J . Lu
2001-11-13 16:17       ` Marc Karasek
2001-11-13 16:30         ` H . J . Lu
2001-11-13 16:45         ` Alan Cox
2001-11-13 16:45           ` Alan Cox
2001-11-13 19:30         ` Pete Popov
2001-11-15 21:42       ` SGI harddisk only - Debian install Garrick Evans
2001-11-16  1:05         ` Garrick Evans
2001-11-02 15:49 ` Bradley D. LaRonde [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='00dd01c163b6$064a39d0$3501010a@ltc.com' \
    --to=brad@ltc.com \
    --cc=linux-mips@oss.sgi.com \
    --cc=marc_karasek@ivivity.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.