From mboxrd@z Thu Jan 1 00:00:00 1970 From: Thomas Petazzoni Date: Mon, 27 Aug 2018 10:28:15 +0200 Subject: [Buildroot] Analysis of defconfig build failures In-Reply-To: <87in3w9qjj.fsf@dell.be.48ers.dk> References: <20180812170138.0b51be07@windsurf> <87600bbg68.fsf@dell.be.48ers.dk> <20180815213421.08e0a3b6@windsurf> <87ftzf9v7u.fsf@dell.be.48ers.dk> <20180816001829.3f7a1436@windsurf> <20180816220655.37fbff34@windsurf> <87in3w9qjj.fsf@dell.be.48ers.dk> Message-ID: <20180827102815.23605ecd@windsurf> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: buildroot@busybox.net Hello, On Mon, 27 Aug 2018 10:12:16 +0200, Peter Korsgaard wrote: > > I.e. there is preprocessing of the dts file, then the actual > > compilation via dtc. > > With this in mind, I actually don't think that this behavior is > > negatively impacted by my changes. I now think it is a failure on top > > of the original failures. When I undo my changes prior to running this > > command, then the same errors occur. And since no other binary than > > the compiler (preprocessor) and the prebuilt dtc is used, there cannot > > be other impact of the changes I did to two header files. > > > Nevertheless, this defconfig still does not build correctly. > > :/ > > I guess giving the timing, the best solution for 2018.08 is to simply > revert the dtc bump? Is this fixing all issues we have, without introducing other problems ? If so, then I'm fine with a revert of the dtc bump, of course. Thomas -- Thomas Petazzoni, CTO, Bootlin Embedded Linux and Kernel engineering https://bootlin.com