Re: [yocto] [bitbake] Failure to compile UltraJson, LMDB and Netifaces python modules recipes for Krogoth.

[Khem Raj]

On Mon, Dec 19, 2016 at 1:46 PM, Mateusz Orzoł <
mateusz.or...@3cityelectronics.com> wrote:

> Hi everyone,
>
> I am migrating my old Yocto image from kernel 3.8 to 4.1 on the Intel
> Quark based platform. After dealing with some SPI driver issues now I've
> encountered some strange bitbake behaviour. My web application requires
> UltraJson , LMDB and Netifaces modules. After running bitbake  I am getting
> a lot of undefined reference errors. In all three cases pretty similar.
> Exemplary log for python-ujson is here: http://pastebin.com/8ms9PgnY . It
> seems like the python environment wasn't linked properly but many other
> python recipes have no problem with compiling.
>
> The python-ujson recipe comes from here https://layers.openembedded.
> org/layerindex/recipe/49510/. In  previous distribution with kernel 3.8
> it was working without any problem.
>
> Have you got any idea what could be wrong or what should I check first?
>

​The error seems to have nothing to do with kernel version. Are you
upgrading the whole of yocto framework from one release to another ? and if
yes from which version to which new version.​



> Thank you for your help in advance,
>
> Mateusz
>
>
> --
> [image: 3City Electronics Sp. z o.o. Abrahama 1A/5.02-5.05 80-307 Gdańsk
> tel.: +48 58 765 01 48]
>
> --
> ___
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
>
>
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] [bitbake] Failure to compile UltraJson, LMDB and Netifaces python modules recipes for Krogoth.

[Mateusz Orzoł]

Hi everyone,

I am migrating my old Yocto image from kernel 3.8 to 4.1 on the Intel
Quark based platform. After dealing with some SPI driver issues now I've
encountered some strange bitbake behaviour. My web application requires
UltraJson , LMDB and Netifaces modules. After running bitbake  I am
getting a lot of undefined reference errors. In all three cases pretty
similar. Exemplary log for python-ujson is here:
http://pastebin.com/8ms9PgnY . It seems like the python environment
wasn't linked properly but many other python recipes have no problem
with compiling.

The python-ujson recipe comes from here
https://layers.openembedded.org/layerindex/recipe/49510/. In  previous
distribution with kernel 3.8 it was working without any problem.

Have you got any idea what could be wrong or what should I check first?

Thank you for your help in advance,

Mateusz


-- 
3City Electronics Sp. z o.o. Abrahama 1A/5.02-5.05 80-307 Gdańsk tel.:
+48 58 765 01 48
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] setting up autobuilder on local machine

[Mirza Krak]

2016-12-19 16:48 GMT+01:00 Bryan Evenson :
> Mirza,
>
>> -Original Message-
>> From: yocto-boun...@yoctoproject.org [mailto:yocto-
>> boun...@yoctoproject.org] On Behalf Of Mirza Krak
>> Sent: Monday, December 19, 2016 8:28 AM
>> To: Bill Randle 
>> Cc: yocto@yoctoproject.org
>> Subject: Re: [yocto] setting up autobuilder on local machine
>>
>> 2016-12-19 7:46 GMT+01:00 Mirza Krak :
>> > 2016-12-19 4:33 GMT+01:00 Bill Randle :
>> >> On Sun, Dec 18, 2016 at 8:25 AM, Paul Barker 
>> wrote:
>> >>> On Sun, 18 Dec 2016 15:46:19 +0100
>> >>> Mirza Krak  wrote:
>> >>>
>>  Hi.
>> 
>>  I have been looking in to the possibility to utilize yocto autobuilder
>>  for one of my own projects.
>> 
>>  But I am having some problems setting this up and hopefully someone
>>  here can provide some pointers.
>> 
>>  I did the "quickstart part":
>> 
>>  git clone git://git.yoctoproject.org/yocto-autobuilder
>>  cd yocto-autobuilder
>>  . ./yocto-autobuilder-setup
>>  yocto-start-autobuilder both
>> 
>>  Above succeeds without any issues. But now what? :)
>> 
>>  I went to https://localhost:8010. I tried to login using the
>>  information that is in the .htpasswd file but that did not work. Where
>>  are the credentials to login setup?
>> >>>
>> >>> You'll need to create the .htpasswd file yourself. I think the
>> >>> "htpasswd" tool can do this for you, I can't remember the exact
>> >>> commands I used to make mine though sorry.
>> >>>
>> 
>>  I also made an attempt to remove all un-wanted buildsets and now
>>  buildset-config contains (all other directories are removed)
>> 
>>  nightly-mender-rpi.conf  yoctoAB.conf
>> 
>>  Above is parsed correctly on start-up but build is never triggered. I
>>  probably removed to much :). Looking in to nigthly.conf it seem that
>>  is the one that trigger all other nightly builds?
>> 
>>  My fork can be found at [1].
>> 
>>  [1]. https://github.com/mirzak/yocto-autobuilder-mender-rpi
>> >>>
>> >>> This looks good, you just need to setup the scheduler with something
>> >>> like this in nightly-mender-rpi.conf:
>> >>>
>> >>> scheduler:
>> >>> [{'nightly-build':{'type':'Nightly','hour':23,'minute':0}}]
>> >>>
>> >>> You should only need a separate nightly.conf when you want that to
>> >>> trigger multiple builds.
>> >>>
>> >>> I've recently setup an autobuilder for meta-raspberrypi which I'll be
>> >>> publishing once I've got the last bits of setup done. If you're still
>> >>> struggling to get the nightly triggering working let me know and I'll
>> >>> put up the configurations I've used as a git repository.
>> >>
>> >> There is also additional helpful information on the Yocto Autobuilder
>> >> wiki page here:
>> >> https://wiki.yoctoproject.org/wiki/The_Yocto_Autobuilder. Some of the
>> >> information applies to the Yocto Project build cluster, but is still
>> >> applicable to local autobuilders. I followed the same instructions to
>> >> setup a local AB. Be sure to use the htpasswd command that's in the
>> >> autobuilder git tree (in one of the bin directories, as I recall),
>> >> rather than a native system one. The AB version defaults to the
>> >> shorter crypto scheme that buildbot requires.
>> >
>> > Thank you for your fast responses. Generating the htpasswd file my
>> > self did the trick. Now I can login. The full command was (as you
>> > suggested I used the one in autobuilder git repo under ./bin):
>> >
>> > ./htpasswd -b -c   > password>
>> >
>> > Forced a build of my configuration now and hoping for the best :).
>>
>> And it was not green all the way.
>>
>> I get an error that I do not get how to get around. The error message is:
>>
>> ERROR: Unable to parse
>> /home/mirzak/project/yocto-autobuilder/yocto-autobuilder-mender-
>> rpi/yocto-worker/nightly-mender-rpi/build/meta-mender/conf/layer.conf:
>> [Errno 2] file /home/mirzak/project/yocto-autobuilder/yocto-autobuilder-
>> mender-rpi/yocto-worker/nightly-mender-rpi/build/meta-
>> mender/conf/layer.conf
>> not found
>>
>> The error message I understand. But I do not understand why it adds
>> meta-mender to bblayers files. I did not tell it to do that, because
>> meta-mender contains layers that I want to include. Similar to
>> meta-openembedded (which is also added to bblayers).
>>
>> Here is the bblayers.conf also for reference:
>> mirzak@debian:~/project/yocto-autobuilder/yocto-autobuilder-mender-
>> rpi/yocto-worker/nightly-mender-rpi/build/build/conf$
>> cat bblayers.conf
>> POKY_BBLAYERS_CONF_VERSION =  "2"
>> BBPATH = "${TOPDIR}"
>> BBFILES ?=""
>> BBLAYERS += " \
>> /home/mirzak/project/yocto-autobuilder/yocto-autobuilder-mender-
>> rpi/yocto-worker/nightly-mender-rpi/build/meta
>> \
>> 

Re: [yocto] live" image: iso and ext4 artifacts

[Takashi Matsuzawa]

Hello.


Thanks it worked for .iso files.


I have found that this really is a save for build time also.


From: Jussi Kukkonen 
Sent: Friday, December 16, 2016 6:22 PM
To: Takashi Matsuzawa
Cc: yocto@yoctoproject.org
Subject: Re: [yocto] live" image: iso and ext4 artifacts

On 15 December 2016 at 09:30, Takashi Matsuzawa 
> wrote:
>
> Hello Yocto.
>
> I am trying x86-64 BSP image (based on jethro version).
> It has following root filesystem type, and it generats .hddimg file that 
> I am using.
>
> > IMAGE_FSTYPES = "live"
>
> The issue is that in addition to .hddimg, it produces following image 
> files and it sometimes cause lack of disk space error on my build PC.
>
> > 2422489088 -intel-corei7-64-20161215004421.hddimg
> > 2402287616 -intel-corei7-64-20161215004421.iso
> > 2368578560 -intel-corei7-64-20161215004421.rootfs.ext4
>
> I do not need xxx.iso and .ext4 files as final output, though I 
> understand that .ext4 file may have been used to produce xxx.hddimg file.

I think you should be able to define NOISO=1.

The rootfs is indeed used to produce the actual images, you could delete it 
afterwards... but before you spend valuable time writing shell scripts, 
consider a new SSD: 500GB is probably less than 150EUR by now.

Jussi
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] setting up autobuilder on local machine

[Bryan Evenson]

Mirza,

> -Original Message-
> From: yocto-boun...@yoctoproject.org [mailto:yocto-
> boun...@yoctoproject.org] On Behalf Of Mirza Krak
> Sent: Monday, December 19, 2016 8:28 AM
> To: Bill Randle 
> Cc: yocto@yoctoproject.org
> Subject: Re: [yocto] setting up autobuilder on local machine
> 
> 2016-12-19 7:46 GMT+01:00 Mirza Krak :
> > 2016-12-19 4:33 GMT+01:00 Bill Randle :
> >> On Sun, Dec 18, 2016 at 8:25 AM, Paul Barker 
> wrote:
> >>> On Sun, 18 Dec 2016 15:46:19 +0100
> >>> Mirza Krak  wrote:
> >>>
>  Hi.
> 
>  I have been looking in to the possibility to utilize yocto autobuilder
>  for one of my own projects.
> 
>  But I am having some problems setting this up and hopefully someone
>  here can provide some pointers.
> 
>  I did the "quickstart part":
> 
>  git clone git://git.yoctoproject.org/yocto-autobuilder
>  cd yocto-autobuilder
>  . ./yocto-autobuilder-setup
>  yocto-start-autobuilder both
> 
>  Above succeeds without any issues. But now what? :)
> 
>  I went to https://localhost:8010. I tried to login using the
>  information that is in the .htpasswd file but that did not work. Where
>  are the credentials to login setup?
> >>>
> >>> You'll need to create the .htpasswd file yourself. I think the
> >>> "htpasswd" tool can do this for you, I can't remember the exact
> >>> commands I used to make mine though sorry.
> >>>
> 
>  I also made an attempt to remove all un-wanted buildsets and now
>  buildset-config contains (all other directories are removed)
> 
>  nightly-mender-rpi.conf  yoctoAB.conf
> 
>  Above is parsed correctly on start-up but build is never triggered. I
>  probably removed to much :). Looking in to nigthly.conf it seem that
>  is the one that trigger all other nightly builds?
> 
>  My fork can be found at [1].
> 
>  [1]. https://github.com/mirzak/yocto-autobuilder-mender-rpi
> >>>
> >>> This looks good, you just need to setup the scheduler with something
> >>> like this in nightly-mender-rpi.conf:
> >>>
> >>> scheduler:
> >>> [{'nightly-build':{'type':'Nightly','hour':23,'minute':0}}]
> >>>
> >>> You should only need a separate nightly.conf when you want that to
> >>> trigger multiple builds.
> >>>
> >>> I've recently setup an autobuilder for meta-raspberrypi which I'll be
> >>> publishing once I've got the last bits of setup done. If you're still
> >>> struggling to get the nightly triggering working let me know and I'll
> >>> put up the configurations I've used as a git repository.
> >>
> >> There is also additional helpful information on the Yocto Autobuilder
> >> wiki page here:
> >> https://wiki.yoctoproject.org/wiki/The_Yocto_Autobuilder. Some of the
> >> information applies to the Yocto Project build cluster, but is still
> >> applicable to local autobuilders. I followed the same instructions to
> >> setup a local AB. Be sure to use the htpasswd command that's in the
> >> autobuilder git tree (in one of the bin directories, as I recall),
> >> rather than a native system one. The AB version defaults to the
> >> shorter crypto scheme that buildbot requires.
> >
> > Thank you for your fast responses. Generating the htpasswd file my
> > self did the trick. Now I can login. The full command was (as you
> > suggested I used the one in autobuilder git repo under ./bin):
> >
> > ./htpasswd -b -cpassword>
> >
> > Forced a build of my configuration now and hoping for the best :).
> 
> And it was not green all the way.
> 
> I get an error that I do not get how to get around. The error message is:
> 
> ERROR: Unable to parse
> /home/mirzak/project/yocto-autobuilder/yocto-autobuilder-mender-
> rpi/yocto-worker/nightly-mender-rpi/build/meta-mender/conf/layer.conf:
> [Errno 2] file /home/mirzak/project/yocto-autobuilder/yocto-autobuilder-
> mender-rpi/yocto-worker/nightly-mender-rpi/build/meta-
> mender/conf/layer.conf
> not found
> 
> The error message I understand. But I do not understand why it adds
> meta-mender to bblayers files. I did not tell it to do that, because
> meta-mender contains layers that I want to include. Similar to
> meta-openembedded (which is also added to bblayers).
> 
> Here is the bblayers.conf also for reference:
> mirzak@debian:~/project/yocto-autobuilder/yocto-autobuilder-mender-
> rpi/yocto-worker/nightly-mender-rpi/build/build/conf$
> cat bblayers.conf
> POKY_BBLAYERS_CONF_VERSION =  "2"
> BBPATH = "${TOPDIR}"
> BBFILES ?=""
> BBLAYERS += " \
> /home/mirzak/project/yocto-autobuilder/yocto-autobuilder-mender-
> rpi/yocto-worker/nightly-mender-rpi/build/meta
> \
> /home/mirzak/project/yocto-autobuilder/yocto-autobuilder-mender-
> rpi/yocto-worker/nightly-mender-rpi/build/meta-poky
> \
> /home/mirzak/project/yocto-autobuilder/yocto-autobuilder-mender-
> 

Re: [yocto] setting up autobuilder on local machine

[Mirza Krak]

2016-12-19 15:57 GMT+01:00 Jussi Kukkonen :
> On 19 December 2016 at 15:28, Mirza Krak  wrote:
>>
>> > Thank you for your fast responses. Generating the htpasswd file my
>> > self did the trick. Now I can login. The full command was (as you
>> > suggested I used the one in autobuilder git repo under ./bin):
>> >
>> > ./htpasswd -b -c   > > password>
>> >
>> > Forced a build of my configuration now and hoping for the best :).
>>
>> And it was not green all the way.
>>
>> I get an error that I do not get how to get around. The error message is:
>>
>> ERROR: Unable to parse
>>
>> /home/mirzak/project/yocto-autobuilder/yocto-autobuilder-mender-rpi/yocto-worker/nightly-mender-rpi/build/meta-mender/conf/layer.conf:
>> [Errno 2] file
>> /home/mirzak/project/yocto-autobuilder/yocto-autobuilder-mender-rpi/yocto-worker/nightly-mender-rpi/build/meta-mender/conf/layer.conf
>> not found
>>
>> The error message I understand. But I do not understand why it adds
>> meta-mender to bblayers files. I did not tell it to do that, because
>> meta-mender contains layers that I want to include. Similar to
>> meta-openembedded (which is also added to bblayers).
>>
>
> I'm not an expert but your nightly-mender-rpi.conf contains this:
> 'layerdirs': ['meta-yocto', 'meta-raspberrypi',
> 'meta-mender/meta-mender-core', 'meta-mender/meta-mender-raspberrypi',
> 'oe-meta-go', 'meta-openembedded/meta-oe']

That is correct. I add following:

   meta-mender/meta-mender-raspberrypi
   meta-mender/meta-mender-core

And they are added to the bblayers.conf correctly.

But I do not add "meta-mender" which is present in my bblayers.conf
and is the cause of my error message. It seems to me like it is picked
up from the "repos" section and hence the "magic" :)

Best Regards
Mirza
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] setting up autobuilder on local machine

[Jussi Kukkonen]

On 19 December 2016 at 15:28, Mirza Krak  wrote:
>
> > Thank you for your fast responses. Generating the htpasswd file my
> > self did the trick. Now I can login. The full command was (as you
> > suggested I used the one in autobuilder git repo under ./bin):
> >
> > ./htpasswd -b -c   
> >
> > Forced a build of my configuration now and hoping for the best :).
>
> And it was not green all the way.
>
> I get an error that I do not get how to get around. The error message is:
>
> ERROR: Unable to parse
>
/home/mirzak/project/yocto-autobuilder/yocto-autobuilder-mender-rpi/yocto-worker/nightly-mender-rpi/build/meta-mender/conf/layer.conf:
> [Errno 2] file
/home/mirzak/project/yocto-autobuilder/yocto-autobuilder-mender-rpi/yocto-worker/nightly-mender-rpi/build/meta-mender/conf/layer.conf
> not found
>
> The error message I understand. But I do not understand why it adds
> meta-mender to bblayers files. I did not tell it to do that, because
> meta-mender contains layers that I want to include. Similar to
> meta-openembedded (which is also added to bblayers).
>

I'm not an expert but your nightly-mender-rpi.conf contains this:
'layerdirs': ['meta-yocto', 'meta-raspberrypi',
'meta-mender/meta-mender-core', 'meta-mender/meta-mender-raspberrypi',
'oe-meta-go', 'meta-openembedded/meta-oe']

Jussi
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Build one package from a split package recipe

[Thomas Thorne]

?  Now when I fire a bitbake command like "bitbake test" all the packages 
listed into the recipe get build. But sometime I need to build only one package 
say test1.

?

?  How that can be achieved as when I tried "bitbake test1" its reports below 
error

?  ERROR: Nothing PROVIDES test1'

I think you would need to define a recipe for each target you wanted to build.  
You could still have a top level recipe that depended on them all and caused 
them all to be generated.

Thomas A. F. Thorne  Software Engineer  
Net2Edge

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Fwd: error while compiling hello_2.7.bb

[Alexander Kanavin]

On 12/19/2016 02:42 PM, praveen vattipalli wrote:

I have hello_2.7.bb  file which contains as below
vim hello_2.7.bb 
DESCRIPTION = "GNU Helloworld application"
SECTION = "test"
LICENSE = "BSD"

LIC_FILES_CHKSUM =
"file://${COMMON_LICENSE_DIR}/BSD;md5=3775480a712fc46a69647678acb234cb"
SRC_DIR ?=
"/home/rajesh/poky-krogoth-15.0.2/meta/recipes-support/hello/hello_2.7"
SRC_URI = "file://${SRC_DIR}"

S = "${SRC_DIR}"

do_compile (){
make prog
}


You probably need to use externalsrc facility:
http://www.yoctoproject.org/docs/2.2/dev-manual/dev-manual.html#building-software-from-an-external-source

Alex
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] setting up autobuilder on local machine

[Mirza Krak]

2016-12-19 7:46 GMT+01:00 Mirza Krak :
> 2016-12-19 4:33 GMT+01:00 Bill Randle :
>> On Sun, Dec 18, 2016 at 8:25 AM, Paul Barker  wrote:
>>> On Sun, 18 Dec 2016 15:46:19 +0100
>>> Mirza Krak  wrote:
>>>
 Hi.

 I have been looking in to the possibility to utilize yocto autobuilder
 for one of my own projects.

 But I am having some problems setting this up and hopefully someone
 here can provide some pointers.

 I did the "quickstart part":

 git clone git://git.yoctoproject.org/yocto-autobuilder
 cd yocto-autobuilder
 . ./yocto-autobuilder-setup
 yocto-start-autobuilder both

 Above succeeds without any issues. But now what? :)

 I went to https://localhost:8010. I tried to login using the
 information that is in the .htpasswd file but that did not work. Where
 are the credentials to login setup?
>>>
>>> You'll need to create the .htpasswd file yourself. I think the
>>> "htpasswd" tool can do this for you, I can't remember the exact
>>> commands I used to make mine though sorry.
>>>

 I also made an attempt to remove all un-wanted buildsets and now
 buildset-config contains (all other directories are removed)

 nightly-mender-rpi.conf  yoctoAB.conf

 Above is parsed correctly on start-up but build is never triggered. I
 probably removed to much :). Looking in to nigthly.conf it seem that
 is the one that trigger all other nightly builds?

 My fork can be found at [1].

 [1]. https://github.com/mirzak/yocto-autobuilder-mender-rpi
>>>
>>> This looks good, you just need to setup the scheduler with something
>>> like this in nightly-mender-rpi.conf:
>>>
>>> scheduler:
>>> [{'nightly-build':{'type':'Nightly','hour':23,'minute':0}}]
>>>
>>> You should only need a separate nightly.conf when you want that to
>>> trigger multiple builds.
>>>
>>> I've recently setup an autobuilder for meta-raspberrypi which I'll be
>>> publishing once I've got the last bits of setup done. If you're still
>>> struggling to get the nightly triggering working let me know and I'll
>>> put up the configurations I've used as a git repository.
>>
>> There is also additional helpful information on the Yocto Autobuilder
>> wiki page here:
>> https://wiki.yoctoproject.org/wiki/The_Yocto_Autobuilder. Some of the
>> information applies to the Yocto Project build cluster, but is still
>> applicable to local autobuilders. I followed the same instructions to
>> setup a local AB. Be sure to use the htpasswd command that's in the
>> autobuilder git tree (in one of the bin directories, as I recall),
>> rather than a native system one. The AB version defaults to the
>> shorter crypto scheme that buildbot requires.
>
> Thank you for your fast responses. Generating the htpasswd file my
> self did the trick. Now I can login. The full command was (as you
> suggested I used the one in autobuilder git repo under ./bin):
>
> ./htpasswd -b -c   
>
> Forced a build of my configuration now and hoping for the best :).

And it was not green all the way.

I get an error that I do not get how to get around. The error message is:

ERROR: Unable to parse
/home/mirzak/project/yocto-autobuilder/yocto-autobuilder-mender-rpi/yocto-worker/nightly-mender-rpi/build/meta-mender/conf/layer.conf:
[Errno 2] file 
/home/mirzak/project/yocto-autobuilder/yocto-autobuilder-mender-rpi/yocto-worker/nightly-mender-rpi/build/meta-mender/conf/layer.conf
not found

The error message I understand. But I do not understand why it adds
meta-mender to bblayers files. I did not tell it to do that, because
meta-mender contains layers that I want to include. Similar to
meta-openembedded (which is also added to bblayers).

Here is the bblayers.conf also for reference:
mirzak@debian:~/project/yocto-autobuilder/yocto-autobuilder-mender-rpi/yocto-worker/nightly-mender-rpi/build/build/conf$
cat bblayers.conf
POKY_BBLAYERS_CONF_VERSION =  "2"
BBPATH = "${TOPDIR}"
BBFILES ?=""
BBLAYERS += " \
/home/mirzak/project/yocto-autobuilder/yocto-autobuilder-mender-rpi/yocto-worker/nightly-mender-rpi/build/meta
\
/home/mirzak/project/yocto-autobuilder/yocto-autobuilder-mender-rpi/yocto-worker/nightly-mender-rpi/build/meta-poky
\
/home/mirzak/project/yocto-autobuilder/yocto-autobuilder-mender-rpi/yocto-worker/nightly-mender-rpi/build/meta-yocto-bsp
\
/home/mirzak/project/yocto-autobuilder/yocto-autobuilder-mender-rpi/yocto-worker/nightly-mender-rpi/build/meta-mender
\
/home/mirzak/project/yocto-autobuilder/yocto-autobuilder-mender-rpi/yocto-worker/nightly-mender-rpi/build/oe-meta-go
\
/home/mirzak/project/yocto-autobuilder/yocto-autobuilder-mender-rpi/yocto-worker/nightly-mender-rpi/build/meta-raspberrypi
\
/home/mirzak/project/yocto-autobuilder/yocto-autobuilder-mender-rpi/yocto-worker/nightly-mender-rpi/build/meta-openembedded
\

[yocto] Fwd: error while compiling hello_2.7.bb

[praveen vattipalli]

Hi All,
I have hello_2.7.bb file which contains as below
vim hello_2.7.bb
DESCRIPTION = "GNU Helloworld application"
SECTION = "test"
LICENSE = "BSD"

LIC_FILES_CHKSUM = "file://${COMMON_LICENSE_DIR}/BSD;md5=
3775480a712fc46a69647678acb234cb"
SRC_DIR ?= "/home/rajesh/poky-krogoth-15.0.2/meta/recipes-support/
hello/hello_2.7"
SRC_URI = "file://${SRC_DIR}"

S = "${SRC_DIR}"

do_compile (){
make prog
}

do_install(){
install -d ${D}${bindir}
install -m 0755 ${S}/hello  ${D}${bindir}
}

in hello_2.7 folder i have two files hello.c and Makefile
vim hello.c
#include
int main()
{
printf("hello YOCTO POKY\n");
return 0;
}

Vim Makefile
prog:
gcc -o hello hello.c

Now when i am building "bitbake hello", I am  getting below error in
poky-krogoth-15.0.2.
The same hello_2.7.bb  is compiling fine without any error in
"poky-dora-10.0.0".
The strange thing i observe in poky-krogoth-15.0.2. is that hello.c and
Makefile are getting erased in hello_2.7 dir.
Am i missing some thing in poky-krogoth-15.0.2? Please help.

Error msg:
ERROR: hello-2.7-r0 do_compile: Function failed: do_compile (log file is
located at /home/rajesh/poky-krogoth-15.0.2/build/tmp/work/cortexa8hf-
neon-poky-linux-gnueabi/hello/2.7-r0/temp/log.do_compile.13763)
ERROR: Logfile of failure stored in: /home/rajesh/poky-krogoth-15.
0.2/build/tmp/work/cortexa8hf-neon-poky-linux-gnueabi/hello/
2.7-r0/temp/log.do_compile.13763
Log data follows:
| DEBUG: Executing shell function do_compile
| make: *** No rule to make target 'prog'.  Stop.
| WARNING: exit code 2 from a shell command.
| ERROR: Function failed: do_compile (log file is located at
/home/rajesh/poky-krogoth-15.0.2/build/tmp/work/cortexa8hf-
neon-poky-linux-gnueabi/hello/2.7-r0/temp/log.do_compile.13763)
ERROR: Task 6 (/home/rajesh/poky-krogoth-15.0.2/meta/recipes-support/hello/
hello_2.7.bb, do_compile) failed with exit code '1'
NOTE: Tasks Summary: Attempted 351 tasks of which 345 didn't need to be
rerun and 1 failed.
No currently running tasks (351 of 358)

Summary: 1 task failed:
  /home/rajesh/poky-krogoth-15.0.2/meta/recipes-support/hello/hello_2.7.bb,
do_compile
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Build one package from a split package recipe

[Burton, Ross]

On 19 December 2016 at 11:24, Bipnesh, Abhinav (Abhinav) <
abhinavbipn...@avaya.com> wrote:

> Now when I fire a bitbake command like “bitbake test” all the packages
> listed into the recipe get build. But sometime I need to build only one
> package say test1.
>
>
>
> How that can be achieved as when I tried “bitbake test1” its reports below
> error
>
> ERROR: Nothing PROVIDES test1'
>
>
You can't do this.  If you have a source that is sufficiently large and
slow to build that it this is a problem, considering splitting the recipes
up.

Ross
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] Build one package from a split package recipe

[Bipnesh, Abhinav (Abhinav)]

Hi,

I have an recipe which built multiple package. Below is the contents of the 
recipe

Test.bb

PACKAGES = "test1 test2 test3 test4 test5"

do_install () {
}



Now when I fire a bitbake command like "bitbake test" all the packages listed 
into the recipe get build. But sometime I need to build only one package say 
test1.

How that can be achieved as when I tried "bitbake test1" its reports below error
ERROR: Nothing PROVIDES test1'


Thanks,
Abhinav
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] "make html" for yocto-docs fails, "Unknown option -customization.xsl"

[Robert P. J. Day]

On Mon, 19 Dec 2016, Robert P. J. Day wrote:

>
>   been a while since i've built the docs from scratch, and now:
>
> $ make html
>
>  Building
>
> cd ; xsltproc  -o .html -customization.xsl .xml; cd ..
> Unknown option -customization.xsl
> Usage: xsltproc [options] stylesheet file [file ...]
>Options:
>... snip ...

   gh ... never mind, i forgot that i *need* to identify a manual,
it won't just build them all by default. apologies.

rday

-- 


Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca

Twitter:   http://twitter.com/rpjday
LinkedIn:   http://ca.linkedin.com/in/rpjday


-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] "make html" for yocto-docs fails, "Unknown option -customization.xsl"

[Robert P. J. Day]

  been a while since i've built the docs from scratch, and now:

$ make html

 Building

cd ; xsltproc  -o .html -customization.xsl .xml; cd ..
Unknown option -customization.xsl
Usage: xsltproc [options] stylesheet file [file ...]
   Options:
   ... snip ...

  i'll take a quick look at how xsltproc has changed lately unless
someone else already knows what the fix is.

rday

-- 


Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca

Twitter:   http://twitter.com/rpjday
LinkedIn:   http://ca.linkedin.com/in/rpjday


-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] NFS rootfs: mount: only root can mount proc on /proc

[John Rama]

Thanks everyone for the feedback.
I got #3 would be the best way. 

Kind Regards,
John Rama

On 2016/12/16 0:20, Daniel. wrote:
> 2016-12-15 12:09 GMT-02:00 Anders Darander :
>> Hi,
>>
>> * John Rama  [161215 02:58]:
>>
>>> The ideas I can come up with are followings, but those of them are not 
>>> perfect..
>>> 1. Run the bitbake as root account
>>>   - would not run as root since the all of generated files are root 
>>> permission even for the log files.
>>
>> Never do this. You've got no idea what bitbake might do to your
>> computer...
>>
>>
>>> 2. Change UID and GID whenever generating new image
>>>   - I guess next build would fall into the trouble because of the owner 
>>> change.
>>
>> Yes, that'll get you problems later on.
>>
>>> 3. Untar the tar ball under  
>>> {YOCTO_BUILD_DIR}//tmp//deploy/image/{TARGET}/*rootfs.tar.bz2 to  the 
>>> export dir
>>>   - takes additional time.. Not good.
>>
>> This is the right way to do it.
>>
>> If it takes to much time, create a script that runs bitbake and then
>> untars the rootfs.
> 
> I do this all the time and have faced no problems regarding exploding
> the tar. You may want to generate a .tar instead of a .tar.bz2. This
> will safe the CPU from decrompressing so it should be faster...
> 
> Regards,
>>
>> Cheers,
>> Anders
>>
>> --
>> Anders Darander, Senior System Architect
>> ChargeStorm AB / eStorm AB
>> --
>> ___
>> yocto mailing list
>> yocto@yoctoproject.org
>> https://lists.yoctoproject.org/listinfo/yocto
> 
> 
> 

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto