From: Thiemo Seufer <ths@networkno.de>
To: "Fu, He Wei PSE NKG" <hewei.fu@siemens.com>
Cc: Daniel Jacobowitz <dan@debian.org>, linux-mips@linux-mips.org
Subject: Re: The difference between mips*-gnu and mips*-linux when configure tool-chain
Date: Tue, 5 Dec 2006 12:43:56 +0000 [thread overview]
Message-ID: <20061205124355.GB26046@networkno.de> (raw)
In-Reply-To: <96E7D5519FC3D741BEE27AB88C7387970167840A@PEKW934A.cn001.siemens.net>
Fu, He Wei PSE NKG wrote:
> Thanks, sorry for I missed the mips*-elf for mips*-gnu.
>
> I think that for ld,the difference between mips*-elf and mips*-linux
> produces only some minor impact on the default ld script, for the
> behavior of ld itself, it has not serious impact.Is it my understanding
> correct?
>
> But for bfd, does the difference of these two config-choice have impact
> on the behavior of two different bfd-target? .
For both cases the resulting object file layout is different. mips*-elf
uses SGI-style, mips*-linux uses "traditional" style. I expect the
"traditional" format to get better long-term maintenance.
For a stand-alone bootloader both do for now, but I would prefer
mips*-linux since it eliminates the need for one extra compiler
when building a Linux environment.
Thiemo
prev parent reply other threads:[~2006-12-05 12:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-03 9:15 The difference between mips*-gnu and mips*-linux when configure tool-chain Fu, He Wei PSE NKG
2006-12-03 9:15 ` Fu, He Wei PSE NKG
2006-12-03 17:05 ` Daniel Jacobowitz
2006-12-05 3:41 ` Fu, He Wei PSE NKG
2006-12-05 3:41 ` Fu, He Wei PSE NKG
2006-12-05 12:43 ` Thiemo Seufer [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=20061205124355.GB26046@networkno.de \
--to=ths@networkno.de \
--cc=dan@debian.org \
--cc=hewei.fu@siemens.com \
--cc=linux-mips@linux-mips.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.