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: Sat, 29 Jan 2005 20:40:55 -0800	[thread overview]
Message-ID: <ff6e59bad677e5375666e34e99d50cbd@embeddededge.com> (raw)
In-Reply-To: <20050130014351.GB24482@gate.ebshome.net>

On Jan 29, 2005, at 5:43 PM, Eugene Surovegin wrote:

> This is taken from cpu/mips/config.mk

Which is the main thing I want to fix.  I don't yet know the proper
solution, but it sounds like there is at least consensus to try
another approach.  The main reason I'm asking is that I don't
have access to other MIPS boards for testing, and I didn't know
the history of this development.  I have several Alchemy Au1xxx
boards that I intend to get running with u-boot, in both big and
little endian modes, along with a couple of R4Kc custom cores.

> ifeq ($(ARCH),mips)
> CROSS_COMPILE = mips_4KC-
> endif

Any objections to setting CROSS_COMPILE in include/config.mk
and allow setting it within the 'mkconfig' part of the Makefile?
I still don't know what to do with the rest of the config.mk, as it
sets R4Kc specific flags based upon the binutils version.

Thanks.

	-- Dan

  reply	other threads:[~2005-01-30  4:40 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-29  2:13 [U-Boot-Users] MIPS build environment Dan Malek
2005-01-29 10:36 ` 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 [this message]
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=ff6e59bad677e5375666e34e99d50cbd@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