[oe] [meta-qt5][PATCH 2/2] qmake5_base: add OE_QMAKE_OBJCOPY from OBJCOPY

[Martin Jansa]

I've dropped the "qmake5_base: add OE_QMAKE_OBJCOPY from OBJCOPY"
change, so now I have only following 3 included:


== Tested changes (not included in master yet) - meta-qt5 ==
latest upstream commit:
2c3ef00 qt5: add missing commercial license
not included in master yet:
bbb3044 meta-qt5: Update to 5.9.2 release
8fd20e8 nativesdk-qtbase Enable objcopy for qmake
60329bc qt5-ptest.inc: fix qtxmlpatterns:do_install_ptest out-of-order call


and it still fails the same as shown in:

http://errors.yoctoproject.org/Errors/Build/47776/

I'm going to drop the 2nd objcopy change and retrigger the builds.

On Fri, Oct 27, 2017 at 7:53 AM, Daniel Mack <daniel at zonque.org> wrote:

> On Thursday, October 26, 2017 03:36 PM, Denys Dmytriyenko wrote:
> > On Thu, Oct 26, 2017 at 03:07:36PM +0200, Daniel Mack wrote:
> >> On Thursday, October 26, 2017 02:55 PM, Denys Dmytriyenko wrote:
> >>> On Tue, Oct 24, 2017 at 03:33:10PM +0200, Daniel Mack wrote:
> >>>> Hi,
> >>>>
> >>>> On Saturday, October 21, 2017 12:54 AM, Martin Jansa wrote:
> >>>>> Either this or the ptest change seems to cause:
> >>>>> http://errors.yoctoproject.org/Errors/Details/157417/
> >>>>
> >>>> FTR, I see the same error locally. Reverting both 8fd20e8b1
> >>>> ("nativesdk-qtbase Enable objcopy for qmake") and 5ec6b97a8
> >>>> ("qmake5_base: add OE_QMAKE_OBJCOPY from OBJCOPY") in the master-next
> >>>> branch of meta-qt5 fixes things for me.
> >>>
> >>> Have you tried bisecting by any chance?
> >>
> >> bisect what exactly? If I take your patch out of my stack, qtbase
> >> builds. If I don't it doesn't. Can I provide more information somehow?
> >
> > That's not what you said above - we are trying to figure out which of
> the 2
> > (*two*) patches causes the breakage, hence the question about
> bisecting...
>
> Ah, sorry, my bad.
>
> Only reverting "qmake5_base: add OE_QMAKE_OBJCOPY from OBJCOPY" fixes a
> build that does not have a native sdk target. I assume the 2nd patch
> would break a native sdk, but I can't tell.
>
> I can provide full build logs if you want.
>
>
> Thanks,
> Daniel
>