this will be required for dizzy when I pull in the cve fix ( which i
missed)..
On 01/15/2015 01:37 AM, Richard Purdie wrote:
The CVE fix introduced problems with entity issues, we observed this
when building the Yocto Docs in particular. Backport the fix from
upstream so we can build our
On 14 January 2015 at 08:47, Robert Yang liezhi.y...@windriver.com wrote:
And bump PR to avoid:
configure: error: source directory already configured; run make
distclean there first
Signed-off-by: Robert Yang liezhi.y...@windriver.com
The autobuilder is hitting this:
On 15 January 2015 at 16:36, akuster808 akuster...@gmail.com wrote:
this will be required for dizzy when I pull in the cve fix ( which i
missed)..
Yes, the CVE fix was broken.
Ross
--
___
Openembedded-core mailing list
This addresses 2 issues discovered trying to build a minimal libc with
libm option. By default nscd was always being built and without inet
enabled there were missing symbols.
[YOCTO #7108]
Signed-off-by: Saul Wold s...@linux.intel.com
---
Sure thing. Will update and resend.
On 15 January 2015 at 08:57, Aníbal Limón anibal.li...@linux.intel.com wrote:
Hi Dan,
Can you explain in the commit message what is this change needed?
On 14/01/15 21:51, Dan McGregor wrote:
+EXTRA_OECONF_append_class-target = TAR=tar
Kind regards
Remove libgfortran packages from PACKAGES list and skip them at compiling
and installing as long as libgfortran has separate receipe since commit
5bde5d9b39ea67f19a1a6aedd0c08c6cfedcbe5f
gcc: Allow fortran to build successfully in 4.8
Otherwise, when fortran support will be enabled in the
On Thu, 2015-01-15 at 18:31 +0200, Daniel Dragomir wrote:
Remove libgfortran packages from PACKAGES list and skip them at compiling
and installing as long as libgfortran has separate receipe since commit
5bde5d9b39ea67f19a1a6aedd0c08c6cfedcbe5f
gcc: Allow fortran to build successfully in 4.8
See bug # 7143 for the details of this issue..
In short, when generating an SDK with the following configuration:
MACHINE = qemumips64
require conf/multilib.conf
MULTILIBS = multilib:lib32 multilib:lib64
DEFAULTTUNE = mips32r2
DEFAULTTUNE_virtclass-multilib-lib32 = mips64-n32
[YOCTO #7143]
When the system is configured for a multilib SDK, such as:
require conf/multilib.conf
MULTILIBS = multilib:lib32 multilib:lib64
DEFAULTTUNE = mips32r2
DEFAULTTUNE_virtclass-multilib-lib32 = mips64-n32
DEFAULTTUNE_virtclass-multilib-lib64 = mips64
Only one of the mips64-n32 or
On 15 January 2015 at 09:41, Dan McGregor danismostlik...@gmail.com wrote:
From: Dan McGregor dan.mcgre...@usask.ca
Force dpkg to use tar on the target.
The dpkg configure script looks for gnutar, gtar, and
tar in order. If it finds gnutar or gtar on the host
it expects to use that as its
On Thu, Jan 08, 2015 at 06:11:18PM +0100, Martin Jansa wrote:
* n is a tuple since this commit:
commit d3aa7668a9f001044d0a0f1ba2de425a36056102
Author: Richard Purdie richard.pur...@linuxfoundation.org
Date: Mon Jul 7 18:41:23 2014 +0100
Subject package.bbclass: Improve shlibs
From: Dan McGregor dan.mcgre...@usask.ca
Force dpkg to use tar on the target.
The dpkg configure script looks for gnutar, gtar, and
tar in order. If it finds gnutar or gtar on the host
it expects to use that as its tar program on the target.
Without this, if gtar exists (as it does on my system)
Bump to 1.1.0
1. Updated LICENSE from GPLv3 to GPLv2 or later
2. Misc. spelling fix
Signed-off-by: Maxin B. John maxin.j...@enea.com
---
.../fuse-exfat/{fuse-exfat_1.0.1.bb = fuse-exfat_1.1.0.bb} | 12 ++--
1 file changed, 6 insertions(+), 6 deletions(-)
rename
On Thu, Jan 15, 2015 at 05:08:47PM +0100, Maxin B. John wrote:
Bump to 1.1.0
1. Updated LICENSE from GPLv3 to GPLv2 or later
2. Misc. spelling fix
Please resend to oe-devel ML.
Signed-off-by: Maxin B. John maxin.j...@enea.com
---
.../fuse-exfat/{fuse-exfat_1.0.1.bb =
Hi Dan,
Can you explain in the commit message what is this change needed?
On 14/01/15 21:51, Dan McGregor wrote:
+EXTRA_OECONF_append_class-target = TAR=tar
Kind regards
alimon
--
___
Openembedded-core mailing list
From: Dan McGregor dan.mcgre...@usask.ca
Rebase sshd_config and ssh_config with openssh upstream.
Check for the ed25519 key in the systemd keygen service.
Signed-off-by: Dan McGregor dan.mcgre...@usask.ca
---
.../openssh/openssh/ssh_config | 4 ++-
No code changes since the RFC version, besides a rebase against latest yocto
changes.
The following changes since commit 10837473b27aa1708866eb2b1b5701daa984e94e:
libxml2: Backport fix for CVE introduced entity issues (2015-01-15 16:55:17
+)
are available in the git repository at:
Since lsof are doing two unpacks and S should be set to match
the second unpack of an internal archive, we should let the build
system know that we are aware of this.
Solve this by temporarily set S like lsof are doing with SRC_URI.
[YOCTO #5627]
Signed-off-by: Petter Mabäcker pet...@technux.se
Currently base.bbclass is creating S if it's not created by unpacking
an archive or fetching a repository. If we avoid creating S we can detect
when S hasn't been set correctly, since it will not exist. Then we can tell
the user that they should set S to a proper value, instead of just failing
After removal of auto-creating S we must ensure that all recipes are
using a proper value for S. Also do some minor adjustment after changing
value of S.
[YOCTO #5627]
Signed-off-by: Petter Mabäcker pet...@technux.se
---
meta/recipes-graphics/xorg-font/xorg-minimal-fonts.bb | 4 +++-
1 file
After removal of auto-creating S we must ensure that all recipes are
using a proper value for S. Also do some cleanup of code not needed
after changing value of S.
[YOCTO #5627]
Signed-off-by: Petter Mabäcker pet...@technux.se
---
meta/recipes-devtools/makedevs/makedevs_1.0.1.bb | 6 ++
1
After removal of auto-creating S we must ensure that all recipes are
using a proper value for S.
Fix all recipes that only need to set S equals to WORKDIR.
[YOCTO #5627]
Signed-off-by: Petter Mabäcker pet...@technux.se
---
meta/recipes-bsp/alsa-state/alsa-state.bb
The new patches 0060-Only-xxx and 0061-Fix-xxx aim to fix the bug in e500v2 as
following:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63908 .
Signed-off-by: Lei Maohui leimao...@cn.fujitsu.com
---
meta/recipes-devtools/gcc/gcc-4.9.inc | 12 +-
On 01/16/2015 01:12 AM, Burton, Ross wrote:
On 14 January 2015 at 08:47, Robert Yang liezhi.y...@windriver.com
mailto:liezhi.y...@windriver.com wrote:
And bump PR to avoid:
configure: error: source directory already configured; run make distclean
there first
Signed-off-by:
Deliver script ssh-copy-id from openssh which is useful to add an
authorized ssh key.
Signed-off-by: Kai Kang kai.k...@windriver.com
---
meta/recipes-connectivity/openssh/openssh_6.7p1.bb | 1 +
1 file changed, 1 insertion(+)
diff --git a/meta/recipes-connectivity/openssh/openssh_6.7p1.bb
msmtp moved from gnome-keyring to libsecret, so update EXTRA_OECONF. Also
explicitly disable libgsasl to avoid potential non-deterministic builds in the
future.
Signed-off-by: Ross Burton ross.bur...@intel.com
---
meta/recipes-extended/msmtp/msmtp_1.6.1.bb |2 +-
1 file changed, 1
There are some cases we want the manipulation cross-canadian performance
on TARGET_OS, there are also cases like meta-environment where we do not
want this manipulation.
We did try and use immediate expansion to avoid this problem and it
works in the non multilib case. If we have a multilib that
Always use use_icc to check if IceCC should be enabled. Move
ICECC_DISABLED variable checking to use_icc function. Also while we are
at it, fix condition in icc_is_allarch function.
Signed-off-by: Dmitry Eremin-Solenikov dmitry_ere...@mentor.com
---
meta/classes/icecc.bbclass | 15
The CVE fix introduced problems with entity issues, we observed this
when building the Yocto Docs in particular. Backport the fix from
upstream so we can build our docs correctly.
[YOCTO #7134]
Signed-off-by: Richard Purdie richard.pur...@linuxfoundation.org
diff --git
From: Bruce Ashfield bruce.ashfi...@windriver.com
guilt is no longer used to manage linux-yocto kernel pathes, so
we no longer need to export variables that it needed to locate
patches in the tree.
Signed-off-by: Bruce Ashfield bruce.ashfi...@windriver.com
Signed-off-by: Ross Burton
From: Bruce Ashfield bruce.ashfi...@windriver.com
commit 3b3f7e785e279 [kernel: Rearrange for 1.8] began the process of
moving the kernel source and build artefacts out of sstate control and
into a shared location.
This changed triggered some workflow issues, as well as bugs related
to the
From: Darren Hart dvh...@linux.intel.com
Fixes [YOCTO 6818]
Update do_unpack[cleandirs] to include the STAGING_KERNEL_BUILDDIR, and
add the same set of updated cleandirs for do_clean.
Signed-off-by: Darren Hart dvh...@linux.intel.com
Signed-off-by: Bruce Ashfield bruce.ashfi...@windriver.com
From: Tom Zanussi tom.zanu...@linux.intel.com
It hasn't actually been being enabled anyway: 'Disabling post unwind,
no support found.'. For now, turn it off because of [YOCTO #7129].
Fixes [YOCTO #7129].
Signed-off-by: Tom Zanussi tom.zanu...@linux.intel.com
Signed-off-by: Ross Burton
From: Darren Hart dvh...@linux.intel.com
Since virtual/kernel do_compile modifies ${B}, we need to wait for
do_compile to copy everything across in order to ensure a deterministic
file set.
Currently, we race against the build and can see .debug directories, and
the do_compile dependency we will
From: Otavio Salvador ota...@ossystems.com.br
Old Linux kernel versions rely on linux/version.h for modules; this
needs to be published for external modules to use. Copy it when
available.
Signed-off-by: Otavio Salvador ota...@ossystems.com.br
Signed-off-by: Ross Burton ross.bur...@intel.com
---
From: Otavio Salvador ota...@ossystems.com.br
When the sstate hash changes for do_configure task, the do_configure
default implementation triggers the 'clean' to be run. For it to
succeed we need to have KERNEL_SRC defined in EXTRA_OEMAKE. Fixes
following error:
,
| DEBUG: Executing shell
From: Tom Zanussi tom.zanu...@linux.intel.com
perf can use either libdw or libunwind dwarf unwinders, or neither.
The perf-libunwind feature implies that if disabled, neither should be
used, so have it disable both libdw and libunwind DWARF unwinders if
disabled.
This fixes [YOCTO #7129].
Hi Chong,
On Monday 12 January 2015 14:48:42 Chong Lu wrote:
It maybe depends on other layers when one layer is added to BBLAYERS. If
define LAYERDEPENDS variable in this layer, we will get error from bitbake.
But sometimes, we don't have defined. Add a mechanism to extend
bitbake-layers and
I've verified this fixes the problem that I had (along with another patch that I
have not yet sent.)
--Mark
On 1/15/15 4:03 AM, Richard Purdie wrote:
There are some cases we want the manipulation cross-canadian performance
on TARGET_OS, there are also cases like meta-environment where we do
39 matches
Mail list logo
