Dear Simon, In message <CAPnjgZ2a+qrsPWTz5Y=48m_lcrqaiky0-sejudw8ay5asdw...@mail.gmail.com> you wrote: > > > I think this is not a good way to address this issue. The GCC > > documentation (section "System-specific Predefined Macros" [1]) > > desribes how this should be handled. The "correct" (TM) way to fix > > this is by adding "-ansi" or any "-std" option that requests strict > > conformance to the compiler/preprocessor command line. > > > > [1] > > http://gcc.gnu.org/onlinedocs/cpp/System_002dspecific-Predefined-Macros.html#System_002dspecific-Predefined-Macros > > Stephen suggested a slightly more extreme version too - I was worried > that all the typing stuff in U-Boot headers would break in this case, > but I didn't actually test it, so perhaps it is fine.
Yes, I've seen it. I think either approach is better that manually undef-ing specific variables. From my personal point of view I think the -undef approach is a bit of overkill, but I would not protest. Best regards, Wolfgang Denk -- DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: w...@denx.de panic: can't find / _______________________________________________ devicetree-discuss mailing list devicetree-discuss@lists.ozlabs.org https://lists.ozlabs.org/listinfo/devicetree-discuss