[asterisk-bugs] [Zaptel 0012056]: HOSTCC not exported by top level Makefile causes makefw compile to fail

noreply at bugs.digium.com noreply at bugs.digium.com
Wed Feb 27 02:05:43 CST 2008


A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=12056 
====================================================================== 
Reported By:                davidw
Assigned To:                
====================================================================== 
Project:                    Zaptel
Issue ID:                   12056
Category:                   General
Reproducibility:            always
Severity:                   minor
Priority:                   normal
Status:                     new
Zaptel Version:              SVN 
SVN Branch (only for SVN checkouts, not tarball releases):  1.4  
SVN Revision (number only!): 3874 
Disclaimer on File?:        N/A 
Request Review:              
====================================================================== 
Date Submitted:             02-24-2008 04:19 CST
Last Modified:              02-27-2008 02:05 CST
====================================================================== 
Summary:                    HOSTCC not exported by top level Makefile causes
makefw compile to fail
Description: 
The Makefile does not explicitly export HOSTCC.  As this is not in the
initial environment, GNU Make does not export it by default.  As a result,
the make in the kernel directory, which does not independently include
makeopts, the file that actually includes the definition of HOSTCC,
substitutes a null string for HOSTCC resulting in a command not found when
compiling the, host platform, utiity makefw.
====================================================================== 

---------------------------------------------------------------------- 
 tzafrir - 02-27-08 02:05  
---------------------------------------------------------------------- 
I feel we're stepping over Kbuild's definitions. IIRC we already had a
problem before where we accidentally stepped over Kbuild's value of ARCH.

We implicitly pass the target ARCH to Kbuild through the the kernel build
directory.

Or is this the kernel 2.4 build system alone?

In that case let's pass those variables explicitly, and not use 'export'. 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
02-27-08 02:05  tzafrir        Note Added: 0083007                          
======================================================================




More information about the asterisk-bugs mailing list