>> yes thats normal when package is re-used from sstate-cache
Many thanks Khem. Got it, so the IPK packages were built early is OK.
I did a clean all and redo the bitbake, all packages, images were rebuilt.
Thanks again,
—Dinh
>
>> On Oct 5, 2016, at 11:43 AM, Dinh Nguyen (dinhn)
> On Oct 5, 2016, at 11:43 AM, Dinh Nguyen (dinhn) wrote:
>
>
>
>>> then it is just going to reuse the build artifacts from last builds and not
>>> checkout the sources etc.
>>> all those tasks will be skipped.
>
>>> why are looking for sources in a build tree ?
>
>
> Not
>> then it is just going to reuse the build artifacts from last builds and not
>> checkout the sources etc.
>> all those tasks will be skipped.
>> why are looking for sources in a build tree ?
Not only source under
.. yp/tmp/work/core2-64-poky-linux/c-mlib/1.1-r0/git
But other data such
> On Oct 5, 2016, at 11:18 AM, Dinh Nguyen (dinhn) wrote:
>
>>> Are the files present in the image/packages? Maybe it is just the
>>> bitbake cache skipping doing work it already did last time.
>
> If I don’t do the bitbake clean, and just do bitbake again, then yes.
>
>
>
>> Are the files present in the image/packages? Maybe it is just the
>> bitbake cache skipping doing work it already did last time.
If I don’t do the bitbake clean, and just do bitbake again, then yes.
But if I do “bitbake -c clean c-mlib” and bitbake again, the is where the
problem.
Thanks Khem
>> I guess its getting renamed as per debian package renaming rules. Just add
>> ALLOW_EMPTY_${PN} = "1"
I added ALLOW_EMPTY_${PN} = “1”
And encountered the same issue as specified in previous mail. For the very
first time after adding it, everything went well, including the -dev,
>> Is that doing a compile in the install target?
Yes Len. Compile was done and there is no issue there.
Thanks,
—Dinh
On 10/5/16, 9:28 AM, "Lennart Sorensen" wrote:
>On Wed, Oct 05, 2016 at 04:10:01PM +, Dinh Nguyen (dinhn) wrote:
>> >>> I wonder
On Wed, Oct 5, 2016 at 9:06 AM, Dinh Nguyen (dinhn) wrote:
> Many thanks Paul. Your help is greatly appreciated.
>
> 1. >>> Like the other responder I would suggest you not set PACKAGES
>
> Yes, I did not set the PACKAGES, so -dev, -dbg and main packages were built
> as shown
On Wed, Oct 05, 2016 at 04:06:25PM +, Dinh Nguyen (dinhn) wrote:
> Many thanks Paul. Your help is greatly appreciated.
>
> 1. >>> Like the other responder I would suggest you not set PACKAGES
>
> Yes, I did not set the PACKAGES, so -dev, -dbg and main packages were built
> as shown below:
>
On Wed, Oct 05, 2016 at 04:10:01PM +, Dinh Nguyen (dinhn) wrote:
> >>> I wonder why do we want to override default PACKAGES here. If we can
> >>> leave that alone things would work out on its own.
>
> I did remove the PACKAGES setting in my .bb — so all default packages were
> built. But
>>> I wonder why do we want to override default PACKAGES here. If we can leave
>>> that alone things would work out on its own.
I did remove the PACKAGES setting in my .bb — so all default packages were
built. But still having some other issue as stated in other emails.
Thanks Khem.
—Dinh
Many thanks Paul. Your help is greatly appreciated.
1. >>> Like the other responder I would suggest you not set PACKAGES
Yes, I did not set the PACKAGES, so -dev, -dbg and main packages were built as
shown below:
dinhn@rs-bldsrv:/media/raghuram/data/dinhn/ioxDevLatest/ioxsdk/yp$ find
I wonder why do we want to override default PACKAGES here. If we can leave
that alone things would work out on its own.
On Tue, Oct 4, 2016 at 11:55 PM, Paul Eggleton
wrote:
> On Wed, 05 Oct 2016 05:12:27 Dinh Nguyen wrote:
>> Thanks much Paul.
>>
>> PACKAGES
On Wed, 05 Oct 2016 05:12:27 Dinh Nguyen wrote:
> Thanks much Paul.
>
> PACKAGES = "${PN}" should work
>
> It solved the early error “ c-mlib listed in PACKAGES multiple times, this
> leads to packaging errors” — Thanks again.
>
>
> But running into other issue. Below is my do_install
>
Thank you Len.
If I specified PACKAGES = “${PN}” as mentioned early, it only built the main
package.
As you suggested, I removed that line from my c-mlib.bb, it then built the
main, -dev and -dbg packages as specified in the bitbake.conf - thanks you...
Thanks much Paul.
PACKAGES = "${PN}" should work
It solved the early error “ c-mlib listed in PACKAGES multiple times, this
leads to packaging errors” — Thanks again.
But running into other issue. Below is my do_install
do_install () {
oe_runmake all
install -d
On Tue, Oct 04, 2016 at 07:47:58PM +, Dinh Nguyen (dinhn) wrote:
>
> Hi Paul, thanks much for prompt response.
>
> The c-mlib.bb below has the packages var as
> PACKAGES =+ "${PN}” I also tried PACKAGES = "${PN}”
Don't do that.
In bitbake.conf you have:
PACKAGES = "${PN}-dbg
On Tue, 04 Oct 2016 19:47:58 Dinh Nguyen wrote:
> The c-mlib.bb below has the packages var as
> PACKAGES =+ "${PN}” I also tried PACKAGES = "${PN}”
PACKAGES = "${PN}" should work (or use bitbake -e recipename | less, search
for ^PACKAGES= (with /) and look through the history to see why not).
Hi Paul, thanks much for prompt response.
The c-mlib.bb below has the packages var as
PACKAGES =+ "${PN}” I also tried PACKAGES = "${PN}”
The packages were built successful indeed, but the ERROR: QA Issue ...
Any recommendation to change the above PACKAGES variable in the bb?
SUMMARY =
Hi Dinh,
On Tue, 04 Oct 2016 16:07:59 Dinh Nguyen wrote:
> >>> ERROR: QA Issue: c-mlib is listed in PACKAGES multiple times, this leads
> >>> to packaging errors. [packages-list]
> Summary: There was 1 ERROR
> >>> message shown, returning a non-zero exit code.
>
> I got the above ERROR because
Hi folks,
>>> ERROR: QA Issue: c-mlib is listed in PACKAGES multiple times, this leads to
>>> packaging errors. [packages-list]
>>> Summary: There was 1 ERROR message shown, returning a non-zero exit code.
I got the above ERROR because my c-mlib_1.0-r0_core2-64.ipk and other packages
were
21 matches
Mail list logo