Re: [yocto] setting up autobuilder on local machine

2016-12-18 Thread 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 :).

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

Re: [yocto] setting up autobuilder on local machine

2016-12-18 Thread 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.

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

Re: [yocto] libssp_nonshared.a not present in native SDK.

2016-12-18 Thread Paul Eggleton 
Hi Rafael,

Looking at this a bit more closely I think the problem here is that within the 
SDK this RRECOMMENDS doesn't actually come into effect. In the SDK, gcc is in 
the host part, but you want the libssp library for the target which is in the 
target part of the SDK; RRECOMMENDS can't cross between those. On the target 
device it's simpler - both packages are in the same "namespace".

The only way I can see to fix this is to add libssp and libssp-dev to 
packagegroup-core-standalone-sdk-target so that it's explicitly brought into 
the SDK. I'll send a patch to do that.

Cheers,
Paul

On Thu, 15 Dec 2016 14:26:52 Rafael Gago Castano wrote:
> Sorry for the late reply, I had higher priority tasks meanwhile.
> 
> 
> Grepping libssp on the sdks ".target.manifest" file doesn't yield any
> result. libssp.so.0.0.0 is present on the toolchain.
> 
> When running bitbake gcc -e is see that this is the last match of
> RRECOMMENDS_gcc:
> 
> RRECOMMENDS_gcc=" libssp libssp-dev "
> 
> 
> From: Paul Eggleton 
> Sent: Monday, December 12, 2016 5:14 AM
> To: Rafael Gago Castano
> Cc: yocto@yoctoproject.org
> Subject: Re: [yocto] libssp_nonshared.a not present in native SDK.
> 
> On Fri, 09 Dec 2016 09:24:41 Rafael Gago Castano wrote:
> > Hello again.
> > 
> > 
> > I tried to fix this in my layers by adding a
> > "recipes-devtools/gcc_5.3.bbappend" file to containing the additions that
> > you did to poky on...
> > 
> > 
> > http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=1c0fc7fcf7772ef8
> > 77 4f623126050972f526fe83
> > 
> > 
> > ...as I think that adding these dependencies to gcc is the right thing.
> > 
> > 
> > Running "bitbake gcc -e" shows the next:
> > 
> > 
> > # $RRECOMMENDS_gcc
> > #   rename from RRECOMMENDS_${PN} data.py:169 [expandKeys]
> > # " libssp libssp-dev "
> > RRECOMMENDS_gcc=" libssp libssp-dev "
> > 
> > So the recipe is at least processed.
> > 
> > The problem is that "libssp_nonshared.a" is still not present on the SDK.
> > It may happen that this is still happening in poky.
> 
> Hmm, I just tried building an SDK (bitbake -c populate_sdk
> core-image-minimal) with master and it definitely includes
> libssp_nonshared.a. Does the target manifest for your SDK indicate
> libssp-dev is included?
> 
> Cheers,
> Paul
> 
> --
> 
> Paul Eggleton
> Intel Open Source Technology Centre

-- 

Paul Eggleton
Intel Open Source Technology Centre
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] [PATCH][yocto-docs] Couple aesthetic fixes for Chapter 1, kernel dev manual

2016-12-18 Thread Robert P. J. Day 

* "sys" filesystem is technically "sysfs"

Signed-off-by: Robert P. J. Day 

---

  nothing earth-shattering, just more pedantry.

diff --git a/documentation/kernel-dev/kernel-dev-intro.xml 
b/documentation/kernel-dev/kernel-dev-intro.xml
index 263e500..abc51aa 100644
--- a/documentation/kernel-dev/kernel-dev-intro.xml
+++ b/documentation/kernel-dev/kernel-dev-intro.xml
@@ -74,14 +74,14 @@
 visible CONFIG options as presented by the 
Linux
 kernel menuconfig system.
 Contrast this against a complete Linux kernel
-.config, which includes all the automatically
+.config file, which includes all the 
automatically
 selected CONFIG options.
 This efficiency reduces your maintenance effort and allows you
 to further separate your configuration in ways that make sense for
 your project.
 A common split separates policy and hardware.
 For example, all your kernels might support
-the proc and sys 
filesystems,
+the proc and sysfs 
filesystems,
 but only specific boards require sound, USB, or specific drivers.
 Specifying these configurations individually allows you to 
aggregate
 them together as needed, but maintains them in only one place.

-- 


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] setting up autobuilder on local machine

2016-12-18 Thread Paul Barker 
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.

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

[yocto] setting up autobuilder on local machine

2016-12-18 Thread Mirza Krak 
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?

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

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