Hi Martin,
I’m sorry, I haven’t been able to reproduce your particular issue locally ☹
Here’s a step by step of my setup process, maybe it can help you:
1. Clone fresh poky
2. Source a build environment by issuing: “source oe-init-build-env
{build_folder_name}”
3. While in {build_folder_name}, start toaster by issuing: “.
{path_to_poky}/bitbake/bin/toaster” (note the leading period-and-space)
4. Once toaster starts, access the web interface and create a new
project(tried both fido and local yocto project)
5. In said project, configure the machine to one that supports lsb builds
(i.e genericx86-64)
6. In the bitbake variables configuration page, change DISTRO to
“poky-lsb” from “poky”
7. Still in the bitbake variables configuration page, remove the
SDK_MACHINE variable (there is a known issue with this particular variable in
master and deleting it is a temporary workaround)
You should now be able to issue a core-image-lsb build command that will fail
with a “Nothing PROVIDES 'core-image-lsb'” error. Still looking into that
problem, but it’s definitely passed the step where you’re getting the error you
mentioned below.
Regards,
Mihail
From: Martin Townsend [mailto:[email protected]]
Sent: Tuesday, December 08, 2015 4:12 PM
To: Mihail, StanciuX
Cc: [email protected]
Subject: Re: [yocto] Toaster Problem
Hi,
I'm using Ubuntu 14.04 LTS, I've cloned poky as myself and added myself to the
www-data group and used
sudo setfacl -d -m group:www-data:rwx /var/www
before doing all this so permissions should be ok. /var/www has group ownership
of www-data
I've checkout out master.
Ah yes, the toaster mailing list would have been better :)
Cheers,
Martin.
On Tue, Dec 8, 2015 at 1:46 PM, Mihail, StanciuX
<[email protected]<mailto:[email protected]>> wrote:
Hi Martin,
First off, may I suggest the toaster mailing list in the future if you have
questions ([email protected]<mailto:[email protected]>)
As for your problem:
Something is off about the way your toaster was started.
Here’s how the first line above your traceback looks on my machine:
lbc_shellcmmd: (/home/dave/poky) git remote –v
That location “/home/dave/poky” is where I issued the toaster start command
(bitbake/bin/toaster).
I’ve tried to reproduce this on my machine but haven’t been able to do it.
Could you please let us know how you started toaster and from what location?
Also, was it as root or a different user?
Off the top of my head , one thing that might cause this would be if you cloned
poky as root then somehow started toaster as a different user.
Also, which yocto project (poky) release are you using? Was it master or maybe
Jethro?
Oh, and what flavor linux is this on?
Regards,
Mihail
From: [email protected]<mailto:[email protected]>
[mailto:[email protected]<mailto:[email protected]>]
On Behalf Of Martin Townsend
Sent: Tuesday, December 08, 2015 12:40 PM
To: [email protected]<mailto:[email protected]>
Subject: [yocto] Toaster Problem
Hi,
I'm trying out a production instance of toaster, I'm following the instructions
from here
http://www.yoctoproject.org/docs/latest/toaster-manual/toaster-manual.html#toaster-setting-up-a-production-instance-of-toaster
I managed to get toaster up and running but had to adjust a few things which
you might want to correct in the documentation:
1) virtualenv package doesn't exist in Ubuntu 14.04 had to use python-virtualenv
2) You need python headers later so add python-dev to list of packages to
install
3) After cloning poky there should be a cd poky before checking out a branch.
4) SECRET_KEY, it would be nice to know what this is used for, what characters
is can contain, ie can it contain spaces.
5) In the mysql part is states we are creating a database called toaster but in
the settings.py we specify toaster_main one of them needs correcting.
6) Before calling ./bitbake/lib/toaster/manage.py syncdb --migrate maybe it
should link to 3.5 and state that you should create a Django super user first.
7)There's a typo in the Apache toaster.conf s/toastern_wsgi/toaster_wsgi/
8) Build runner service is wrong, there needs to be the poky directory involved
somewhere, either cd /var/www/toaster/poky or we call
./poky/bitbake/toaster/manage.py
Even with all this I can't get it to build, creating a project based on fido
1.8 and trying to build core-image-lsb I get
2015-12-08 10:27:57,705 DEBUG localhostbecontroller, our git repos are
{(u'git://git.yoctoproject.org/meta-yocto<http://git.yoctoproject.org/meta-yocto>',
u'fido'): [(u'meta-yocto',
u'meta-yocto'),
(u'meta-yocto-bsp',
u'meta-yocto-bsp')],
(u'git://git.yoctoproject.org/poky<http://git.yoctoproject.org/poky>',
u'fido'): [('bitbake', u'bitbake'),
(u'openembedded-core',
u'meta')]}
2015-12-08 10:27:57,705 DEBUG lbc_shellcmmd: () git remote -v
Traceback (most recent call last):
File
"/var/www/toaster/poky/bitbake/lib/toaster/bldcontrol/management/commands/runbuilds.py",
line 60, in schedule
bec.triggerBuild(br.brbitbake_set.all(), br.brlayer_set.all(),
br.brvariable_set.all(), br.brtarget_set.all())
File
"/var/www/toaster/poky/bitbake/lib/toaster/bldcontrol/localhostbecontroller.py",
line 282, in triggerBuild
self.setLayers(bitbake, layers, targets)
File
"/var/www/toaster/poky/bitbake/lib/toaster/bldcontrol/localhostbecontroller.py",
line 150, in setLayers
for remotes in self._shellcmd("git remote -v",
self.be.sourcedir).split("\n"):
File
"/var/www/toaster/poky/bitbake/lib/toaster/bldcontrol/localhostbecontroller.py",
line 59, in _shellcmd
p = subprocess.Popen(command, cwd = cwd, shell=True,
stdout=subprocess.PIPE, stderr=subprocess.PIPE)
File "/usr/lib/python2.7/subprocess.py", line 710, in __init__
errread, errwrite)
File "/usr/lib/python2.7/subprocess.py", line 1327, in _execute_child
raise child_exception
OSError: [Errno 2] No such file or directory: ''
in the console.
Any idea whats going wrong?
Cheers,
Martin.
--
_______________________________________________
toaster mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/toaster
