public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Dan Malek <dan@embeddededge.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] MIPS build environment
Date: Fri, 28 Jan 2005 18:13:23 -0800	[thread overview]
Message-ID: <e7af2eca2d0ca4432255ff965eb51330@embeddededge.com> (raw)


Hello all MIPS u-booters.

I'd like to discuss how we can make the MIPS
build environment a little bit easier to use.  For
example, the cpu/mips/config.mk assumes big
endian, and although I'll be the first to stand up
and say that's the only proper and useful byte
ordering, there are people willing to pay me
to assist with the alternative :-)  I'd like it if
we can just find a way to invoke 'mipseb-*'
or 'mipsel-*' based upon the configuration
chosen and let it go at that.

I'd also like us to agree to use up to date tools.
Again, the config.mk with the test and hard coded
flags depending upon tools seems unnecessary
since the newer tools have been around for a
while and proven to work.

Unless I'm doing something wrong, I also have
to use binutils with the 'allow_branch_to_undefined'
patch.

Comments?  Other concerns?

Thanks.


	-- Dan

             reply	other threads:[~2005-01-29  2:13 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-29  2:13 Dan Malek [this message]
2005-01-29 10:36 ` [U-Boot-Users] MIPS build environment Thomas Sailer
2005-01-29 17:08   ` Wolfgang Denk
2005-01-29 23:54     ` Thomas Sailer
2005-01-30  1:22       ` Wolfgang Denk
2005-01-29 17:03 ` Wolfgang Denk
2005-01-30  0:20 ` Eugene Surovegin
2005-01-30  1:24   ` Wolfgang Denk
2005-01-30  1:43     ` Eugene Surovegin
2005-01-30  4:40       ` Dan Malek
2005-01-30  9:18         ` Wolfgang Denk
2005-01-30 10:33           ` Eugene Surovegin
2005-01-30  9:13       ` Wolfgang Denk
2005-01-30 10:26         ` Eugene Surovegin
2005-09-24 23:16           ` Wolfgang Denk

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=e7af2eca2d0ca4432255ff965eb51330@embeddededge.com \
    --to=dan@embeddededge.com \
    --cc=u-boot@lists.denx.de \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox