From mboxrd@z Thu Jan 1 00:00:00 1970 From: Detlef Vollmann Date: Tue, 17 May 2005 07:12:20 +0200 Subject: [U-Boot-Users] Makefile problems References: <20050516230451.E1E29C1512@atlas.denx.de> Message-ID: <42897D34.1D5EDE7@vollmann.ch> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.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/