From: Detlef Vollmann <dv@vollmann.ch>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] Makefile problems
Date: Mon, 16 May 2005 20:09:52 +0200 [thread overview]
Message-ID: <4288E1F0.52B7590@vollmann.ch> (raw)
In-Reply-To: 42889324.7080604@themalago.net
Simon Poole wrote:
>
> I'm not sure why "HOSTCC=gcc-3 make -e" isn't working. This should
> override the declaration in config.mk.
>
> However, you can always try the alternative (better) syntax:
> make HOSTCC=gcc-3
The problem with this is, that I have to remeber that every time
I issue the command (and my customers as well).
If the first version would work, I could put the variable
in the shell startup file.
> make -e should be avoided because it causes *all* of your environment
> variables to override declarations in the Makefile.
I believe that is what I want.
The problem with it is that it works recursively: the definitions
in the main makefile overide the ones from the sub-makefile.
And that causes the sources in the tools directory to be
compiled with the CC from the main makefile, which is the
cross compiler :-(
> Using the format
> above you can explicity override individual variables.
On each single invocation. And that is what I want to avoid.
Detlef
--
Detlef Vollmann vollmann engineering gmbh
Linux and C++ for Embedded Systems http://www.vollmann.ch/
next prev parent reply other threads:[~2005-05-16 18:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-13 23:48 [U-Boot-Users] Makefile problems Detlef Vollmann
2005-05-16 12:33 ` Simon Poole
2005-05-16 18:09 ` Detlef Vollmann [this message]
2005-05-16 23:04 ` Wolfgang Denk
2005-05-17 5:12 ` Detlef Vollmann
2005-05-17 7:17 ` Wolfgang Denk
2005-05-17 14:56 ` Simon Poole
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=4288E1F0.52B7590@vollmann.ch \
--to=dv@vollmann.ch \
--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 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.