+ Adds native support for systemd in addition to sysvinit.
* Splits the huge recipe into an inc and a small bb file.
* Avoids the installation of the sysvinit files with systemd.
Signed-off-by: Markus Hubig mhu...@imko.de
---
.../openssh/openssh-6.2p2/init | 92
My current build system is an Ubuntu 11.10 64-bit (server). This is now out of
support, so I plan to upgrade to 12.04 (LTS).
Is this likely to go smoothly, or are there some gotchas to worry about? I'm
currently building for Poky 8 if that makes a difference.
Thanks!
Chris Tapp
On Thu, Jul 11, 2013 at 11:49:47AM +0100, Chris Tapp wrote:
My current build system is an Ubuntu 11.10 64-bit (server). This is
now out of support, so I plan to upgrade to 12.04 (LTS).
Hello,
Is this likely to go smoothly, or are there some gotchas to worry
about? I'm currently building for
No problems at all...I am running since long :)
//Gaurang Shastri
On Thu, Jul 11, 2013 at 5:36 PM, Eren Türkay e...@hambedded.org wrote:
On Thu, Jul 11, 2013 at 11:49:47AM +0100, Chris Tapp wrote:
My current build system is an Ubuntu 11.10 64-bit (server). This is
now out of support,
On Thu, Jul 11, 2013 at 11:43:28AM +0200, Markus Hubig wrote:
+ Adds native support for systemd in addition to sysvinit.
* Splits the huge recipe into an inc and a small bb file.
* Avoids the installation of the sysvinit files with systemd.
Similar patch is already on oe-core ML where it
Hi,
I created a recipe (xyz) to assemble together an externally built executable
and some configuration files that are local to recipe. It consists of a few
SRC_URI specifications for the files and a do_install function to place all the
pieces in the root filesystem. When I bitbake the recipe,
On Thu, Jul 11, 2013 at 3:20 PM, Brian Karcz bri...@russound.com wrote:
I created a recipe (xyz) to assemble together an externally built executable
and some configuration files that are local to recipe. It consists of a few
SRC_URI specifications for the files and a do_install function to
On 11 July 2013 15:20, Brian Karcz bri...@russound.com wrote:
I created a recipe (xyz) to assemble together an externally built executable
and some configuration files that are local to recipe. It consists of a few
SRC_URI specifications for the files and a do_install function to place all
the
Thanks Ross and Nicolas. That was the nudge I needed to get past this.
-Brian
-Original Message-
From: Burton, Ross [mailto:ross.bur...@intel.com]
Sent: Thursday, July 11, 2013 10:29 AM
To: Brian Karcz
Cc: yocto@yoctoproject.org
Subject: Re: [yocto] only -dbg and -dev packages being
Has anyone tried using the bitbake-env utility lately?
On master I get:
$ bitbake-env
Traceback (most recent call last):
File /home/trevor/local/bin/bitbake-env, line 275, in module
main(sys.argv[1:])
File /home/trevor/local/bin/bitbake-env, line 248, in main
tinfoil =
On Thu, Jul 11, 2013 at 9:25 AM, Trevor Woerner
trevor.woer...@linaro.orgwrote:
Has anyone tried using the bitbake-env utility lately?
On master I get:
$ bitbake-env
Traceback (most recent call last):
File /home/trevor/local/bin/bitbake-env, line 275, in module
main(sys.argv[1:])
On 11 July 2013 17:27, Chris Larson clar...@kergoth.com wrote:
On Thu, Jul 11, 2013 at 9:25 AM, Trevor Woerner trevor.woer...@linaro.org
wrote:
Has anyone tried using the bitbake-env utility lately?
bitbake has had some changes recently. Try using the 'show' subcommand of
I recall a while back that OE/poky had issues with Ubuntu's dash shell
(Ubuntu's replacement for bash) which required the the shell to be linked
to bash rather than dash. Is this (bash) still a requirement for Yocto/Poky
or does it work with dash now.
On 11 July 2013 19:39, Glenn Schmottlach gschmottl...@gmail.com wrote:
I recall a while back that OE/poky had issues with Ubuntu's dash shell
(Ubuntu's replacement for bash) which required the the shell to be linked to
bash rather than dash. Is this (bash) still a requirement for Yocto/Poky or
OK, I finally tracked this bugger down to the eglibc update to 2.18 and
specifically
../../../eglibc/2.18-r0/eglibc-2.18/libc/ChangeLog: * include/features.h
(__GLIBC_HAVE_LONG_LONG): Remove.
Turns out that in boost code there is a check for the
__GLIBC_HAVE_LONG_LONG in cstdint.hpp
Thanks for the feedback. Just waiting for a backup to complete and then I'll
run the update...
On 11 Jul 2013, at 13:20, Gaurang Shastri wrote:
No problems at all...I am running since long :)
//Gaurang Shastri
On Thu, Jul 11, 2013 at 5:36 PM, Eren Türkay e...@hambedded.org wrote:
On 11 Jul 2013, at 20:27, Saul Wold wrote:
OK, I finally tracked this bugger down to the eglibc update to 2.18 and
specifically
../../../eglibc/2.18-r0/eglibc-2.18/libc/ChangeLog: * include/features.h
(__GLIBC_HAVE_LONG_LONG): Remove.
Turns out that in boost code there is a
dash will obviously work but not all the properties of bash (like wild card
characters). somewhere you need to change the logic to run with dash...
but if you really like bash, then you can do
# dpkg-reconfigure dash
and select NO on the prompt
//Gaurang Shastri
On Fri, Jul 12, 2013 at 12:32
Hi,
I am building the Arago Yocto Project first time. I have follow the
steps given in the Arago Project link -
http://arago-project.org/wiki/index.php/Setting_Up_Build_Environment#Detailed_Setup
Error Log is -
amit@amit-HP:~/tisdk/build$ MACHINE=am335x-evm bitbake
19 matches
Mail list logo
