[yocto] yocto Digest, Vol 99, Issue 26
Nicolas Dechesne
nicolas.dechesne at linaro.org
Tue Dec 11 22:40:17 PST 2018
On Wed, Dec 12, 2018 at 2:40 AM Mohamed Youseif
<MohamedYouseif at outlook.com> wrote:
>
> I'm asking about how to enable PACKAGECONFIG feature from local.conf file, let's say that i have the following pacakgeconfig in a recipe
> PACKAGECONFIG = " f1 f2 "
> PACKAGECONFIG[f1] = "-DENABLE_f1=ON,-DENABLE_f1=OFF,f1,"
>
> so i need to add line in local.conf file to enable this feature for my image?
> I tried to use the following line to loca.conf but it does not help:
>
> PACKAGECONFIG_pn-<my-recipe-name>_append = "-DENABLE_f1=ON"
It should be:
PACKAGECONFIG_append_pn-<my-recipe-name> = " f1"
e.g. f1 and f2 are the packageconfig options defined by the recipe,
which can be enabled or disabled. "-Dxxx" are CFLAGS that will be
added when each packageconfig option is set or not.
>
> ________________________________
> From: yocto-bounces at yoctoproject.org <yocto-bounces at yoctoproject.org> on behalf of yocto-request at yoctoproject.org <yocto-request at yoctoproject.org>
Please note that you should not be sending email to
yocto-request at yoctoproject.org or yocto-bounces at yoctoproject.org, they
are not valid mailing lists. Sending to yocto at yoctoproject.org is
enough.
> Sent: Tuesday, December 11, 2018 11:57 AM
> To: yocto at yoctoproject.org
> Subject: yocto Digest, Vol 99, Issue 26
>
> Send yocto mailing list submissions to
> yocto at yoctoproject.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
> https://lists.yoctoproject.org/listinfo/yocto
> or, via email, send a message with subject or body 'help' to
> yocto-request at yoctoproject.org
>
> You can reach the person managing the list at
> yocto-owner at yoctoproject.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of yocto digest..."
>
>
> Today's Topics:
>
> 1. Using multilib to build 32-bit glibc on 64-bit target
> platform (Nicholas Tsirakis)
> 2. Raspberry pi with Yocto os sd card is not working with
> Raspbian os sd card (AKASH BHARDWAJ)
> 3. Do rootfs fail when switch from rpm to deb (Jonas Andersson)
> 4. Lib update (Peter Balazovic)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Mon, 10 Dec 2018 15:37:19 -0500
> From: Nicholas Tsirakis <niko.tsirakis at gmail.com>
> To: yocto at yoctoproject.org
> Subject: [yocto] Using multilib to build 32-bit glibc on 64-bit target
> platform
> Message-ID:
> <CAFqpmVLj_54Ou1N=+YdjAqtcGGDLsWoH-85+89nQ=NJLUhPDpA at mail.gmail.com>
> Content-Type: text/plain; charset="utf-8"
>
> Hello,
>
> I'm having trouble understanding the proper usage of multilib within the
> Yocto project. I've read through Yocto's documentation, but I think I am
> missing something crucial. Here are the steps I've taken:
>
> 1. Added the following to my local.conf:
> require conf/multilib.conf
> MULTILIBS = "multilib:lib32"
> DEFAULTTUNE_virtclass-multilib-lib32 = "x86"
>
> 2. Attempted to build lib32-glibc with bitbake. Received the following
> errors for lib32-glib-initial (shortened for brevity):
>
> | <stdin>:10:36: error: 'REG_RBP' undeclared (first use in this function)
> | <stdin>:9:26: note: in expansion of macro 'ucontext'
> | <stdin>:10:20: note: in expansion of macro 'mcontext'
> | <stdin>:11:61: note: in expansion of macro 'mreg'
> | <stdin>:10:36: note: each undeclared identifier is reported only once for
> each function it appears in
> | <stdin>:9:26: note: in expansion of macro 'ucontext'
> | <stdin>:10:20: note: in expansion of macro 'mcontext'
> | <stdin>:11:61: note: in expansion of macro 'mreg'
> | <stdin>:10:36: error: 'REG_RSP' undeclared (first use in this function)
> | <stdin>:9:26: note: in expansion of macro 'ucontext'
> | <stdin>:10:20: note: in expansion of macro 'mcontext'
> | <stdin>:12:61: note: in expansion of macro 'mreg'
> ...
> | <stdin>:5:73: error: 'La_x86_64_xmm' undeclared (first use in this
> function)
> ...
> | <stdin>:10:87: error: invalid use of undefined type 'struct
> La_x86_64_regs'
> ...
>
> 3. At this point it appeared to me like it was attempting to build a 64-bit
> version of glibc in a 32-bit environment, so I tried building the
> lib32-linux-libc-headers by adding the following to its recipe:
>
> do_install_prepend() {
> if [ "${MLPREFIX}" == "lib32-" ]; then
> ARCH="x86"
> fi
> }
>
> This was more a shot in the dark than anything else and still yielded the
> same result. Can someone clear up the proper usage of multilib and tell me
> if I'm doing something wrong? Please note that my project currently uses
> OE's pyro branches.
>
> Thank you for your time.
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: <http://lists.yoctoproject.org/pipermail/yocto/attachments/20181210/bef1ca7f/attachment-0001.html>
>
> ------------------------------
>
> Message: 2
> Date: Tue, 11 Dec 2018 07:57:35 +0530
> From: AKASH BHARDWAJ <akash12bhardwaj at gmail.com>
> To: yocto at yoctoproject.org
> Subject: [yocto] Raspberry pi with Yocto os sd card is not working
> with Raspbian os sd card
> Message-ID:
> <CALYZMn=_AhWPbX1Hx=7o=mhoGEU==jnCBJhiQ0v5Y6gL4f0H9A at mail.gmail.com>
> Content-Type: text/plain; charset="utf-8"
>
> Few months ago,I built an custom image for Raspberrypi using Yocto
> Project,flashed it in a sd card and was able to boot
> raspberrypi.Presently,I am trying to use a different sd card with raspbian
> os in same Raspberrypi.But it is not able to boot Raspberrypi.How can I
> rectify this problem?This is my code which I used few years back to
> generate yocto image.
>
>
>
>
>
>
>
>
>
>
> PACKAGE_CLASSES ?= "package_rpm package_deb"
> >
> >
> > EXTRA_IMAGE_FEATURES ?= "debug-tweaks dbg-pkgs dev-pkgs tools-sdk
> > tools-debug eclipse-debug "
> >
> >
> > USER_CLASSES ?= "buildstats image-mklibs image-prelink"
> >
> >
> >
> >
> > BB_DISKMON_DIRS ??= "\
> > STOPTASKS,${TMPDIR},1G,100K \
> > STOPTASKS,${DL_DIR},1G,100K \
> > STOPTASKS,${SSTATE_DIR},1G,100K \
> > STOPTASKS,/tmp,100M,100K \
> > ABORT,${TMPDIR},100M,1K \
> > ABORT,${DL_DIR},100M,1K \
> > ABORT,${SSTATE_DIR},100M,1K \
> > ABORT,/tmp,10M,1K"
> >
> >
> >
> >
> >
> > CONF_VERSION = "1"
> > MACHINE = "raspberrypi3"
> > PREFERRED_VERSION_linux-raspberrypi = "4.%"
> > DISTRO_FEATURES_remove = "x11 wayland"
> > DISTRO_FEATURES_append = " systemd"
> > VIRTUAL-RUNTIME_init_manager = "systemd"
> > IMAGE_INSTALL_append = " git apt dpkg opkg rpm sudo wiringpi wiringpi-dev
> > connman connman-client tzdata i2c-tools i2c-tools-dev glibc-utils rpm
> > dhcp-server bluez5 python-smbus bridge-utils hostapd apache2 openvpn
> > iptables nano"
> > IMAGE_INSTALL += "wiringpi"
> > ENABLE_UART="1"
> > ENABLE_SPI_BUS= "1"
> > ENABLE_I2C = "1"
> >
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: <http://lists.yoctoproject.org/pipermail/yocto/attachments/20181211/d89aff52/attachment-0001.html>
>
> ------------------------------
>
> Message: 3
> Date: Tue, 11 Dec 2018 10:10:29 +0100
> From: Jonas Andersson <jonaskgandersson at gmail.com>
> To: yocto at yoctoproject.org
> Subject: [yocto] Do rootfs fail when switch from rpm to deb
> Message-ID:
> <CAKpuFdeEtgn9SFt6OsTca7zHFKDc32ORmbn69EO01P+YdybVDw at mail.gmail.com>
> Content-Type: text/plain; charset="utf-8"
>
> Hi
>
> We have an recipe based on microservicebus-node npm package created with
> devtool.
>
> When we build with PACKAGE_CLASSES = "package_rpm" it builds but when
> switching to package_deb do_rootfs fails.
> What can I do to get more information about the packages that is reported
> as broken, are there any known issues with npm and deb?
>
> Here is my build output
> _______________________________________________________________________________________________________
> Build Configuration:
> BB_VERSION = "1.38.0"
> BUILD_SYS = "x86_64-linux"
> NATIVELSBSTRING = "universal"
> TARGET_SYS = "arm-poky-linux-gnueabi"
> MACHINE = "raspberrypi3"
> DISTRO = "poky"
> DISTRO_VERSION = "2.5.1"
> TUNE_FEATURES = "arm armv7ve vfp thumb neon vfpv4
> callconvention-hard cortexa7"
> TARGET_FPU = "hard"
> meta
> meta-poky
> meta-yocto-bsp = "sumo:36d5cee56bd389ecbe66dbfad9e5d57c13b56b95"
> meta-oe = "sumo:2bb21ef27c4b0c9d52d30b3b2c5a0160fd02b966"
> meta-microservicebus
> meta-example-msb-rpi = "dev:be586f405a92a563ff49b8adf9ef7a9da5cc7192"
> meta-raspberrypi = "sumo:2d40b000021bc8a9ef7f329ed0ad410f8d227b97"
> meta-rauc = "sumo:40a5890478a50ad80e404be5d9de197dd9a79d44"
>
> NOTE: Executing SetScene Tasks
> NOTE: Executing RunQueue Tasks
> NOTE: Running task 2864 of 3398
> (/home/jonas/git/devtool/meta-microservicebus-node/meta-example-msb-rpi/recipes-core/images/msb-image-rauc.bb:
> do_rootfs)
> NOTE: recipe msb-image-rauc-1.0-r0: task do_rootfs: Started
> ERROR: msb-image-rauc-1.0-r0 do_rootfs: Unable to install packages. Command
> '/home/jonas/git/devtool/build-deb/tmp/work/raspberrypi3-poky-linux-gnueabi/msb-image-rauc/1.0-r0/recipe-sysroot-native/usr/bin/apt-get
> install --force-yes --allow-unauthenticated microservicebus-node
> packagegroup-core-boot psplash-raspberrypi packagegroup-base-extended
> packagegroup-core-ssh-openssh run-postinsts' returned 100:
> Reading package lists...
> Building dependency tree...
> Reading state information...
> Some packages could not be installed. This may mean that you have
> requested an impossible situation or if you are using the unstable
> distribution that some required packages have not yet been created
> or been moved out of Incoming.
> The following information may help to resolve the situation:
>
> The following packages have unmet dependencies:
> microservicebus-node : Depends: microservicebus-node-npm but it is not
> going to be installed
> Depends: microservicebus-node-npm-JSONStream but it
> is not installable
> Depends:
> microservicebus-node-npm-JSONStream-jsonparse but it is not installable
> Depends:
> microservicebus-node-npm-JSONStream-through but it is not installable
> E: Unable to correct problems, you have held broken packages.
>
> ERROR: msb-image-rauc-1.0-r0 do_rootfs: Function failed: do_rootfs
> ERROR: Logfile of failure stored in:
> /home/jonas/git/devtool/build-deb/tmp/work/raspberrypi3-poky-linux-gnueabi/msb-image-rauc/1.0-r0/temp/log.do_rootfs.7424
> NOTE: recipe msb-image-rauc-1.0-r0: task do_rootfs: Failed
> ERROR: Task
> (/home/jonas/git/devtool/meta-microservicebus-node/meta-example-msb-rpi/recipes-core/images/msb-image-rauc.bb:do_rootfs)
> failed with exit code '1'
> NOTE: Tasks Summary: Attempted 3391 tasks of which 3390 didn't need to be
> rerun and 1 failed.
> _______________________________________________________________________________________________________
>
> /Jonas
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: <http://lists.yoctoproject.org/pipermail/yocto/attachments/20181211/ab6fe374/attachment-0001.html>
>
> ------------------------------
>
> Message: 4
> Date: Tue, 11 Dec 2018 10:57:14 +0100
> From: Peter Balazovic <balazovic.peter at gmail.com>
> To: Yocto list discussion <yocto at yoctoproject.org>,
> eclipse-yocto at yoctoproject.org
> Subject: [yocto] Lib update
> Message-ID:
> <CAFq4t4jdGXQnytzXjW-Op=NVdy1s1yAO=U6v9G8NXGd-OX4F0w at mail.gmail.com>
> Content-Type: text/plain; charset="utf-8"
>
> I am developing library (set of libraries) which at first are built and
> part of build image & my SDK.
> Now I would need to update the libs so SDK and as well target remote image
> are updated. I want to avoid rebuild whole image and flash SD-Card again
> and generated SDK over again. I use SDK cross-compiler, Eclipse, ADT plugin
> to develop cmake-based application.
> What is the correct procedure?
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: <http://lists.yoctoproject.org/pipermail/yocto/attachments/20181211/84c549da/attachment.html>
>
> ------------------------------
>
> --
> _______________________________________________
> yocto mailing list
> yocto at yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
>
>
> End of yocto Digest, Vol 99, Issue 26
> *************************************
> --
> _______________________________________________
> yocto mailing list
> yocto at yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
More information about the yocto
mailing list