On Sun, May 1, 2011 at 7:40 PM, Bruce Ashfield <[email protected]> wrote: > On Sun, May 1, 2011 at 9:14 PM, Khem Raj <[email protected]> wrote: >> Hi >> >> I am trying to test this patch >> >> http://uclibc.org/~kraj/perf-tool-Fix-gcc-4.6.0-issues.patch >> >> to fix the build using gcc 4.6.0 but the kernel patching for yocto is >> not as usual as other recipes >> since it uses entire set of tooling around it. >> >> I tried to look around for documentation and few references I found >> >> https://wiki.pokylinux.org/wiki/Wind_River_Kernel >> >> discourages putting patches in metadata. and in another document it >> says it uses git to do patching but does not explain how. >> >> So if someone can explain in simple terms how to patch a linux-yocto >> would be really helpful from a >> developer POV or any documentation will be helpful. >> >> How do people develop/test patches on linux-yocto I understand >> eventually they are desired to be part >> of linux-yocto git but that comes after they are tried and tested locally >> >> I would have preferred to have the usual SRC_URI patching atleast for >> local testing. As of now >> it seems not to use normal OE recipe procedures. > > Are you actually not seeing this work ? I put in place compatibility > with existing patching via the SRC_URI for just this reason. A patch > specified in the SRC_URI will be picked up by the tools and applied > to the end of the BSP branch during the patching phase. >
if it worked. I would not be writing this email :) > It has definitely worked during all the development cycles, so if you > are seeing it not work, it's a bug and I'll fix it. > > Cheers, > > Bruce > >> >> Thanks >> -Khem >> >> _______________________________________________ >> Openembedded-core mailing list >> [email protected] >> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core >> > > > > -- > "Thou shalt not follow the NULL pointer, for chaos and madness await > thee at its end" > > _______________________________________________ > Openembedded-core mailing list > [email protected] > http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core > _______________________________________________ Openembedded-core mailing list [email protected] http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
