fixing vs WARN_CFLAGS vs cross builds

[Jim Wilson]

DJ Delorie wrote:
> I'm trying to cross-build a native DJGPP.  It tries to build fixinc,
> but uses "gcc" as the compiler.  It passes a full WARN_CFLAGS, which
> includes options that the system gcc doesn't understand, and so fails.
> Should we just not pass WARN_CFLAGS when cross compiling that way?

The gcc Makefile does not directly call "gcc" anywhere.  From a brief 
glance, I think you mean CC_FOR_BUILD, which you have set to gcc.

It isn't exactly clear why you have a problem though.  WARN_CFLAGS is 
set for a stage1 build only if the build (host?) compiler is gcc, and 
your compiler is gcc, so why is there a problem?  Is there a particular 
option which is the problem?  If so, which one?  Is this a versioning 
problem?  I.e. an option is in WARN_CFLAGS that is not supported by an 
old gcc version you are using for the bootstrap?  Or is the problem 
confusion between the host and build compiler, which may be different 
gcc versions?  Maybe we need a BUILD_WARN_CFLAGS separate from WARN_CFLAGS?

You haven't provided enough info here to see what the problem is.

It may be reasonable to remove the WARN_CFLAGS setting in the fixinc.sh 
rule.  We don't use WARN_CFLAGS anyplace else where we use CC_FOR_BUILD. 
  This can work in stage2 etc builds, but this is probably not important 
enough to worry about.

It would be nice to have a proper bug report though.
-- 
Jim Wilson, GNU Tools Support, http://www.SpecifixInc.com