From: Stefan Sonski <s.sonski@gmail.com>
To: Daniel Mack <daniel@zonque.org>
Cc: "Chris E. Rallis" <Chris.Rallis@ravenind.net>,
openembedded-devel <openembedded-devel@lists.openembedded.org>
Subject: Re: [meta-qt5][PATCH 2/2] qmake5_base: add OE_QMAKE_OBJCOPY from OBJCOPY
Date: Thu, 26 Oct 2017 15:29:54 +0200 [thread overview]
Message-ID: <CAGR_wht7JsOrTdV_e4gp9=hOcwMyn+pH1zWcCsw7xxx1t3hHZQ@mail.gmail.com> (raw)
In-Reply-To: <689fd8ec-97bf-2451-0c7a-1bc4606458e5@zonque.org>
On Thu, Oct 26, 2017 at 3:07 PM, Daniel Mack <daniel@zonque.org> 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?
>
>
> Thanks,
> Daniel
My patch has some weird dependency on nativesdk-qtbase, where when
the patch is added, qtPrepareTool is not found in some prf files and
the build fails.
Removing my patch, the build succeeds. What I don't get, is how
OBJCOPY depends on some qt5 internal prf scripts, regarding undefined
'qtPrepareTool.
The problem does not occure just using the ptest changes.
next prev parent reply other threads:[~2017-10-26 13:29 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-17 19:56 [meta-qt5][PATCH 1/2] nativesdk-qtbase Enable objcopy for qmake Stefan Sonski
2017-10-17 19:56 ` [meta-qt5][PATCH 2/2] qmake5_base: add OE_QMAKE_OBJCOPY from OBJCOPY Stefan Sonski
2017-10-20 22:54 ` Martin Jansa
2017-10-24 13:33 ` Daniel Mack
2017-10-26 12:55 ` Denys Dmytriyenko
2017-10-26 13:00 ` Stefan Sonski
2017-10-26 13:07 ` Daniel Mack
2017-10-26 13:29 ` Stefan Sonski [this message]
2017-10-26 13:36 ` Denys Dmytriyenko
2017-10-26 13:47 ` Stefan Sonski
2017-10-26 13:49 ` Denys Dmytriyenko
2017-10-27 5:53 ` Daniel Mack
2017-10-27 19:05 ` Martin Jansa
2017-11-01 18:57 ` Denys Dmytriyenko
2017-11-01 19:52 ` Martin Jansa
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAGR_wht7JsOrTdV_e4gp9=hOcwMyn+pH1zWcCsw7xxx1t3hHZQ@mail.gmail.com' \
--to=s.sonski@gmail.com \
--cc=Chris.Rallis@ravenind.net \
--cc=daniel@zonque.org \
--cc=openembedded-devel@lists.openembedded.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.