Concatenated fix of PowerPC time related system calls in eglibc 2.18 taken
from upstream glibc. See credits in patch header.
The effect is that some time related system calls returns nothing or garbage.
Fix tested on PowerPC e300c3.
Eglibc 2.17 does not have this issue and the patches are
On Sun, 2014-03-30 at 18:55 -0400, Trevor Woerner wrote:
On 03/11/14 11:40, Stefan Stanacar wrote:
== is a bashism use = instead.
But the first line of this script is:
#/bin/bash
Shouldn't a bash script be allowed to have bash-isms??!
I was referring to the recipe which shouldn't
On 03/29/2014 12:48 AM, Iorga, Cristian wrote:
Hello all,
This is an important patch, please make sure that BA still works correctly
after this one gets merged (including properly building an image in BA).
Hi Cristian,
I have built the build-appliance-image with this one merged,
and
Update and resend.
* Update patch header.
* Drop PR.
yanjun.zhu (1):
pseudo-1.5.1: keep install command directory mode
.../files/pseudo-1.5.1-install-directory-mode.patch| 18 ++
meta/recipes-devtools/pseudo/pseudo_1.5.1.bb | 3 +--
2 files changed, 19
Hello,
BA is short for Build Appliance, and corresponds to build-appliance-image
target.
Like I previously said, only building BA is not a proper test.
After the change that you proposed (a fine change, I might say), building
images in BA is another test that needs to be performed in order to
The following changes since commit 8210928e847fda7dbc145a94372b0beaf653a4f9:
yocto-bsps: remove linux-yocto 3.8 bbappend (2014-03-30 23:53:00 +0100)
are available in the git repository at:
git://git.yoctoproject.org/poky-contrib ciorga/lsb-pam-enforcing
core-image-lsb only gave a warning:
WARNING: Building libpam but 'pam' isn't in DISTRO_FEATURES,
PAM won't work correctly
when the proper DISTRO was not set for it.
default choice would be DISTRO = poky-lsb,
but not necessarily, depending on each custom distro.
This fix will enforce the proper
On Mon, 2014-03-31 at 12:51 +0300, Cristian Iorga wrote:
core-image-lsb only gave a warning:
WARNING: Building libpam but 'pam' isn't in DISTRO_FEATURES,
PAM won't work correctly
when the proper DISTRO was not set for it.
default choice would be DISTRO = poky-lsb,
but not necessarily,
No, but I will.
But is this a negative point of the patch, or the autobuilder should be changed?
I acted upon some personal observations, a discussion with Paul (he suggested
the change) and also on this guide:
https://wiki.yoctoproject.org/wiki/LSB_Result (in which distro is set to
poky-lsb).
On 29 March 2014 20:04, Otavio Salvador ota...@ossystems.com.br wrote:
piglit and mesa-demos are not buildable in x11-less distros so we must
to add those only when opengl and x11 DISTRO_FEATURES are available.
I'm surprised that piglit needs libx11, waffle should be abstracting
that. I'll
On Mon, Mar 31, 2014 at 04:35:30PM +0800, Kai Kang wrote:
From: yanjun.zhu yanjun@windriver.com
When install command sets the created directory mode, pseudo will change
the mode of the directory to 0700 incorrectly. Backport patch to fix it.
Drop PR as well.
Signed-off-by:
The following change since commit 2116e326d9d7039aac4ec6c7ae5d2a2bedfb4a74:
linux-yocto/3.10: fix qemuarm build failure (2014-03-30 23:52:10 +0100)
is available in the git repository at:
git://git.openembedded.org/openembedded-core-contrib paule/sdkmachine
If you try to set SDKMACHINE in a distro configuration file, it won't
take effect because by the time that is parsed the line in bitbake.conf
which includes the appropriate conf file for SDKMACHINE has already been
parsed. Check that SDK_ARCH has changed from its default value and show
an error if
Hello,
I have checked, on the autobuilder the right association between LSB-enabled
images and proper distro (in our case, poky-lsb) is in place.
As such, my patch should not cause any trouble.
Regards,
Cristian
-Original Message-
From: openembedded-core-boun...@lists.openembedded.org
On Mon, 2014-03-31 at 10:58 +0100, Richard Purdie wrote:
On Mon, 2014-03-31 at 12:51 +0300, Cristian Iorga wrote:
core-image-lsb only gave a warning:
WARNING: Building libpam but 'pam' isn't in DISTRO_FEATURES,
PAM won't work correctly
when the proper DISTRO was not set for it.
On Monday 31 March 2014 11:58:49 Stanacar, StefanX wrote:
On Mon, 2014-03-31 at 10:58 +0100, Richard Purdie wrote:
On Mon, 2014-03-31 at 12:51 +0300, Cristian Iorga wrote:
core-image-lsb only gave a warning:
WARNING: Building libpam but 'pam' isn't in DISTRO_FEATURES,
PAM won't work
Duplicate parameters in the tune args are repeated in the
MULTILIB_OPTIONS variable. This leads to incorrect configurations
if the order of the parameters is bad.
(Eg. mhard-float m32/mhard-float m64 leads to an incorrect config)
This patch finds the common parameters and removes the duplicates.
On Mon, Mar 31, 2014 at 7:14 AM, Burton, Ross ross.bur...@intel.com wrote:
On 29 March 2014 20:04, Otavio Salvador ota...@ossystems.com.br wrote:
piglit and mesa-demos are not buildable in x11-less distros so we must
to add those only when opengl and x11 DISTRO_FEATURES are available.
I'm
Hi Richard,
I don't quite understand what you mean this makes nss machine specific. After
update way for nss-native, I send this new version for review.
Thanks.
Roy Li (1):
nss: avoid to use the hardcode kernel version
meta/recipes-support/nss/nss.inc | 15 +--
1 file changed,
From: Roy Li rongqing...@windriver.com
When native package is built, use the uname to return the kernel version.
When target is built, read kernel version from
${STAGING_KERNEL_DIR}/kernel-abiversion
to avoid to use the hardcode kernel version.
Signed-off-by: Roy Li rongqing...@windriver.com
On Mon, Mar 31, 2014 at 11:20 AM, Kai Kang kai.k...@windriver.com wrote:
From: Roy Li rongqing...@windriver.com
When native package is built, use the uname to return the kernel version.
When target is built, read kernel version from
${STAGING_KERNEL_DIR}/kernel-abiversion
to avoid to use
On 2014年03月31日 18:24, Martin Jansa wrote:
On Mon, Mar 31, 2014 at 04:35:30PM +0800, Kai Kang wrote:
From: yanjun.zhu yanjun@windriver.com
When install command sets the created directory mode, pseudo will change
the mode of the directory to 0700 incorrectly. Backport patch to fix it.
Drop
On Sun, 2014-03-30 at 22:52 -0300, João Henrique Ferreira de Freitas
wrote:
Hi Tom,
Let's back in this context. This is really important and I was waiting
to complete the previous stage.
Em 17-03-2014 13:11, Otavio Salvador escreveu:
If my understand is right, I like the feature. My
V2:
* keep PR
yanjun.zhu (1):
pseudo-1.5.1: keep install command directory mode
.../files/pseudo-1.5.1-install-directory-mode.patch| 18 ++
meta/recipes-devtools/pseudo/pseudo_1.5.1.bb | 1 +
2 files changed, 19 insertions(+)
create mode 100644
From: yanjun.zhu yanjun@windriver.com
When install command sets the created directory mode, pseudo will change
the mode of the directory to 0700 incorrectly. Backport patch to fix it.
Signed-off-by: yanjun.zhu yanjun@windriver.com
Signed-off-by: Kai Kang kai.k...@windriver.com
---
Drop --disable-ffmpegcomponents which is deprecated since
libomxil-bellagio-0.9.1
Components are external and are available separately here:
http://sourceforge.net/projects/omxil/files/components/
---
meta/recipes-multimedia/libomxil/libomxil_0.9.3.bb | 8 +---
1 file changed, 5
On 31 March 2014 16:39, Matthieu Crapet matthieu.cra...@ingenico.com wrote:
-EXTRA_OECONF += --disable-ffmpegcomponents --disable-Werror
+EXTRA_OECONF += --disable-doc --disable-Werror
--disable-doc is new but wasn't mentioned in the commit message,
please explain why it was added.
Ross
--
In the default config openssh does reverse DNS resolution, but
if there is no DNS configured on the target (or even worse the
DNS server is unreachable) there is a long timeout when connecting
over ssh. This is most visible on core-image-sato-sdk builds on AB, where the
tests take a long time
On Mon, Mar 31, 2014 at 10:20:49PM +0800, Kai Kang wrote:
From: Roy Li rongqing...@windriver.com
When native package is built, use the uname to return the kernel version.
When target is built, read kernel version from
${STAGING_KERNEL_DIR}/kernel-abiversion
to avoid to use the hardcode
On Mon, Mar 31, 2014 at 10:37:36PM +0800, Kang Kai wrote:
On 2014年03月31日 18:24, Martin Jansa wrote:
On Mon, Mar 31, 2014 at 04:35:30PM +0800, Kai Kang wrote:
From: yanjun.zhu yanjun@windriver.com
When install command sets the created directory mode, pseudo will change
the mode of
Drop --disable-ffmpegcomponents which is deprecated since
libomxil-bellagio-0.9.1
Explicitly disable doc generation to prevent using doxygen from build machine.
Components are external and are available separately here:
http://sourceforge.net/projects/omxil/files/components/
---
On 30 March 2014 17:48, Khem Raj raj.k...@gmail.com wrote:
On Sun, Mar 30, 2014 at 8:43 AM, Paul Barker p...@paulbarker.me.uk wrote:
On 30 March 2014 05:17, Khem Raj raj.k...@gmail.com wrote:
On Thu, Mar 27, 2014 at 5:53 AM, Paul Barker p...@paulbarker.me.uk wrote:
On 26 March 2014 22:12,
Hi,
On Mon, Mar 31, 2014 at 11:39 AM, Tom Zanussi
tom.zanu...@linux.intel.comwrote:
But I think you could accomplish the same thing by just allowing the
indirect string e.g. rootfs2 to resolve to either a full path, or as an
image name, which would be treated as an instance of '-e
-yocto 3.8 bbappend (2014-03-30 23:53:00 +0100)
are available in the git repository at:
git://git.yoctoproject.org/poky-contrib adamian/20140331-submission
http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=adamian/20140331-submission
Alexandru DAMIAN (1):
sstate.bbclass: update missed
From: Cristiana Voicu cristiana.vo...@intel.com
Replaced DEPLOY_DIR_IMAGE with DEPLOY_DIR
[YOCTO #6051]
Signed-off-by: Cristiana Voicu cristiana.vo...@intel.com
---
meta/classes/toaster.bbclass | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/meta/classes/toaster.bbclass
On Thu, 2014-03-20 at 12:35 -0700, Ricardo Neri wrote:
Add support to specify a directory for custom BIOS, VGA BIOS and
keymaps as supported by qemu (-L option). Even though this can be
done through qemuparams, having this option provides better user
experience by not having to specify a long
On Mon, 2014-03-31 at 13:18 +0100, Paul Eggleton wrote:
On Monday 31 March 2014 11:58:49 Stanacar, StefanX wrote:
On Mon, 2014-03-31 at 10:58 +0100, Richard Purdie wrote:
On Mon, 2014-03-31 at 12:51 +0300, Cristian Iorga wrote:
core-image-lsb only gave a warning:
WARNING: Building
On Monday 31 March 2014 18:03:32 Richard Purdie wrote:
On Mon, 2014-03-31 at 13:18 +0100, Paul Eggleton wrote:
On Monday 31 March 2014 11:58:49 Stanacar, StefanX wrote:
On Mon, 2014-03-31 at 10:58 +0100, Richard Purdie wrote:
On Mon, 2014-03-31 at 12:51 +0300, Cristian Iorga wrote:
On 31 March 2014 18:03, Richard Purdie
richard.pur...@linuxfoundation.org wrote:
I kind of disagree with that, the LSB image can take into account
configuration in other parts of the system. If pam isn't configured, I'm
not sure that should automatically make it completely unbuildable...
An
On 3/31/14, 12:31 PM, Burton, Ross wrote:
On 31 March 2014 18:03, Richard Purdie
richard.pur...@linuxfoundation.org wrote:
I kind of disagree with that, the LSB image can take into account
configuration in other parts of the system. If pam isn't configured, I'm
not sure that should
Signed-off-by: Bruce Ashfield bruce.ashfi...@windriver.com
---
meta/conf/distro/include/tcmode-default.inc | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/meta/conf/distro/include/tcmode-default.inc
b/meta/conf/distro/include/tcmode-default.inc
index
Richard/Saul,
Here are the remaining changes from my previous pull request for linux-yocto
updates.
Now that 3.14 has been released, we have the full 3.14 kernel and associated
libc-headers .. with no PV games.
There is one new change in the libc-headers series, to adapt to the xz
compression
The release kernel for Yocto 1.5 is the 3.14 kernel, so we introduce
the versioned recipes here.
Signed-off-by: Bruce Ashfield bruce.ashfi...@windriver.com
---
meta/recipes-kernel/linux/linux-yocto-tiny_3.14.bb | 21
meta/recipes-kernel/linux/linux-yocto_3.14.bb | 37
Introduce the 3.14 linux-libc-headers recipe, now that the 3.14 kernel is
available, and the default for the qemu reference BSPs.
The three patches which were required for the previous 3.10 libc-headers
are not required for 3.14 and can be ignored.
Signed-off-by: Bruce Ashfield
3.14 is now the reference for libc-headers. After building and booting 3.x based
BSPs against the 3.14 headers, we can safely remove the old version and patches
that are now part of the mainline kernel.
Signed-off-by: Bruce Ashfield bruce.ashfi...@windriver.com
---
As of the 3.13 kernel bz2 compressed tarballs are not available. To support
older header tarballs, and newer ones that require the 'xz' compressed
bundles, we can break out a variable that allows versioned libc headers to
select the archive format that works.
Signed-off-by: Bruce Ashfield
On Mon, Mar 31, 2014 at 12:21 PM, Paul Barker p...@paulbarker.me.uk wrote:
On 30 March 2014 17:48, Khem Raj raj.k...@gmail.com wrote:
On Sun, Mar 30, 2014 at 8:43 AM, Paul Barker p...@paulbarker.me.uk wrote:
On 30 March 2014 05:17, Khem Raj raj.k...@gmail.com wrote:
On Thu, Mar 27, 2014 at
On Mon, Mar 31, 2014 at 10:56 AM, Bruce Ashfield
bruce.ashfi...@windriver.com wrote:
-LINUXLIBCVERSION ?= 3.10
+LINUXLIBCVERSION ?= 3.14
Does this buy us much ? Infact its too late to change usespace APIs
at this point. 3.10 being LTS
I would assume its a better option to keep at 3.10
--
On 14-03-31 03:29 PM, Khem Raj wrote:
On Mon, Mar 31, 2014 at 10:56 AM, Bruce Ashfield
bruce.ashfi...@windriver.com wrote:
-LINUXLIBCVERSION ?= 3.10
+LINUXLIBCVERSION ?= 3.14
Does this buy us much ? Infact its too late to change usespace APIs
This was always the plan. I've been building
On 31 March 2014 18:56, Bruce Ashfield bruce.ashfi...@windriver.com wrote:
The release kernel for Yocto 1.5 is the 3.14 kernel, so we introduce
the versioned recipes here.
Should this say Yocto 1.6?
--
Paul Barker
Email: p...@paulbarker.me.uk
http://www.paulbarker.me.uk
--
On 14-03-31 03:39 PM, Paul Barker wrote:
On 31 March 2014 18:56, Bruce Ashfield bruce.ashfi...@windriver.com wrote:
The release kernel for Yocto 1.5 is the 3.14 kernel, so we introduce
the versioned recipes here.
Should this say Yocto 1.6?
Ha. Yes it should!
Bruce
--
-Khem
On Mar 31, 2014 12:33 PM, Bruce Ashfield bruce.ashfi...@windriver.com
wrote:
On 14-03-31 03:29 PM, Khem Raj wrote:
On Mon, Mar 31, 2014 at 10:56 AM, Bruce Ashfield
bruce.ashfi...@windriver.com wrote:
-LINUXLIBCVERSION ?= 3.10
+LINUXLIBCVERSION ?= 3.14
Does this buy us much ?
On 14-03-31 03:47 PM, Khem Raj wrote:
-Khem
On Mar 31, 2014 12:33 PM, Bruce Ashfield bruce.ashfi...@windriver.com
mailto:bruce.ashfi...@windriver.com wrote:
On 14-03-31 03:29 PM, Khem Raj wrote:
On Mon, Mar 31, 2014 at 10:56 AM, Bruce Ashfield
bruce.ashfi...@windriver.com
Changelog since 2014-03-23 until 2014-03-30. Projects included in this report:
bitbake: git://git.openembedded.org/bitbake
openembedded-core: git://git.openembedded.org/openembedded-core
meta-openembedded: git://git.openembedded.org/meta-openembedded
meta-angstrom:
On Mon, Mar 31, 2014 at 12:10 PM, Martin Jansa martin.ja...@gmail.com wrote:
On Mon, Mar 31, 2014 at 10:20:49PM +0800, Kai Kang wrote:
From: Roy Li rongqing...@windriver.com
When native package is built, use the uname to return the kernel version.
When target is built, read kernel version
On Mon, Mar 31, 2014 at 1:56 PM, Bruce Ashfield
bruce.ashfi...@windriver.com wrote:
Richard/Saul,
Here are the remaining changes from my previous pull request for linux-yocto
updates.
Now that 3.14 has been released, we have the full 3.14 kernel and associated
libc-headers .. with no PV
On 26 March 2014 07:01, Robert Yang liezhi.y...@windriver.com wrote:
The qsort_r() was added to glibc in version 2.8, so there is no qsort_r() on
the host like CentOS 5.x, use qsort() to fix it since they are nearly
identical.
Signed-off-by: Robert Yang liezhi.y...@windriver.com
---
Unfortunately gdk-pixbuf-query-loaders can issue errors but still return
success. We therefore check for output and error in the case any output
is issued (normal success does not issue any).
Signed-off-by: Richard Purdie richard.pur...@linuxfoundation.org
---
Ross: I'm open to better patches ;-)
From: Denys Dmytriyenko de...@ti.com
The latest commit in opkg-utils allows packages created by opkg-build to be read
by dpkg-deb again.
(Based on OE-Core master rev: 219944af2700ce9dbc425fac384cd32b0a802123,
but all of the update-alternative fixes from master are skipped)
Signed-off-by: Denys
I took a look into these three (in hopes of free beer):
polkit-gnome: configure was passed unrecognised options:
--disable-scrollkeeper --disable-man-pages
gnome-bluetooth-2.32.0: gnome-bluetooth: configure was passed
unrecognised options: --disable-schemas-install
openobex-1.5: openobex:
Ping
On 03/19/2014 07:59 PM, Burton, Ross wrote:
On 19 March 2014 02:00, Chong Lu chong...@windriver.com wrote:
If image contains dbus and ptest is in DISTRO_FEATURES, dbus-ptest package
is installed, regardless of whether ptest-pkgs is in IMAGE_FEATURES. This
issue will increase size for most
On 04/01/2014 05:22 AM, Paul Barker wrote:
On 26 March 2014 07:01, Robert Yang liezhi.y...@windriver.com wrote:
The qsort_r() was added to glibc in version 2.8, so there is no qsort_r() on
the host like CentOS 5.x, use qsort() to fix it since they are nearly
identical.
Signed-off-by: Robert
On 2014年04月01日 00:32, Richard Purdie wrote:
On Mon, 2014-03-31 at 17:10 +0200, Martin Jansa wrote:
On Mon, Mar 31, 2014 at 10:20:49PM +0800, Kai Kang wrote:
From: Roy Li rongqing...@windriver.com
When native package is built, use the uname to return the kernel version.
When target is built,
On Mon, Mar 31, 2014 at 06:17:25PM -0700, Adam Lee wrote:
I took a look into these three (in hopes of free beer):
polkit-gnome: configure was passed unrecognised options:
--disable-scrollkeeper --disable-man-pages
gnome-bluetooth-2.32.0: gnome-bluetooth: configure was passed
unrecognised
Fix some errors for bash 3.2.48 by take patches from bash 4.3.
Yong Zhang (1):
bash-3.2.48: fix error path of getc_with_restart
.../bash-fix-error-path-of-getc_with_restart.patch | 41 ++
.../bash-3.2.48/bash-fix-getc_with_restart.patch | 28 +++
From: Yong Zhang yong.zh...@windriver.com
1. let getc_with_restart() handle EAGAIN|EWOULDBLOCK
correctly.
2. When read() returns with ERROR, local_bufused will be set
to -1; and if we return with local_bufused == -1 left,
the next time we call getc_with_restart(), the condition
From: Ming Liu ming@windriver.com
/usr/src/kernel/source deployed by kernel-dev package is symbolically
linking to a build-time kernel source folder, which make no sense when
cross-compiling.
Fixed by not populating it at install stage.
Signed-off-by: Ming Liu ming@windriver.com
From: Denys Dmytriyenko de...@ti.com
This is done to work around the issue of auto-mounting block devices
(i.e. SD cards) when root filesystem is still in read-only mode and
creating /media/device mount-points by udev is not possible. That
is due to udev (/etc/rcS.d/S03udev) getting started
...in roughly 12 hours from now?
--
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core
On Tue, Apr 01, 2014 at 12:04:16AM -0400, Trevor Woerner wrote:
...in roughly 12 hours from now?
?
--
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core
On 04/01/14 00:34, Denys Dmytriyenko wrote:
On Tue, Apr 01, 2014 at 12:04:16AM -0400, Trevor Woerner wrote:
...in roughly 12 hours from now?
?
I'm referring to the monthly OE meeting that's held on IRC. I'm trying
to confirm it takes place today and is scheduled for noon EST.
--
On Fri, Mar 28, 2014 at 2:43 AM, Hongxu Jia hongxu@windriver.com wrote:
++ const size_t max_write = INT_MAX;
I think INT_MAX is a mismatch here size_t may not be defined 'unsigned
int' on all kind of architectures.
--
___
Openembedded-core
Mats
On Fri, Mar 28, 2014 at 9:43 AM, Mats Kärrman mats.karr...@tritech.se wrote:
+# glibc configure options to make use of 603e specific sqrt/sqrtf routines
+GLIBC_EXTRA_OECONF += ${@bb.utils.contains(TUNE_FEATURES, ppce300c3,
--with-cpu=e300c3, , d)}
looks good, may be the comment above
On Fri, Mar 28, 2014 at 10:28 AM, Denys Dmytriyenko de...@denix.org wrote:
-KERNEL_LD = ${CCACHE}${HOST_PREFIX}ld ${HOST_LD_KERNEL_ARCH}
+KERNEL_LD = ${CCACHE}${HOST_PREFIX}ld.bfd ${HOST_LD_KERNEL_ARCH}
KERNEL_AR = ${CCACHE}${HOST_PREFIX}ar ${HOST_AR_KERNEL_ARCH}
I know this is almost a
74 matches
Mail list logo
