I'm sorry, for some reason this thread in Gmail starts with the morty review you've sent, but when I look in my favorite mutt, I see that my replies were linked with pyro review where you're right the files aren't included.
Still I would like to see what's the diff between gcc-6.4 in morty and pyro and gcc-6.4 which was in master (and there is still gcc-6.3 in rocko which should imho be upgraded first to preserve continuity). On Sun, Mar 4, 2018 at 2:35 PM, Martin Jansa <[email protected]> wrote: > Are we both talking about the same morty-next? > > docker-shr @ ~/openembedded-core $ git log origin/morty-next -- > meta/recipes-devtools/gcc/gcc-6.4/CVE-2016-4490.patch > commit a926f3986174b67375c4486e5b3f27ad3b939e28 > Author: Juro Bystricky <[email protected]> > Date: Thu Mar 1 13:38:08 2018 -0800 > > gcc6: Upgrade to 6.4.0 (latest stable series release) > > Changed BINV and PV from 6.2.0 to 6.4.0 > Modified BASEURI to load xz tarball instead of bz2 > > Backported series of patches from https://github.com/hjl-tools/gcc.git > branch /hjl/indirect/gcc-6-branch/master which contains > an IA patch series for security related issues > > ubsan-fix-check-empty-string.patch : removed, already applied > > Signed-off-by: Juro Bystricky <[email protected]> > docker-shr @ ~/openembedded-core $ git show -1 > a926f3986174b67375c4486e5b3f27ad3b939e28 -M | grep CVE-2016-4490.patch > diff --git a/meta/recipes-devtools/gcc/gcc-6.2/CVE-2016-4490.patch > b/meta/recipes-devtools/gcc/gcc-6.4/CVE-2016-4490.patch > rename from meta/recipes-devtools/gcc/gcc-6.2/CVE-2016-4490.patch > rename to meta/recipes-devtools/gcc/gcc-6.4/CVE-2016-4490.patch > > > On Sun, Mar 4, 2018 at 2:26 PM, Richard Purdie <richard.purdie@ > linuxfoundation.org> wrote: > >> On Sun, 2018-03-04 at 13:08 +0100, Martin Jansa wrote: >> > And the same with >> > meta/recipes-devtools/gcc/gcc-6.4/CVE-2016-4490.patch >> > which isn't included in SRC_URI since: >> >> As far as I can tell this isn't included in the patch or the >> repository? >> >> Cheers, >> >> Richard >> > >
-- _______________________________________________ Openembedded-core mailing list [email protected] http://lists.openembedded.org/mailman/listinfo/openembedded-core
