On Sun, Aug 7, 2022 at 12:00 PM Martin Jansa <[email protected]> wrote: > > Thanks Khem, > > v3 builds fine with gprofng enabled again. > > Tested-by: Martin Jansa <[email protected]> > > any idea why binutils-2.39 v3 version isn't visible on patchwork yet? > https://patchwork.yoctoproject.org/project/oe-core/list/?series=&submitter=&state=*&q=binutils&archive=&delegate= > it's almost 1,5 hour since you sent it to ML > https://lists.openembedded.org/g/openembedded-core/message/169001 > > Usually patchwork doesn't have such long delay (v2 was there shortly after > I've noticed it in my mbox). >
I am not sure, sometimes patchwork chokes on largish patches, and this patch is large, especially v3 has bigger 0008-Use-libtool-2.4.patch grew to 1.2M from 1M in v2. Perhaps it crossed some sort of size boundary perhaps. > On Sun, Aug 7, 2022 at 7:37 PM Khem Raj <[email protected]> wrote: >> >> On Sun, Aug 7, 2022 at 9:41 AM Martin Jansa <[email protected]> wrote: >> > >> > >> > >> > On Sun, Aug 7, 2022 at 6:06 PM Khem Raj <[email protected]> wrote: >> >> >> >> Details of changes [1] >> >> >> >> [1] https://sourceware.org/pipermail/binutils/2022-August/122246.html >> >> >> >> Signed-off-by: Khem Raj <[email protected]> >> >> --- >> >> v2: Remove trailing .0 from PV >> >> >> >> meta/conf/distro/include/tcmode-default.inc | 2 +- >> >> .../{binutils-2.38.inc => binutils-2.39.inc} | 26 +- >> >> ....38.bb => binutils-cross-canadian_2.39.bb} | 0 >> >> ...38.bb => binutils-cross-testsuite_2.39.bb} | 0 >> >> ...s-cross_2.38.bb => binutils-cross_2.39.bb} | 0 >> >> ...ssdk_2.38.bb => binutils-crosssdk_2.39.bb} | 0 >> >> ...s-crosssdk-Generate-relocatable-SDKs.patch | 2 +- >> >> ...o-not-generate-linker-script-directo.patch | 2 +- >> >> ...dk-Search-for-alternative-ld.so.conf.patch | 16 +- >> >> ...004-Point-scripts-location-to-libdir.patch | 10 +- >> >> ...tro-compiler-point-to-the-wrong-ins.patch} | 2 +- >> >> ...system-directories-when-cross-linki.patch} | 42 +- >> >> ...ct-assembling-for-ppc-wait-mnemonic.patch} | 8 +- >> >> ...l-2.4.patch => 0008-Use-libtool-2.4.patch} | 2131 ++++++++--------- >> >> ...-in-libtool-when-sysroot-is-enabled.patch} | 2 +- >> >> ...> 0010-sync-with-OE-libtool-changes.patch} | 2 +- >> >> ...r-clang-before-checking-gcc-version.patch} | 10 +- >> >> ...RPATH-entry-if-LD_RUN_PATH-is-not-e.patch} | 17 +- >> >> .../0013-Avoid-as-info-race-condition.patch | 75 - >> >> .../binutils/0014-CVE-2019-1010204.patch | 49 - >> >> .../{binutils_2.38.bb => binutils_2.39.bb} | 0 >> >> 21 files changed, 1129 insertions(+), 1267 deletions(-) >> >> rename meta/recipes-devtools/binutils/{binutils-2.38.inc => >> >> binutils-2.39.inc} (60%) >> >> rename meta/recipes-devtools/binutils/{binutils-cross-canadian_2.38.bb >> >> => binutils-cross-canadian_2.39.bb} (100%) >> >> rename meta/recipes-devtools/binutils/{binutils-cross-testsuite_2.38.bb >> >> => binutils-cross-testsuite_2.39.bb} (100%) >> >> rename meta/recipes-devtools/binutils/{binutils-cross_2.38.bb => >> >> binutils-cross_2.39.bb} (100%) >> >> rename meta/recipes-devtools/binutils/{binutils-crosssdk_2.38.bb => >> >> binutils-crosssdk_2.39.bb} (100%) >> >> rename >> >> meta/recipes-devtools/binutils/binutils/{0006-don-t-let-the-distro-compiler-point-to-the-wrong-ins.patch >> >> => 0005-don-t-let-the-distro-compiler-point-to-the-wrong-ins.patch} (94%) >> >> rename >> >> meta/recipes-devtools/binutils/binutils/{0007-warn-for-uses-of-system-directories-when-cross-linki.patch >> >> => 0006-warn-for-uses-of-system-directories-when-cross-linki.patch} (91%) >> >> rename >> >> meta/recipes-devtools/binutils/binutils/{0008-fix-the-incorrect-assembling-for-ppc-wait-mnemonic.patch >> >> => 0007-fix-the-incorrect-assembling-for-ppc-wait-mnemonic.patch} (85%) >> >> rename >> >> meta/recipes-devtools/binutils/binutils/{0009-Use-libtool-2.4.patch => >> >> 0008-Use-libtool-2.4.patch} (95%) >> >> rename >> >> meta/recipes-devtools/binutils/binutils/{0010-Fix-rpath-in-libtool-when-sysroot-is-enabled.patch >> >> => 0009-Fix-rpath-in-libtool-when-sysroot-is-enabled.patch} (96%) >> >> rename >> >> meta/recipes-devtools/binutils/binutils/{0011-sync-with-OE-libtool-changes.patch >> >> => 0010-sync-with-OE-libtool-changes.patch} (97%) >> >> rename >> >> meta/recipes-devtools/binutils/binutils/{0012-Check-for-clang-before-checking-gcc-version.patch >> >> => 0011-Check-for-clang-before-checking-gcc-version.patch} (84%) >> >> rename >> >> meta/recipes-devtools/binutils/binutils/{0005-Only-generate-an-RPATH-entry-if-LD_RUN_PATH-is-not-e.patch >> >> => 0012-Only-generate-an-RPATH-entry-if-LD_RUN_PATH-is-not-e.patch} (70%) >> >> delete mode 100644 >> >> meta/recipes-devtools/binutils/binutils/0013-Avoid-as-info-race-condition.patch >> >> delete mode 100644 >> >> meta/recipes-devtools/binutils/binutils/0014-CVE-2019-1010204.patch >> >> rename meta/recipes-devtools/binutils/{binutils_2.38.bb => >> >> binutils_2.39.bb} (100%) >> > >> > >> > I'm seeing bunch of libtool erros with this applied, see: >> > http://errors.yoctoproject.org/Errors/Details/664878/ >> >> yes. gprofng is a new tool and I have forgotten to upgrade it to use >> libtool 2.4 since I have it disabed in my testing. I have done so now >> and sent a v3. Try it out.
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#169006): https://lists.openembedded.org/g/openembedded-core/message/169006 Mute This Topic: https://lists.openembedded.org/mt/92874030/21656 Group Owner: [email protected] Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
