`bitbake uninative-tarball' raises the following warning.
WARNING: Function doesn't exist
This is because SDK_PACKAGING_FUNC is set to "" in its recipe.
Anyway, we need to check this variable to avoid executing empty function.
Signed-off-by: Chen Qi
---
meta/classes/populate_sdk_base.bbcl
The following changes since commit c9b06c79ed8a082d1b385e9f61721aeeda9bf1af:
init-install-efi.sh: fix gummiboot entry installation (2015-04-21 07:19:07
+0100)
are available in the git repository at:
git://git.openembedded.org/openembedded-core-contrib
ChenQi/uninative-tarball-fixes
http
This task is meaningless for uninative-tarball as the package task
has been deleted. Besides, sometimes it would cause problems. To
reproduce, use the following command.
bitbake uninative-tarball -c cleansstate && bitbake uninative-tarball &&
bitbake uninative-tarball -c clean && bitbake uninative
An out of bounds read access in the UTF-8 decoding can be triggered with
a malformed file in the tool less. The access happens in the function
is_utf8_well_formed due to a truncated multibyte character in the sample
file.
The bug does not crash less, it can only be made visible by running less
wit
LIC_FILES_CHKSUM change is due to shifting of
the hunk to different line numbers, checksum remains same still
Change-Id: I0ce0cc96d39c801e57394f7a839a01d11a6f3979
Signed-off-by: Khem Raj
---
.../fontconfig/{fontconfig_2.11.1.bb => fontconfig_2.11.93.bb} | 6 +++---
1 file changed, 3 inserti
With gcc-5 defaulting to gnu11 C we need to follow
c99 inline semantics
Change-Id: I397520c36c81634556b3f3782aebc532e4a79aed
Signed-off-by: Khem Raj
---
meta/recipes-extended/mdadm/files/inline.patch | 39 ++
meta/recipes-extended/mdadm/mdadm_3.3.2.bb | 1 +
2 files
see https://gcc.gnu.org/gcc-5/porting_to.html
we need to stop the preprocessor from generating the #line directives
or we run into issues like
| checking for apr_int64_t Python/C API format string...
| configure: error: failed to recognize APR_INT64_T_FMT on this platform
| Configure failed. The
Fixes cross building dependent packages with gcc-5
e.g. matchbox-panel-2
Change-Id: I6290cfa4aac5d03a7200472d0c713b7ea84b99ac
Signed-off-by: Khem Raj
---
.../fontconfig/revert-static-pkgconfig.patch | 20
.../fontconfig/fontconfig_2.11.93.bb | 1 +
2
it really needs nls, so lets add proper dependencies
and options
Change-Id: Ib01f066e9dadf2784686cbe28578d2784dfcba88
Signed-off-by: Khem Raj
---
meta/recipes-gnome/gnome/gnome-icon-theme_2.31.0.bb | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/meta/recipes-gnome/gnome/gnome
0.28 was released 2 years ago and bunch of patches
have gone in since. The commit rate is quite low
so its not a lot of churn to use. We have backports
for few bugs that are removed. Git version of recipe is removed too
since its no longer needed
Change-Id: I4b57db15320c76b1de5d26a733e60436663ff34
gcc-5 is stricter and complains about const to non-const
conversions, we backport the patch from upstream into 2.00
Change-Id: I17db365fdd253daaa1ab726e2a70ecad0ac7b2ae
Signed-off-by: Khem Raj
---
..._dhcp_vendor-Add-missing-const-qualifiers.patch | 33 ++
meta/recipes-bsp/gr
43 does not compile with gcc-5
Refresh objcopy patch to incorporate latest changes
Change-Id: Ied41ed1335bb1db3438b98121e05c22242a8a13e
Signed-off-by: Khem Raj
---
.../gummiboot/gummiboot/fix-objcopy.patch | 28 +-
meta/recipes-bsp/gummiboot/gummiboot_git.bb|
Make skipping expression simpler to check for given libc
Make sure glibc specific items are covered with right override
Change-Id: I8b4a0b7cbfe38ffdc9320f798038c79c7220552b
Signed-off-by: Khem Raj
---
meta/recipes-core/glibc/glibc_2.21.bb| 8 +++-
meta/recipes-core/pa
Backport a patch from fedora details are in patch header
Change-Id: I6b8dfaae3b751071bf8b0d88b15a4f95c19877f6
Signed-off-by: Khem Raj
---
...sdksyms.sh-Make-sdksyms.sh-work-with-gcc5.patch | 50 ++
.../xorg-xserver/xserver-xorg_1.16.3.bb| 1 +
2 files changed, 51
This will ensure that compiler does not initialize the definitions
in header files
Change-Id: I1076201c667f96707c320a51a77d4a70e22df750
Signed-off-by: Khem Raj
---
.../lttng/lttng-tools/extern-decls.patch | 442 +
meta/recipes-kernel/lttng/lttng-tools_2.6.0.bb |
Kill 2 bugs with one patch
| insserv.c:997:5: note: each undeclared identifier is reported only
once for each function it appears in
| insserv.c:997:15: error: expected ';' before 'char'
| extension char buf[strlen(myname)+2+strlen(fmt)+1];
|^
| insserv.c: In function 'main':
This is turned on by default in gcc-5 so far
we have been getting by this issue but time to fix it
has now come
Change-Id: I012248731de0be7a9b7e232073746360fe6c83dd
Signed-off-by: Khem Raj
---
.../gtk+/gtk+/strict-prototypes.patch | 24 ++
meta/recipes-gnome/gtk+
Change-Id: I5322f1ff8653009b45ddee1a2d3a0d96584d3327
Signed-off-by: Khem Raj
---
meta/recipes-bsp/u-boot/u-boot-mkimage/gcc5.patch | 91 +++
meta/recipes-bsp/u-boot/u-boot-mkimage_2015.01.bb | 4 +-
2 files changed, 94 insertions(+), 1 deletion(-)
create mode 100644 meta/rec
I saw that my prior pull request has not yet been picked so I took opportunity
to update it
with few more commits and remove the commits not needed for world builds out.
With these world builds on OE-Core are succeeding for all supported qemu
machines
The gcc upgrade is not yet proposed since we
From: Roy Li
rsync 3.1.1 allows remote attackers to write to arbitrary files via a symlink
attack on a file in the synchronization path.
Backport Complain-if-an-inc-recursive-path-is-not-right-for-i.patch to fix it
Signed-off-by: Roy Li
---
...-an-inc-recursive-path-is-not-right-for-i.patch |
bdfReadCharacters: ensure metrics fit into xCharInfo struct
We use 32-bit ints to read from the bdf file, but then try to stick
into a 16-bit int in the xCharInfo struct, so make sure they won't
overflow that range.
Signed-off-by: Li Zhou
---
...acters-ensure-metrics-fit-into-xCharInfo-.patch |
bdfReadCharacters: bailout if a char's bitmap cannot be read
Previously would charge on ahead with a NULL pointer in ci->bits, and
then crash later in FontCharInkMetrics() trying to access the bits.
Signed-off-by: Li Zhou
---
...acters-bailout-if-a-char-s-bitmap-cannot-.patch | 36 +++
bdfReadProperties: property count needs range check
Avoid integer overflow or underflow when allocating memory arrays
by multiplying the number of properties reported for a BDF font.
Signed-off-by: Li Zhou
---
...erties-property-count-needs-range-check-C.patch | 38
meta/
I've made a page on OpenEmbedded.org for people to link to jobs they
know about. The job posting hsould have some OpenEmbedded/Yocto Project
content:
http://openembedded.org/wiki/Jobs
I know you can search places like Linkedin for OpenEmbedded and get lots
of hits, but I'd like this to be communi
Docstrings make nosetests output more clear:
Test wic create --help ... ok
Test wic --help ... ok
Test wic list --help ... ok
Test wic create directdisk providing all artifacts. ... ok
Test wic create directdisk --image-name core-image-minimal ... ok
Signed-off-by: Ed Bartosh
---
scripts/tests/
Added 2 simple functional test cases to check if
wic is able to produce images using directdisk.wks
Signed-off-by: Ed Bartosh
---
scripts/setup.cfg | 2 +-
scripts/tests/02_wic_test_directdisk.py | 61 +
2 files changed, 62 insertions(+), 1
Hi Otavio,
On 04/22/2015 02:30 PM, Otavio Salvador wrote:
On Wed, Apr 22, 2015 at 2:27 PM, Anders Darander wrote:
I'm repeating the comments from my review of the earlier version.
I'm slightly worried as we're changing some of the default
configurations here. And we're suddenly starting to
On Thu, 2015-04-23 at 14:25 +0100, Paul Eggleton wrote:
> On Thursday 23 April 2015 16:02:45 Burton, Ross wrote:
> > On 23 April 2015 at 12:20, Paul Eggleton
> > wrote:
> > > I can't remember for certain, but I suspect the lack of this dependency
> > > was intentional, so that you could e.g. copy
On Thu, Apr 23, 2015 at 3:31 PM, Carlos Rafael Giani
wrote:
> It is in master, which is nice. But not in fido? Is it too late for fixes
> like these? If so, I'll have to backport this fix into meta-fsl-arm-extra
> for the cubox-i uboot.
> Otherwise, if it is to be reviewed for inclusion into fido,
It is in master, which is nice. But not in fido? Is it too late for
fixes like these? If so, I'll have to backport this fix into
meta-fsl-arm-extra for the cubox-i uboot.
Otherwise, if it is to be reviewed for inclusion into fido, I'm fine
with that.
Am 2015-04-20 um 21:31 schrieb Otavio Salva
From: Markus Lehtonen
In order to get correct metadata, SRCREV for example.
Fixes [YOCTO #7648].
Signed-off-by: Markus Lehtonen
---
meta/lib/oe/recipeutils.py | 6 +++---
scripts/lib/devtool/standard.py | 35 ++-
2 files changed, 25 insertions(+), 16 dele
If you manually delete files in the workspace layer (which you really
shouldn't) it was possible to get yourself into the situation where you
couldn't reset because we were attempting to check if the file had been
modified and erroring out if it couldn't be opened. If the file's not
there anymore t
From: Markus Lehtonen
This option can be used to have a separate build directory, in order to
keep the srctree directory clean for packages that do not need to be
built in the source directory.
Signed-off-by: Markus Lehtonen
---
scripts/lib/devtool/standard.py | 9 +++--
1 file changed, 7
Names such as glib-2.0 are valid (and used) recipe names, so we need to
support them.
Fixes [YOCTO #7643].
Signed-off-by: Paul Eggleton
---
meta/lib/oe/recipeutils.py | 4 ++--
scripts/devtool| 2 +-
2 files changed, 3 insertions(+), 3 deletions(-)
diff --git a/meta/lib/oe/recipeut
From: Markus Lehtonen
All local files from the layer, including patches, are added to to
srctree repository when S==WORKDIR. The patch files are useless as they
are automatically applied on top of the srctree by devtool.
This change causes devtool extract to not commit these unnecessary (and
pos
From: Markus Lehtonen
Number of patches in mtd-utils changed in changeset bd1aa28.
Signed-off-by: Markus Lehtonen
---
meta/lib/oeqa/selftest/devtool.py | 11 +--
1 file changed, 9 insertions(+), 2 deletions(-)
diff --git a/meta/lib/oeqa/selftest/devtool.py
b/meta/lib/oeqa/selftest/de
We weren't adding the version into the bbappend file name which meant
that building or resetting failed.
Also adjust one of the tests so that we're testing devtool add both with
and without this option.
Fixes [YOCTO #7647].
Signed-off-by: Paul Eggleton
---
meta/lib/oeqa/selftest/devtool.py | 4
From: Markus Lehtonen
Makes the build succeed for packages which do not support separate build
directory, e.g. zlib. The same outcome could be achieved with the
--same-dir option, but, it's generally hard to tell if a random package
would need that option. The negative side effect of this patch i
This series rolls up 5 patches previously posted by Markus (with very
minor tweaks to a couple of the commit messages), and adds three new
patches from me.
The following changes since commit 166f2587468ae71988c610858aad3f7ef67eccba:
bison: don't depend on help2man (2015-04-21 11:29:30 +0100)
Upgrade include these security fixes:
1. CVE-2015-3143
2. CVE-2015-3144
3. CVE-2015-3145
4. CVE-2015-3148
Signed-off-by: Maxin B. John
---
meta/recipes-support/curl/{curl_7.41.0.bb => curl_7.42.0.bb} | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
rename meta/recipes-support/curl/{cur
In v5:
1. removed bluez5 exclusion from world builds;
2. Updated commit messages/general message;
3. Updated bluez4 recipe with improved systemd support.
Please merge this patchset only after the SRCREV of linux-yocto for qemu*
machines will advance after the BT kernel config updates, otherwise s
If you're installing ptest packages into an image there's a good chance
you want to run the tests. Assist with this by recommending
ptest-runner in the -ptest packages.
Signed-off-by: Ross Burton
---
meta/classes/ptest.bbclass |1 +
1 file changed, 1 insertion(+)
diff --git a/meta/classes/
BlueZ 4.x and associated recipes
are now obsolete.
(bluez4,bluez-hcidump, gst-plugin-bluetooth).
Will be moved into recipes-connectivity
collection of meta-openembedded.
BlueZ 4.x is still usable in poky/YP.
Signed-off-by: Cristian Iorga
---
.../obsolete_automake_macros.patch |
BlueZ 5.x is now the default Bluetooth stack.
BlueZ 4.x is moved to recipes-connectivity in meta-oe
layer and still supported in poky/YP.
The following changes since commit 781165b071babb888f46a4e1d15880df924c65f6:
bison: don't depend on help2man (2015-04-21 13:59:21 +0100)
are available in th
Signed-off-by: Cristian Iorga
---
meta/recipes-connectivity/bluez/bluez4.inc | 6 +-
1 file changed, 5 insertions(+), 1 deletion(-)
diff --git a/meta/recipes-connectivity/bluez/bluez4.inc
b/meta/recipes-connectivity/bluez/bluez4.inc
index 11c9616..948b495 100644
--- a/meta/recipes-connectiv
As BlueZ5 will be the default Bluetooth stack,
don't exclude it from world builds.
Signed-off-by: Cristian Iorga
---
meta/recipes-connectivity/bluez5/bluez5.inc | 2 --
1 file changed, 2 deletions(-)
diff --git a/meta/recipes-connectivity/bluez5/bluez5.inc
b/meta/recipes-connectivity/bluez5/bl
If bluez4 is not explicitly passed as a
distro feature, bluez5 should be used as
the default, so backfill it.
Signed-off-by: Cristian Iorga
---
meta/conf/bitbake.conf | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/meta/conf/bitbake.conf b/meta/conf/bitbake.conf
index 2b3c110
On Thursday 23 April 2015 16:02:45 Burton, Ross wrote:
> On 23 April 2015 at 12:20, Paul Eggleton
> wrote:
> > I can't remember for certain, but I suspect the lack of this dependency
> > was intentional, so that you could e.g. copy in an image built elsewhere
> > and run tests on it. Maybe we can
Fixes below listed bugs:
1. CVE-2015-3143
2. CVE-2015-3144
3. CVE-2015-3145
4. CVE-2015-3148
Signed-off-by: Maxin B. John
---
meta/recipes-support/curl/curl/CVE-2015-3143.patch | 38
meta/recipes-support/curl/curl/CVE-2015-3144.patch | 45 ++
meta/recipes-support/curl/cu
On 23 April 2015 at 12:20, Paul Eggleton
wrote:
> I can't remember for certain, but I suspect the lack of this dependency was
> intentional, so that you could e.g. copy in an image built elsewhere and
> run
> tests on it. Maybe we can take the decision we don't need that, but it
> should
> be a c
From: Jackie Huang
This reverts commit 7a1fb7a19d046ff6ebbc07ef83e5258a95fe74b1.
---
meta/files/common-licenses/Firmware-Abilis | 22 -
meta/files/common-licenses/Firmware-Marvell| 18 -
meta/files/common-licenses/Firmware-OLPC | 33 --
meta/files/common-licenses/Fir
From: Jackie Huang
* An approach for non-generic license is added in license.bbclass.
* Revert the commit that added common license files for linux-firmware and
use the new approach.
--
The following changes since commit 781165b071babb888f46a4e1d15880df924c65f6:
bison: don't depend on help2
From: Jackie Huang
Some package like linux-firmware has many licenses that aren't in any
way common, and new ones will be added from time to time, in order to
avoid adding bunch of such common license files that are only applicable
to a specific package, NO_GENERIC_LIC is added to allow copying l
From: Jackie Huang
An alternative approach with NO_GENERIC_LIC has been added
in license.bbclass to allow copying non-generic license,
add it for all firmware licenses.
Signed-off-by: Jackie Huang
---
.../linux-firmware/linux-firmware_git.bb | 39 ++
1 file change
On Thursday 23 April 2015 09:39:08 Cristian Iorga wrote:
> While starting a test with testimage, changes
> of the image under test don't trigger a rebuild,
> so fix that.
>
> Signed-off-by: Cristian Iorga
> ---
> meta/classes/testimage.bbclass | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion
The linux-yocto.inc may remove the meta dir:
do_install_append(){
if [ -n "${KMETA}" ]; then
rm -rf ${STAGING_KERNEL_DIR}/${KMETA}
fi
}
Which may cause the error:
[snip]
find:
`./meta/cfg/kernel-cache/bsp/altera-socfpga/0073-FogBugz-116676-Align-clk.c-with-kernel.o
The following changes since commit 166f2587468ae71988c610858aad3f7ef67eccba:
bison: don't depend on help2man (2015-04-21 11:29:30 +0100)
are available in the git repository at:
git://git.openembedded.org/openembedded-core-contrib rbt/2fixes
http://cgit.openembedded.org/cgit.cgi/openembedd
Fixed:
Assembler messages:
Fatal error: can't create runtime/rtlock.o: No such file or directory
Assembler messages:
Fatal error: can't create runtime/rtdata.o: No such file or directory
Assembler messages:
Fatal error: can't create runtime/vm.o: No such file or directory
Assembler messages:
Fatal
On 21 April 2015 at 16:49, Jussi Kukkonen wrote:
> -Upstream-Status: Submitted [
> https://bugzilla.gnome.org/show_bug.cgi?id=712693]
>
This tag disappears in the updated patch, please add it back.
Ross
--
___
Openembedded-core mailing list
Openembed
Hi All,
In OE, we have three providers for update-alternatives, dpkg, opkg-utils
and chkconfig.
We default to use the following setting in default-providers.inc.
PREFERRED_PROVIDER_virtual/update-alternatives ?= "opkg-utils"
PREFERRED_PROVIDER_virtual/update-alternatives-native ?= "opkg-utils-
On 21 April 2015 at 18:49, Tanu Kaskinen
wrote:
> I'm planning to add a new option to /etc/pulse/client.conf:
> "allow-autospawn-for-root". I'm not sure how to meet the goal of disabling
> that option by default, and enabling it in Sato. I think it could be done
> so that the default version of c
61 matches
Mail list logo
