This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: fixing vs WARN_CFLAGS vs cross builds

On Tue, 2004-03-30 at 19:10, DJ Delorie wrote:
> Well, it is GCC, and strict1 propogates to WARN_CFLAGS, and
> WARN_CFLAGS is passed to fixinc.  But the compiler used in fixinc is a
> different gcc (BUILD_CC vs CC).

Thanks.  I see the problem now.  There is configure support that adds
options to strict1_warn based on CC.  I missed this when looking at the
code.  This was the info I was looking for.  These tests are obviously
unsafe when WARN_STRICT is used with CC_FOR_BUILD where CC_FOR_BUILD is
different from CC.

We would need a parallel set of tests and macros for a
BUILD_WARN_STRICT, and it seems unreasonable to ask you do that much
work to fix your cross compiler build problem.  So I think that simply
changing the fixinc.sh rule to not use WARN_STRICT is an acceptable
solution.
-- 
Jim Wilson, GNU Tools Support, http://www.SpecifixInc.com
Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]