public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Detlef Vollmann <dv@vollmann.ch>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] Makefile problems
Date: Tue, 17 May 2005 07:12:20 +0200	[thread overview]
Message-ID: <42897D34.1D5EDE7@vollmann.ch> (raw)
In-Reply-To: 20050516230451.E1E29C1512@atlas.denx.de

Wolfgang Denk wrote:
> In message <4288E1F0.52B7590@vollmann.ch> you wrote:
> > > 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).
> 
> You better know exactly what you are doing, so having to remember the
> correct command is a Good Thing (TM).
Hmm, so if my host's C compiler happens to be named gcc, I don't
have to remember, but if it happens to be named differently
(ncc, como, gcc-3, acc, ...) I need to remember?
Strange policy...

> > If the first version would work, I could put the variable
> > in the shell startup file.
> 
> ... and run into trouble with other builds failing  in  "interesting"
> ways later. No, thanks.
Well, that's the way all the packages using 'configure' work.
They pick up whatever is defined in your environment at
configure time.

And as I wrote, my most preferred solution would be something
like 'HOSTCC=gcc-3 make xyz_config'.  To achieve this, a simple
line like '[ $HOSTCC ] && echo "HOSTCC = $HOSTCC" >> config.mk'
in mkconfig would probably suffice.  But maybe there's another
(better) way.

 Detlef

-- 
Detlef Vollmann   vollmann engineering gmbh
Linux and C++ for Embedded Systems    http://www.vollmann.ch/

  reply	other threads:[~2005-05-17  5:12 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
2005-05-16 23:04     ` Wolfgang Denk
2005-05-17  5:12       ` Detlef Vollmann [this message]
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=42897D34.1D5EDE7@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox