Hi 2016-04-05 2:44 GMT+02:00 Khem Raj <[email protected]>: > On Mon, Apr 4, 2016 at 12:56 AM, Andreas Müller > <[email protected]> wrote: >> On Mon, Apr 4, 2016 at 4:36 AM, Khem Raj <[email protected]> wrote: >>> On Sun, Apr 3, 2016 at 4:00 PM, Richard Purdie >>> <[email protected]> wrote: >>>>> I added some text to bugzilla. The gist is: In poky the sources are >>>>> not deployed. >>>> >>>> I don't understand that. If you mean playing sources in the -dbg >>>> packages, poky does that too. Is there some specific configuration >>>> Angstrom makes which triggers this? >>>> >>>> There was a bug in master recently which broke source file deployment >>>> into -dbg packages but that was a bug everywhere which was then fixed >>>> when we realised.
I gave some misleading information. I checked out poky a few days before angstrom and thus poky did not include the commit which fixed the deployment of the debug sources while angstrom did. http://cgit.openembedded.org/openembedded-core/commit/meta/classes/package.bbclass?h=master-next&id=ecb56a6ae0c870af680da03db9d39703b525fc98 So with that patch applied my poky build does deploy the sources but does not show the host contamination warnings. Sorry for the red heering. @ Andreas * Which version of cpio does your build host distribution ship openSUSE Leap 42.1: cpio (GNU cpio) 2.11 Fedora 20: cpio (GNU cpio) 2.11 * do you see floods of host contamination warnings for shipped source files? Yes, on both systems. @ Richerd > You could install a copy of our buildtools tarball, see if the problem > goes away with that installed? I will try that out. However, as I did setup a poky and an angstrom build on the same machine likely the host build tools will not be the culprit. >>> >>> Max, somewhere in thread you indicated angstrom 2015.12 release which >>> would be actually using jethro >>> and if it has been recently fixed in master than it would explain why >>> it worked on poky/master and not on angstrom >>> may be this fix should be cherry-picked to jethro. >> I checked Angstrom master but did not find matching commit. Which >> commit are you referring to? > > Just ensure that angstrom master is using master of OE-Core ( latest ) > and if problem still is there then second thing would be the toolchain it uses > might be coming from meta-linaro, now see if there are any gcc patches > that are in OE-Core but not in meta-linaro which could cause this kind > of stuff Note that I tested this with qemux86. For x86 angstrom is not using the linaro toolchain. (And I usually build for ARM where I also see the issue) >> >> Andreas > -- > _______________________________________________ > Openembedded-core mailing list > [email protected] > http://lists.openembedded.org/mailman/listinfo/openembedded-core -- _______________________________________________ Openembedded-core mailing list [email protected] http://lists.openembedded.org/mailman/listinfo/openembedded-core
