All of lore.kernel.org
 help / color / mirror / Atom feed
From: Simon Poole <simon.armlinux@themalago.net>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] Makefile problems
Date: Mon, 16 May 2005 13:33:40 +0100	[thread overview]
Message-ID: <42889324.7080604@themalago.net> (raw)
In-Reply-To: <42853CE2.181F62BF@vollmann.ch>

Detlef Vollmann wrote:
> Hello,
> 
> as the command constants in cmd_confdefs.h are long longs,
> the programs in tools that include a board configuration file
> dont't compile with GCC 2.x.  But on a number of workstations
> the 'gcc' command is still 2.95.x, while the 3.x version
> is named gcc3, gcc-3 or similar.
> One way to solve this is to add a line to tools/Makefile like
> HOSTCC=gcc-3
> But now I need a different makefile on different machines.
> To avoid this, I tried things like
>  $ HOSTCC=gcc-3 make
> or even
>  $ HOSTCC=gcc-3 make -e
> but none of these worked.
> The most elegant version would be to give the HOSTCC at
> configuration time, i.e.
>  $ HOSTCC=gcc-3 make xyz_config
> But I have no idea whether this is possible and if so how
> to implement it.
> 
> Any ideas?
> 
>  Detlef
> 

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

make -e should be avoided because it causes *all* of your environment 
variables to override declarations in the Makefile.  Using the format 
above you can explicity override individual variables.

--
Simon Poole
www.appliancestudio.com

  reply	other threads:[~2005-05-16 12:33 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 [this message]
2005-05-16 18:09   ` Detlef Vollmann
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=42889324.7080604@themalago.net \
    --to=simon.armlinux@themalago.net \
    --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.