On Thu, Jul 20, 2017 at 3:18 PM, Burton, Ross <ross.bur...@intel.com> wrote: > > On 20 July 2017 at 19:51, Khem Raj <raj.k...@gmail.com> wrote: >> >> it does cause harm, by making the behaviour inconsistent and highly >> dependent >> upon build host. > > > It *stops* behaviour being dependent on the build host, surely. The problem > is that some recipes use the host compiler when they're not meant to be and > this can cause subtle (or not so subtle) breakage. >
I think I do understand what it does, all of you dont have to keep repeating that :), my concern is a bit different as explained. Because such patches are sticky forever, if they dont get accepted into gcc, look at the cross include poisoning patch. If you run it via gcc ml, its possible they have better suggestions to get the same thing done. > Ross > -- _______________________________________________ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core