From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by yocto-www.yoctoproject.org (Postfix, from userid 118) id BAA24E00978; Mon, 22 Jun 2015 04:18:26 -0700 (PDT) X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on yocto-www.yoctoproject.org X-Spam-Level: X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00 autolearn=ham version=3.3.1 X-Spam-HAM-Report: * -1.9 BAYES_00 BODY: Bayes spam probability is 0 to 1% * [score: 0.0000] Received: from teledigit.eu (teledigit.eu [195.56.148.37]) by yocto-www.yoctoproject.org (Postfix) with ESMTP id 16CF7E00957 for ; Mon, 22 Jun 2015 04:18:13 -0700 (PDT) X-AuthUser: kgy@teledigit.eu Received: from [192.168.42.238] ([176.63.203.49]:48836) by teledigit.eu with [XMail 1.27 ESMTP Server] id for from ; Mon, 22 Jun 2015 13:18:04 +0200 Message-ID: <5587EEB0.50008@teledigit.eu> Date: Mon, 22 Jun 2015 13:17:04 +0200 From: =?UTF-8?B?R3nDtnJneSBLw7Z2ZXNkaQ==?= User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.7.0 MIME-Version: 1.0 To: meta-freescale@yoctoproject.org References: <20150621183207.0f614fb8@kgy-pc.lan> <5587C667.10701@teledigit.eu> In-Reply-To: <5587C667.10701@teledigit.eu> Subject: Re: Error compiling barebox on fido X-BeenThere: meta-freescale@yoctoproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Usage and development list for the meta-fsl-* layers List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 22 Jun 2015 11:18:26 -0000 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Hi, I tried to switch back to gcc 4.8 on fido, but the same error occurs. Is the gcc built differently on fido? Regards Gyorgy Kovesdi On 2015-06-22 10:25, György Kövesdi wrote: > Hi, > > I found that really the gcc causes the problem. > I created this test file (x.c): > > #include > int main() {} > > I tried to compile it this way: > > arm-poky-linux-gnueabi-gcc x.c > > On fido it fails, while on daisy, it succeeds. > I see that gcc 4.9 on fido does not have standard includes by default, > while gcc 4.8 on daisy does. However, it is set in CFLAGS, so all > compilation succeeded this way. > I will resolve barebox build by changing its make rules, but i don't > know if this is a problem with gcc 4.9 or not. Which behaviour is > standard? > > Regards > Gyorgy Kovesdi > > On 2015-06-21 18:32, Gyorgy Kovesdi wrote: >> Hi, >> >> I tried to compile barebox_2015.06 on the current fido, and got the >> following error: >> >> arm-poky-linux-gnueabi-gcc -Wp,-MD,scripts/.bareboxenv-target.d >> -Wall -Wundef -Wstrict-prototypes -Wno-trigraphs >> -Werror-implicit-function-declaration -fno-strict-aliasing >> -fno-common -Os -pipe -fno-stack-protector >> -Wno-unused-but-set-variable -Wno-trampolines >> -Wdeclaration-after-statement -Wno-pointer-sign -o >> scripts/bareboxenv-target scripts/bareboxenv.c >> scripts/bareboxenv.c:20:19: fatal error: stdio.h: No such file or >> directory >> #include >> ^ >> compilation terminated. >> >> Exactly the same command is executed when building on odler revisions >> (e.g. on current daisy), without problem. >> >> The difference I see that fido uses gcc 4.9 and daisy uses 4.8, but I >> think this is not the cause. >> What can be the problem? >> >> Thanks in advance >> György Kövesdi >