Re: [yocto] YoctoProject: problem bitbake core-image-minimal
Hi Luca, Thank you for providing a more complete problem report. There are two problems you will need to fix in order for your build to succeed: 1) Don't run the build as the root user. Editing sanity.conf to get rid of the build failure is not the solution to avoid the build failing because it is being invoked as the root user. The correct solution is to create a non-privileged user, login as that user, and run the build as that user. 2) Fix the networking in your VM. It doesn't look like git works from within your VM. Does the "git clone" command work on your host? In any case, performing a build will require your build VM to be able to access the internet in order to perform many downloads. A normal build will invoke git, subversion, and other repository fetches as well as downloading many tarballs. So without networking working properly a build is not possible. Best regards, Trevor On Wed, Oct 26, 2016 at 3:23 AM, Luca Boscariol DEC wrote: > Hi Trevor. > > I'm working in VMware Virtual Machine. > I have installed Open Suse Desktop 12 (SLED 12) (x86_64) > Linux version 3.12.28-4-default > > I'm following: > http://www.yoctoproject.org/docs/2.1/mega-manual/mega-manual.html > > I have installed: > python-2.7.7-2.12.x86_64 > git-2.10.1-318.1.x86_64 > tar-1.27.1-2.22.x86_64 > gcc4.8 > gcc-c++4.8 > make 4.0 > wget 1.14 > python-xml 2.7 > diffstat 1.61 > makeinfo4.13a > python-curses2.7.7 > patch2.7.1 > socat1.7.2.4 > libSDL1.2.15 > > First I have tried to used command: > git clone -b krogoth git://git.yoctoproject.org/poky.git > > but connection refused. > Output is following: > > Cloning into 'poky... > fatal: unable to connect to git.yoctoproject.org: > git.yoctoproject.org[0:140.211.169.56]: errno=Connection refused > > How can I use clone repository? > > > > Next, I have downloaded from > http://downloads.yoctoproject.org/releases/yocto/yocto-2.1.1/poky-krogoth-15.0.1.tar.bz2 > > > Then > tar -xvf poky-krogoth-15.0.1.tar.bz2 > > in /opt directory > > > I have modified file build/conf/local.conf in following mode: > #MACHINE ??= "qemux86" > MACHINE ??= "qemuarm" > > I run script: > source oe-init-build-env > > Output is: > > Shell enviroment set up for builds. ###You can now run 'bitbake > ' > > Common targets are: > core-image-minimal > core-image-sato > meta-toolchian > meta-ide-support > > You can also run generated qemu images with a command like 'runqemu qemux86 > > > > To conserve disk space, I have added in build/conf/local.conf > INHERIT += "rm_work" > > When i run a script: > bitbake core-image-minimal > I have 1 error. > > Output is: > > ERROR: OE-core's config sanity checker detected a potential > misconfiguration. > Either fix the cause of this error or at your own risk disable the checker > (see sanity.conf). > Following is the list of potential problems / advisories: > > Do not use Bitbake as root > > > > > Then, I have modified file /meta/conf/sanity.conf in following mode: > > #INHERIT += "sanity" > #INHERIT += "rm_work" > > > I change directory: > /build > > > I run: > bitbake core-image-minimal > > Output is: > > Parsing recipes: 100% | > > # > > | Time: 00:00:46 > Parsing of 871 .bb files complete (0 cached, 871 parsed). 1301 targets, 66 > skipped, 0 masked, 0 errors. > NOTE: Resolving any missing task queue dependencies > > Build Configuration: > BB_VERSION= "1.30.0" > BUILD_SYS = "x86_64-linux" > NATIVELSBSTRING = "SUSELINUX-12" > TARGET_SYS= "arm-poky-linux-gnueabi" > MACHINE = "qemuarm" > DISTRO= "poky" > DISTRO_VERSION= "2.1.1" > TUNE_FEATURES = "arm armv5 thumb dsp" > TARGET_FPU= "soft" > meta > meta-poky > meta-yocto-bsp= ":" > > NOTE: Fetching uninative binary shim from > http://downloads.yoctoproject.org/releases/uninative/0.95/x86_64-nativesdk-libc.tar.bz2;sha256sum=26d46c61ad88cc245e31c88549717c0092a838d111b93ec169d88b08cc027581 > > > NOTE: Preparing RunQueue > NOTE: Executing SetScene Tasks > NOTE: Executing RunQueue Tasks > ERROR: quilt-native-0.64-r0
[yocto] Package relation between package.manifest and license.manifest
Question: What is the relation between the package.manifest and license.manifest ? After a yocto poky based image has been built there are 2 files in the licenses directory "tmp/deploy/licenses/*image_name-datestamp*" One is the package.manifest, which if understood correctly is a list of all packages included in the image. The second file is the license.manifest, but this one contains besides the package name also the version, recipe name and license of the package. However if I compare the package names in both lists, there seem to be a number of packages in the license.manifest that are not part of the package.manifest. E.g. "readline, popt, expat, freetype". Is the license.manifest a list of all items in the package.manifest + ?build dependencies? or something ? Regards, H.Heutinck -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] [meta-raspberrypi3] Failed to build gstreamer1.0-plugins-bad with minimal configuration
Hi all, I'm currently unable to build gstreamer1.0-plugins-bad with a clean checkout of poky-krogoth and also poky-master with DISTRO_FEATURES_remove = " x11 wayland" It fails during the do_compile() task of gstreamer1.0-plugins-bad with the following error message: undefined reference to graphics_get_display_size(). This function comes with libbcmhost which is however installed with userland in sysroot. In addition, the log.do_configure of gstreamer1.0-plugins-bad detects bcm_host as well. If I change DISTRO_FEATURES_remove = " x11" it will work. I have tested with a minimal configuration & layers: Build Configuration: BB_VERSION= "1.32.0" BUILD_SYS = "x86_64-linux" NATIVELSBSTRING = "Debian-8.2" TARGET_SYS= "arm-poky-linux-gnueabi" MACHINE = "raspberrypi3" DISTRO= "poky" DISTRO_VERSION= "2.2" TUNE_FEATURES = "arm armv7ve vfp thumb neon vfpv4 callconvention-hard cortexa7" TARGET_FPU= "hard" meta meta-poky meta-yocto-bsp= "master:ef627ab364d52fe19994c94c1a78fbe21620a32c" meta-raspberrypi = "master:de016ceef63028f5578191785c50529695f76a1a" meta-oe meta-multimedia = "master:8ba31c9ba214802b1305aabbc0be0353cba0bc3e and simply launched: bitbake -k gstreamer1.0-plugins-bad Has anyone already experienced this issue with raspberrypi3 ? Cheers, Karim -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] how to add files to boot media hddimg/ISO
Hello yocto world
I have a recipe that produce an ISO image and a hddimg image.
I need to add a file to the boot media root, alongside rootfs.img and
intrd - so it is NOT a part of the rootfs
inspired by bootimg.bbclass, I tried to add the following recipe to my build
/DESCRIPTION = "Provide a sektionnumber.dat file on bootmedia (ISO and
hdd)"//
//
//LICENSE = "CLOSED"//
//BRANCH ?= "develop"//
//SRC_URI ="file://sektionnumber.dat;"//
//FILESEXTRAPATHS_prepend := "${THISDIR}/files:" //
//
//do_bootimg_prepend(){//
//install -d ${ISODIR}//
//install -m 0644 "${THISDIR}/files/sektionnumber.dat
${ISODIR}/sektionnumber.dat//
// install -d ${HDDDIR}//
// install -m 0644 "${THISDIR}/files/sektionnumber.dat
${HDDDIR}/sektionnumber.dat//
//}
/but it is not recognized
any suggestions ?
BR Lars
--
Best Regards
Lars Larsen
F.Poulsen Engineering Aps
Tjørnager 16
4330 Hvalsø
Denmark
+45 29802784
www.visionweeding.com
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
[yocto] Release Candidate Build for yocto-2.2.rc6.rc6 now available.
A release candidate build for yocto-2.2.rc6 is now available at: http://autobuilder.yoctoproject.org/pub/releases/yocto-2.2.rc6 Please begin QA on this build as soon as possible. Build hash information: meta-qt4 : fc9b050569e94b5176bed28b69ef28514e4e4553 meta-intel : 8dbd551c1ce6d7124f4bf70030415bda5f154030 meta-minnow : 9c965ef5252e383843d796cd8b50c61b3034b6ae meta-qt3 : f33b73a9563f2dfdfd0ee37b61d65d90197a456f poky : dc8508f609974cc99606b9042bfa7f870ce80228 This is an automated message from The Yocto Project Autobuilder Git: git://git.yoctoproject.org/yocto-autobuilder Email: pi...@toganlabs.com -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] how to add files to boot media hddimg/ISO SOLVED
I manage to solve it, with a not so elegant solution
I any one has an "authorized" solution please let me know
in my local .conf I have
INHERIT += "rootfsdebugfiles"
ROOTFS_DEBUG_FILES += "\
${TOPDIR}/[path to file]/sektionnumber.dat ${ISODIR}/sektionnumber.dat; \
${TOPDIR}/[path to file]/sektionnumber.dat ${HDDDIR}/sektionnumber.dat; \
"
-Lars
On 2016-10-26 15:22, Lars Larsen wrote:
Hello yocto world
I have a recipe that produce an ISO image and a hddimg image.
I need to add a file to the boot media root, alongside rootfs.img and
intrd - so it is NOT a part of the rootfs
inspired by bootimg.bbclass, I tried to add the following recipe to my
build
/DESCRIPTION = "Provide a sektionnumber.dat file on bootmedia (ISO and
hdd)"//
//
//LICENSE = "CLOSED"//
//BRANCH ?= "develop"//
//SRC_URI ="file://sektionnumber.dat;"//
//FILESEXTRAPATHS_prepend := "${THISDIR}/files:" //
//
//
//do_bootimg_prepend(){//
//install -d ${ISODIR}//
//install -m 0644 "${THISDIR}/files/sektionnumber.dat
${ISODIR}/sektionnumber.dat//
// install -d ${HDDDIR}//
// install -m 0644 "${THISDIR}/files/sektionnumber.dat
${HDDDIR}/sektionnumber.dat//
//}
/but it is not recognized
any suggestions ?
BR Lars
--
Best Regards
Lars Larsen
F.Poulsen Engineering Aps
Tjørnager 16
4330 Hvalsø
Denmark
+45 29802784
www.visionweeding.com
--
Best Regards
Lars Larsen
F.Poulsen Engineering Aps
Tjørnager 16
4330 Hvalsø
Denmark
+45 29802784
www.visionweeding.com
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
[yocto] [meta-security][PATCH 2/2] smack kernel: add smack kernel config fragments
Signed-off-by: Armin Kuster
---
recipes-kernel/linux/linux-yocto-4.8/smack-default-lsm.cfg | 2 ++
recipes-kernel/linux/linux-yocto-4.8/smack.cfg | 8
recipes-kernel/linux/linux-yocto_4.8.bbappend | 5 +
3 files changed, 15 insertions(+)
create mode 100644 recipes-kernel/linux/linux-yocto-4.8/smack-default-lsm.cfg
create mode 100644 recipes-kernel/linux/linux-yocto-4.8/smack.cfg
diff --git a/recipes-kernel/linux/linux-yocto-4.8/smack-default-lsm.cfg
b/recipes-kernel/linux/linux-yocto-4.8/smack-default-lsm.cfg
new file mode 100644
index 000..b5c4845
--- /dev/null
+++ b/recipes-kernel/linux/linux-yocto-4.8/smack-default-lsm.cfg
@@ -0,0 +1,2 @@
+CONFIG_DEFAULT_SECURITY="smack"
+CONFIG_DEFAULT_SECURITY_SMACK=y
diff --git a/recipes-kernel/linux/linux-yocto-4.8/smack.cfg
b/recipes-kernel/linux/linux-yocto-4.8/smack.cfg
new file mode 100644
index 000..62f465a
--- /dev/null
+++ b/recipes-kernel/linux/linux-yocto-4.8/smack.cfg
@@ -0,0 +1,8 @@
+CONFIG_IP_NF_SECURITY=m
+CONFIG_IP6_NF_SECURITY=m
+CONFIG_EXT2_FS_SECURITY=y
+CONFIG_EXT3_FS_SECURITY=y
+CONFIG_EXT4_FS_SECURITY=y
+CONFIG_SECURITY=y
+CONFIG_SECURITY_SMACK=y
+CONFIG_TMPFS_XATTR=y
diff --git a/recipes-kernel/linux/linux-yocto_4.8.bbappend
b/recipes-kernel/linux/linux-yocto_4.8.bbappend
index 0e6960e..048e8fd 100644
--- a/recipes-kernel/linux/linux-yocto_4.8.bbappend
+++ b/recipes-kernel/linux/linux-yocto_4.8.bbappend
@@ -5,3 +5,8 @@ SRC_URI += "\
${@bb.utils.contains('DISTRO_FEATURES', 'tpm', ' file://tpm.cfg', '',
d)} \
${@bb.utils.contains('DISTRO_FEATURES', 'tpm', ' file://tpm.scc', '',
d)} \
"
+
+SRC_URI += "\
+${@bb.utils.contains('DISTRO_FEATURES', 'smack', ' file://smack.cfg',
'', d)} \
+${@bb.utils.contains('DISTRO_FEATURES', 'smack', '
file://smack-default-lsm.cfg', '', d)} \
+"
--
2.7.4
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
[yocto] [meta-security][PATCH 1/2] smack: Add new package
Signed-off-by: Armin Kuster
---
recipes-security/smack/files/run-ptest | 3 ++
.../smack/files/smack_generator_make_fixup.patch | 18 ++
recipes-security/smack/smack_1.3.0.bb | 42 ++
3 files changed, 63 insertions(+)
create mode 100644 recipes-security/smack/files/run-ptest
create mode 100644
recipes-security/smack/files/smack_generator_make_fixup.patch
create mode 100644 recipes-security/smack/smack_1.3.0.bb
diff --git a/recipes-security/smack/files/run-ptest
b/recipes-security/smack/files/run-ptest
new file mode 100644
index 000..049a9b4
--- /dev/null
+++ b/recipes-security/smack/files/run-ptest
@@ -0,0 +1,3 @@
+#!/bin/sh
+./tests/make_policies.bash ./tests/generator
+./tests/make_policies.bash ./tests/generator labels
diff --git a/recipes-security/smack/files/smack_generator_make_fixup.patch
b/recipes-security/smack/files/smack_generator_make_fixup.patch
new file mode 100644
index 000..8bafc5e
--- /dev/null
+++ b/recipes-security/smack/files/smack_generator_make_fixup.patch
@@ -0,0 +1,18 @@
+Upstream-Status: Pending
+
+Signed-off-by: Armin Kuster
+
+
+Index: git/tests/Makefile
+===
+--- git.orig/tests/Makefile
git/tests/Makefile
+@@ -4,7 +4,7 @@ clean:
+ rm -rf ./out ./generator
+
+ generator: generator.c
+- gcc -Wall -O3 generator.c -o ./generator
++ ${CC} generator.c -o ./generator
+
+ policies: ./generator ./make_policies.bash
+ ./make_policies.bash ./generator
diff --git a/recipes-security/smack/smack_1.3.0.bb
b/recipes-security/smack/smack_1.3.0.bb
new file mode 100644
index 000..46d305e
--- /dev/null
+++ b/recipes-security/smack/smack_1.3.0.bb
@@ -0,0 +1,42 @@
+DESCRIPTION = "Selection of tools for developers working with Smack"
+HOMEPAGE = "https://github.com/smack-team/smack";
+SECTION = "Security/Access Control"
+LICENSE = "LGPL-2.1"
+
+LIC_FILES_CHKSUM = "file://COPYING;md5=4fbd65380cdd255951079008b364516c"
+
+SRCREV = "478f68d182c5070f510482194d3e097b11c21907"
+SRC_URI = " \
+ git://github.com/smack-team/smack.git;branch=v1.3.x \
+ file://smack_generator_make_fixup.patch \
+ file://run-ptest"
+
+PV = "1.3.0+git${SRCPV}"
+
+inherit autotools pkgconfig systemd ptest
+
+S = "${WORKDIR}/git"
+
+PACKAGECONFIG ??= ""
+PACKAGECONG += "${@bb.utils.contains('DISTRO_FEATURES', 'systemd', 'systemd',
'', d)}"
+
+PACKAGECONFIG[systemd] = "--with-systemdsystemunitdir=DIR"
+PACKAGECONFIG[systemd] =
"--with-systemdsystemunitdir=${systemd_system_unitdir},
--without-systemdsystemunitdir, systemd"
+
+do_compile_append () {
+ oe_runmake -C ${S}/tests generator
+}
+
+do_install_ptest () {
+ install -d ${D}${PTEST_PATH}/tests
+ install ${S}/tests/generator ${D}/${PTEST_PATH}/tests
+ install ${S}/tests/generate-rules.sh ${D}${PTEST_PATH}/tests
+ install ${S}/tests/make_policies.bash ${D}${PTEST_PATH}/tests
+}
+
+FILES_${PN}-ptest += "generator"
+
+RDEPENDS_${PN} += "coreutils"
+RDEPENDS_${PN}-ptest += "make bash bc"
+
+BBCLASSEXTEND = "native"
--
2.7.4
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
[yocto] How to proceed with kernel-fitimage and INITRAMFS_IMAGE
I am using poky Krogoth and try to generate a fitImage including an initramfs. Whatever I try I end up with circular dependendies. My image recipe is based on core-image In my local conf I have the following: KERNEL_CLASSES += "kernel-fitimage" INITRAMFS_IMAGE = "image-recovery" INITRAMFS_IMAGE_BUNDLE = "1" And in my image recipe I tried: EXTRA_IMAGEDEPENDS = "" RDEPENDS_kernel-base = "" But still end up with circular dependencies. What is the correct configuration to be able to build a fitimage with an initramfs included ? And what shall be the bitbake command... the kernel or the image name ? Any suggestions ? -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] Reg porting of CVE-2016-5195 Linux Kernel Local Privilege Escalation (Dirty CoW) to 3.14 kernel
Hi Team, Ref - mm: remove gup_flags FOLL_WRITE games from __get_user_pages() https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=19be0eaffa3ac7d8eb6784ad9bdbc7d67ed8e619 The above issue was recently patched in 4.8 kernel. When are we backporting this to 3.14 ? Can you give us an ETA ? Regards, Anup -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Reg porting of CVE-2016-5195 Linux Kernel Local Privilege Escalation (Dirty CoW) to 3.14 kernel
On 10/26/2016 11:40 AM, Anup Maheshwari (anumahes) wrote: Hi Team, Ref - mm: remove gup_flags FOLL_WRITE games from __get_user_pages() https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=19be0eaffa3ac7d8eb6784ad9bdbc7d67ed8e619 The above issue was recently patched in 4.8 kernel. When are we backporting this to 3.14 ? I am glad you said "we". Does that mean you are willing to send a patch? regards, Armin Can you give us an ETA ? Regards, Anup -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] How to handle meta-intel/openembedded repos with multiple developers
On Thu, Mar 3, 2016 at 8:27 AM, Mark Hatle wrote: > At some point during product development a lead/architect needs to make the > decision to 'freeze' development and at that point everything is > tagged/branched > and only backports are used from them on. (If the number of backports gets > too > large, you MIGHT decide to selectively rebase.) I'm currently trying to figure out with how to control external layers in my Yocto build and found this thread. I'm a little unclear on how to track a release to the version used on non-company layers. Say I'm using poky, meta-openembedded, meta-xilinx and then my own layer, meta-me. When I freeze development and do a release, I can tag meta-me, but because I also treat non-company assets as RO, I shouldn't tag poky, meta-openembedded nor meta-xilinx (or should I? Is this where I use git's lightweight tagging as opposed to annotated tags?) When "everything is tagged/branched", does that somehow include tagging the non-company assets? Thanks for any help. Ed -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] General policies for CVE fixes
> > Yes regressions (forgetting to fix bugs in master) are bad. I believe > > there are other ways to avoid this, Yocto project has a bug reporting > > system to have track of such things, right? > The issue there is if Jethro gets a fix and Krogoth, morty and mater need it > as well, the bug system implies someone else is going to have to do the > work. > That is the problem. Not too many people are stepping up to do the work > in the other branches. > > > > > Maintenance branches are likely deployed in production systems, I > > think Fixing security problems here should have higher priority. > You are more than welcome to submit patches for the stable branch you > are concerned about knowing the patches wont be applied until the > parent branches are addressed first. > > > Don't you agree? > > > > Perhaps we should discuss this at next OEDEM :) > We have and until more people step up to help, this will be a constant > issue. > > -armin I see your point, they are absolutely valid. Thanks. //Sona -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
