From: Wolfgang Denk <wd@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] MIPS build environment
Date: Sun, 30 Jan 2005 10:18:55 +0100 [thread overview]
Message-ID: <20050130091900.AFD2DC108D@atlas.denx.de> (raw)
In-Reply-To: Your message of "Sat, 29 Jan 2005 20:40:55 PST." <ff6e59bad677e5375666e34e99d50cbd@embeddededge.com>
Deear Dan,
in message <ff6e59bad677e5375666e34e99d50cbd@embeddededge.com> you wrote:
>
ifndef CROSS_COMPILE
> > ifeq ($(ARCH),mips)
> > CROSS_COMPILE = mips_4KC-
> > endif
endif
> Any objections to setting CROSS_COMPILE in include/config.mk
> and allow setting it within the 'mkconfig' part of the Makefile?
Yes. Please don't do this, as it is not necessary. The "mips_4KC-"
setting above is just the default which is used when the user does
not supply a CROSS_COMPILE setting either in his environment or in
the make command line. This should be sufficient.
> 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.
This is because we needed a way to find out if
"allow_branch_to_undefined" is available; maybe you know a better
approach.
Best regards,
Wolfgang Denk
--
Software Engineering: Embedded and Realtime Systems, Embedded Linux
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de
A committee is a group that keeps the minutes and loses hours.
-- Milton Berle
next prev parent reply other threads:[~2005-01-30 9:18 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
2005-01-30 9:18 ` Wolfgang Denk [this message]
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=20050130091900.AFD2DC108D@atlas.denx.de \
--to=wd@denx.de \
--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