From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jeroen Hofstee Date: Tue, 20 May 2014 20:06:57 +0200 Subject: [U-Boot] Building under Cygwin - "-ansi" flag? In-Reply-To: References: <20140509150821.GI22182@bill-the-cat> Message-ID: <1400609217.2002.37.camel@yellow> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de Dear Vasili, On ma, 2014-05-19 at 12:45 +0300, Vasili Galka wrote: [...] > 2. I see a reoccurring pattern of some headers being used from the host, > causing mismatches and arising build errors. Then some way is sought > to include headers from U-Boot tree prior to them which solves the > problem. This happens for both Linux and Cygwin. you can add FreeBSD to the list as well, see [1] > This pattern is a > result of the original decision from 2004 to prioritize the host > include paths over the paths from U-Boot tree. any reference? > I see this happening > again and again with different headers in the future. So here comes > the question, is it really the right thing prioritize the include > paths this way? Why do host paths MUST come first? > I'll try reverting this locally and looking what breaks and what > alternative solutions exist. I have no idea why it is the way it is, but keep in mind that e.g. stdio headers in u-boot is quite something different then stdio for the target userland. Regards, Jeroen [1] http://lists.denx.de/pipermail/u-boot/2014-May/179301.html