On 2014-01-23 11:56, Otavio Salvador wrote:
On Thu, Jan 23, 2014 at 6:39 AM, David Nyström
david.c.nyst...@gmail.com wrote:
On ons 22 jan 2014 19:11:21, Otavio Salvador wrote:
On Wed, Jan 22, 2014 at 4:02 PM, David Nyström
david.c.nyst...@gmail.com wrote:
On ons 22 jan 2014 16:47:06, Otavio
Use a systemd service file for first boot configuration for dpkg
based images which has 'package-management' in its IMAGE_FEATURES.
[YOCTO #5719]
Signed-off-by: Chen Qi qi.c...@windriver.com
---
meta/recipes-devtools/dpkg/dpkg.inc| 21 ++--
From: Ross Burton ross.bur...@intel.com
This patch mainly adds a systmd service file for run-postinsts,
which is started at first boot to run the post-install scripts.
Apart from this, this patch also modifies the installation location
of run-postinsts to ${sbindir}. This is because this script
From: Ross Burton ross.bur...@intel.com
The run-postinsts script has been moved to ${sbindir}.
[YOCTO #5719]
Signed-off-by: Chen Qi qi.c...@windriver.com
---
meta/classes/image.bbclass |4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/meta/classes/image.bbclass
From: Ross Burton ross.bur...@intel.com
Remove this service as it's moved to the run-postinsts recipe.
[YOCTO #5719]
Signed-off-by: Chen Qi qi.c...@windriver.com
---
meta/recipes-core/systemd/systemd-compat-units.bb | 19 +--
.../systemd-compat-units/run-postinsts.service
If we enable ipk/deb package back-end, and we have 'package-management'
in our IMAGE_FEATURES, then the /etc/rcS.d/S99run-postinsts would
still exist in our system after a clean start-up.
The initial design for run-postinsts requires the related init script
to be removed if there's no more
Seems that it is caused by the libtool, but I'm not very sure, we can
reproduce it by:
$ sudo touch /usr/lib/libstdc++.so
$ bitbake db
// Robert
On 01/24/2014 03:01 AM, Paul Barker wrote:
On 23 January 2014 17:54, Philip Balister phi...@balister.org wrote:
On 01/23/2014 06:51 AM, Carlos
On Fri, Jan 24, 2014 at 6:51 AM, David Nyström
david.c.nyst...@gmail.com wrote:
On 2014-01-23 11:56, Otavio Salvador wrote:
On Thu, Jan 23, 2014 at 6:39 AM, David Nyström
david.c.nyst...@gmail.com wrote:
On ons 22 jan 2014 19:11:21, Otavio Salvador wrote:
On Wed, Jan 22, 2014 at 4:02 PM,
Hi Robert,
What is your OS?
I am unable to reproduce it on my machine following your testcase: Ubuntu 13.10
x86 64bits.
I tried with qemux86 and qemux86-64 machines.
But then again, on my machine there is no /usr/lib/libstdc++.so file.
I assume that you have tried with that touch, see how system
On Mon, 2014-01-20 at 20:24 +0800, Robert Yang wrote:
The dash can't handle the or [[ in parameter expansion, for example:
A=/usr/bin/[[
B=[[
C=${A%$B}
The C should be /usr/bin in common, but it will be /usr/bin/[[ on
dash, use dirname to fix it.
NOTE:
There are 3 lines about
Signed-off-by: Jason Plum jp...@devonit.com
---
meta/lib/oe/path.py | 13 -
1 file changed, 12 insertions(+), 1 deletion(-)
diff --git a/meta/lib/oe/path.py b/meta/lib/oe/path.py
index 46783f8..dab20fc 100644
--- a/meta/lib/oe/path.py
+++ b/meta/lib/oe/path.py
@@ -90,7 +90,7 @@ def
On 14-01-24 14:43 +0100, Richard Purdie wrote:
On Mon, 2014-01-20 at 20:24 +0800, Robert Yang wrote:
The dash can't handle the or [[ in parameter expansion, for example:
Good to know. Interesting! Noting that escaping the [ would work,
but not applicable in this case.
A=/usr/bin/[[
On Thu, 2014-01-23 at 18:22 +, alexandru.sar...@freescale.com wrote:
Maybe I didn't understand correctly what kind of toolchain you want to
be built in the end. Do you want to have a single GCC that builds all
powerpc targets (e500v2, e5500, e6500 etc) and a separate sysroot for
Added new tests:
- sstate relocation stress testing
- rebuild from sstate stress testing
Signed-off-by: Corneliu Stoicescu corneliux.stoice...@intel.com
---
meta/lib/oeqa/selftest/_sstatetests_noauto.py | 96 +
1 file changed, 96 insertions(+)
create mode 100644
The following changes since commit 1a9226f140f578f11696abf1a3c989fae1d4c14a:
libtool-cross/native: Force usage of bash due to sstate inconsistencies
(2014-01-23 12:18:05 +)
are available in the git repository at:
git://git.yoctoproject.org/poky-contrib ciorga/YB5733
This fix integrates a patch released
after rpcbind 0.2.1 distribution.
0001-rpcbind-rpcuser-not-being-set-in-Makefile.am.patch
fixes the issue of rpcuser not being set in Makefile.am,
which causes rpcbind to immediately exit.
Fixes [YOCTO #5733].
Signed-off-by: Cristian Iorga
Adds packageconfigs for all appropriate configure arguments (other than jpeg
8/12 bit mode support, where I wasn't clear on the deps, and which I doubt we
care about).
jpeg, zlib, and xz dependencies can now be controlled.
Signed-off-by: Christopher Larson kerg...@gmail.com
---
This fix integrates a patch released
after rpcbind 0.2.1 distribution.
0001-rpcbind-rpcuser-not-being-set-in-Makefile.am.patch
fixes the issue of rpcuser not being set in Makefile.am,
which causes rpcbind to immediately exit.
Fixes [YOCTO #5733].
Signed-off-by: Cristian Iorga
The following changes since commit 1a9226f140f578f11696abf1a3c989fae1d4c14a:
libtool-cross/native: Force usage of bash due to sstate inconsistencies
(2014-01-23 12:18:05 +)
are available in the git repository at:
git://git.yoctoproject.org/poky-contrib ciorga/YB5733
Hi folks,
As previously discussed, OpenEmbedded will be present at FOSDEM this year in
Brussels in a week's time:
https://fosdem.org/2014/
If you will be at the conference, please add yourself to the appropriate
section on the following wiki page (or ask me to if you have trouble editing):
On 01/24/2014 07:08 AM, Iorga, Cristian wrote:
Hi Robert,
What is your OS?
I am unable to reproduce it on my machine following your testcase: Ubuntu
13.10 x86 64bits.
I tried with qemux86 and qemux86-64 machines.
But then again, on my machine there is no /usr/lib/libstdc++.so file.
I
On 2014-01-23 18:54, Philip Balister wrote:
On 01/23/2014 06:51 AM, Carlos Rafael Giani wrote:
Hello,
I noticed that since the C++ bindings for the berkeley DB were included
in commit 23f29027db73d5759889b48fabdea7f6173217a7 , I cannot build db
anymore.
The error is:
On Thu, 2014-01-23 at 18:22 +, alexandru.sar...@freescale.com wrote:
[Alex Sardan] No. The more generic target powerpc-none-linux will not
generate SPE code and the powerpc-none-linux-gnuspe target that generates
SPE will not be able to generate Altivec.
Why not? As far as I can tell from
On 01/23/2014 04:02 AM, Nicolas Dechesne wrote:
As discussed in [1], SDL recipe makes the wrong assumption that
'opengl' in DISTRO_FEATURES implies GL/GLX. However 'opengl' could
also mean GLES/EGL, and the recipe fails to build in such
situations. So we add a PACKAGECONFIG option for opengl so
Signed-off-by: Saul Wold s...@linux.intel.com
---
scripts/combo-layer | 6 --
1 file changed, 4 insertions(+), 2 deletions(-)
diff --git a/scripts/combo-layer b/scripts/combo-layer
index ae97471..9da1d3a 100755
--- a/scripts/combo-layer
+++ b/scripts/combo-layer
@@ -194,7 +194,8 @@ def
Building the C++ bindings in a484b35b818768487ff27cf06b8c5d4e128126af
introduced this error on systems with /usr/lib/libstdc++.so present:
/usr/lib/libstdc++.so: file not recognized: File format not recognized
The shipped libtool is sysroot aware, so pass --with-sysroot so it will
extract
26 matches
Mail list logo
