From: =?iso-8859-1?Q?M=E5ns_Rullg=E5rd?= Date: Mon, 18 Nov 2013 16:39:19 +0000 Subject: [U-Boot] [PATCH] include: define bool type in a more portable way In-Reply-To: <20131118163238.GF420@bill-the-cat> (Tom Rini's message of "Mon, 18 Nov 2013 11:32:38 -0500") References: <1384770105-32364-1-git-send-email-yamada.m@jp.panasonic.com> <20131118162856.1403C38043B@gemini.denx.de> <20131118163238.GF420@bill-the-cat> Message-ID: List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de Tom Rini writes: > On Mon, Nov 18, 2013 at 05:28:56PM +0100, Wolfgang Denk wrote: >> Dear Masahiro Yamada, >> >> In message <1384770105-32364-1-git-send-email-yamada.m@jp.panasonic.com> you wrote: >> > Currently U-boot defins bool type by including >> > rather than defining directly. >> > But it does not work for some cross compilers. >> >> Can you explain why this fails? >> >> AFAICT, is a compiler provided header file, which is >> mandatory by the C99 ISO standard. So if a compiler fails to work >> using it, it looks as if the compiler was broken. > > Indeed. And the very ancient but (as far as I know) still "latest" gcc > for the SPARC port, which is 3.4.4, has it. So if there's a problem > here with blackfin it feels strongly like a toolchain issue. FWIW, my Blackfin cross-gcc has a correct stdbool.h. Even gcc 2.95 has it. -- M?ns Rullg?rd mans at mansr.com