Re: [yocto] advice on recipe for shared lib mDNSResponder

On 27 September 2017 at 23:58, Steve Pavao wrote: > I am fairly new to Yocto, yet have been able to successfully add a custom > kernel object to my Yocto poky build, no problem. However, I am having > some difficulty adding a shared library, namely mDNSResponder. > Andre has already replied wit

Re: [yocto] Problems when adding custom layer

On 2 October 2017 at 16:55, Aaron Sarginson wrote: > When added, I receive parsing errors at the inherit “systemd” line. > No quotes needed, just: inherit systemd Ross -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/l

Re: [yocto] pkg-config search directories

On 3 October 2017 at 15:13, eliya@gmail.com wrote: > Hi all, > I am new to the Yocto project. > Is this the Yocto forum ? > I would like configure pkg-config search directories but, the program > configured from the sysroots file system, so it does not see Host > environment variables. > i.e

Re: [yocto] pkg-config search directories

You don't need to, it will search the host. Ross On 3 October 2017 at 15:54, eliya@gmail.com wrote: > Hi Ross, > how to configure use of pkg-config-native ? > > On Tue, Oct 3, 2017 at 5:51 PM, Burton, Ross > wrote: > >> On 3 October 2017 at 15:13, eliya@g

Re: [yocto] pkg-config search directories

; build/tmp/sysroots/x86_64-linux/usr/bin/pkg-config > > How do I change that ? > > On Tue, Oct 3, 2017 at 6:02 PM, Burton, Ross > wrote: > >> You don't need to, it will search the host. >> >> Ross >> >> On 3 October 2017 at 15:54, eliya@gmail.com

Re: [yocto] pkg-config search directories

On 3 October 2017 at 16:36, eliya@gmail.com wrote: > Thanks Ross, > That is the issue : default pkg-config does not search host paths - How to > edit its search paths ? > "If you *really* want to link against host binaries and not building your own native recipes for it then see qemu.inc for

Re: [yocto] u-boot recipe: Missing dependencies

On 3 October 2017 at 18:15, Eric Schwarz wrote: > DEPENDS += "bc-native dtc-native" > +DEPENDS_append = " python-native" > +DEPENDS_append_x86-64 = " iasl-native swig-native" > Don't _append when you can just extend the assignment above. Depending on python-native does nothing as the binary is

Re: [yocto] Having trouble getting recipe to run in proper directory

On 5 October 2017 at 18:51, Greg Wilson-Lindberg wrote: > ERROR: configure failed > Unknown argument --build=x86_64-linux > > so bitbake is including an option that the configure script doesn't > understand. Is there a way to delete that option > If configure doesn't recognise that option then i

Re: [yocto] pkg-config search directories

ble > No package 'gl' found > > not found > from /home/wzbwjj/vpm/GR_Yocto/build/tmp/work/corei7-64-poky- > linux/glmark2/2014.03+AUTOINC+fa71af2dfa-r0/git: The configuration failed > > > Thanks! > > > > On Tue, Oct 3, 2017 at 6:40 PM, Burton, Ross &

Re: [yocto] [meta-gplv2][pyro] Fast-forward to master?

On 5 October 2017 at 23:01, Andre McCurdy wrote: > On Thu, Oct 5, 2017 at 1:46 PM, Peter Kjellerstedt > wrote: > > I would like to suggest fast-forwarding the pyro branch of > > meta-gplv2 to master. The only change that I see as questionable > > is the change to mc, but since the change was acc

Re: [yocto] u-boot recipe: Missing dependencies

On 8 October 2017 at 18:04, Eric Schwarz wrote: > Don't _append when you can just extend the assignment above. >> > > I just did it that way for the moment since I wanted to circumvent merge > conflicts when I upgrade the underlying recipes from openembedded. Well it's ugly, so if you want a pa

Re: [yocto] errors in recipe after move from devtool

On 10 October 2017 at 17:34, Greg Wilson-Lindberg wrote: > So to continue, what is the problem with symlinked libraries in a non-dev > package, don't most libraries have syslink's to them? > Typically: libfoo.so -> libfoo.so.1 libfoo.so.1 -> libfoo.so.1.2 libfoo.so.1.2 is a real file In this c

Re: [yocto] Basic question: "core-image-minimal" v.s "core-image-base" ?

On 9 October 2017 at 16:08, Jerry Lian wrote: > Hi, all: > > I have a basic question: how to tell the difference between > "core-image-minimal" and "core-image-base"? > * If we look at file* \poky\meta\recipes-core\images\core-image-base.bb > * > ===

Re: [yocto] How to use same user in two recipes?

Both of your recipes will need to depend on the user-creating recipe. Ross On 11 October 2017 at 07:45, Fabien Lahoudere < fabien.lahoud...@collabora.co.uk> wrote: > On Tue, 2017-10-10 at 15:31 -0700, aaron_wri...@selinc.com wrote: > > > Hi > > > > I want to use the same user in two different re

Re: [yocto] How to use same user in two recipes?

-native', > 'gnu-config-native', 'automake-native', 'mpfr-native', 'autoconf-native', > 'opkg-utils', 'attr', 'gettext-minimal-native', 'flex-native', > 'bison-native', 'm4-native&#x

Re: [yocto] How to use same user in two recipes?

For this you definitely want DEPENDS. Read the do_prepare_sysroot log to for the recipe you're building, it might have an error that isn't causing the build to fail. Ross On 11 October 2017 at 11:18, Fabien Lahoudere < fabien.lahoud...@collabora.co.uk> wrote: > On Wed, 2017-10-11 at 13:06 +0300

Re: [yocto] customising custom-image-sato

If you want a custom core-image-sato then the easiest (and right) thing to do is to write a new image recipe. Then you get to pick what you want in it and don't want in it. puzzles comes in via packagegroup-x11-sato-games, via -x11-sato (which also depends on -x11-sato-base and -x11-sato-apps)..

Re: [yocto] Plain package isn't built for alsa-lib in Poky

Note that the alsa-lib package doesn't actually put the library alsa-lib but the libasound package, the alsa-lib package could not exist (or for most recent releases, it exists but only contains card data files). So if you're depending on alsa-lib to get the library then that's not the right name.

Re: [yocto] rocko: QA issue with glibc-locale

On 19 October 2017 at 12:10, Belisko Marek wrote: > I'm using latest origin/rocko > (65d23bd7986615fdfb0f1717b615534a2a14ab80) with no change to build > beaglebone core-image-minimal. While build I got this QA error: > > ERROR: glibc-locale-2.26-r0 do_package: QA Issue: glibc-locale: > Files/dire

Re: [yocto] rocko: QA issue with glibc-locale

; > On Thu, Oct 19, 2017 at 9:15 PM, Burton, Ross > wrote: > >> On 19 October 2017 at 12:10, Belisko Marek > wrote: > >>> > >>> I'm using latest origin/rocko > >>> (65d23bd7986615fdfb0f1717b615534a2a14ab80) with no change to build > >

Re: [yocto] OpenEmbedded sole base meta layer and poky base meta layers in sync, or not (should be The Same meta base layer, used in different distros)???

On 23 October 2017 at 10:08, Zoran Stojsavljevic < zoran.stojsavlje...@gmail.com> wrote: > > Or better yet use > > http://www.yoctoproject.org/docs/2.3.2/mega-manual/mega-ma > nual.html#ref-classes-image-buildinfo > > Since I am also (relatively) new to YOCTO, reading these emails makes me > think

Re: [yocto] OpenEmbedded sole base meta layer and poky base meta layers in sync, or not (should be The Same meta base layer, used in different distros)???

On 23 October 2017 at 12:39, Zoran Stojsavljevic < zoran.stojsavlje...@gmail.com> wrote: > > poky is generated using combo-layer, which effectively cherry-picks > commits from the parent repositories (in this case bitbake, > > oe-core, meta-poky, meta-yocto-bsp). This explains why the SHAs don't

Re: [yocto] Adding usb-modeswitch and minicom packages on yocto

On 24 October 2017 at 05:16, vishal ashapur wrote: > Hi > I want to add USB modeswitch and minicom packages on the target image. I > am using raspberry pi 3 for the same. How to add those two packages so that > they are enabled on target machine. > > Find the recipes you're after using the layer

Re: [yocto] rocko: QA issue with glibc-locale

On 24 October 2017 at 10:25, Belisko Marek wrote: > Probably. Should I fill some bugzilla somewhere? Rocko should be > released in few days (if not yet already) and this issue can be really > annoying ;) > There's already a bug: https://bugzilla.yoctoproject.org/show_bug.cgi?id=12265 Ross -- _

Re: [yocto] [PATCH] poky: LICENSE in packagegroup makes no sense - removed

On 30 October 2017 at 16:02, Khem Raj wrote: > On Mon, Oct 30, 2017 at 6:51 AM, Robert Berger > wrote: > > > > Signed-off-by: Robert Berger > > --- > > meta/recipes-core/packagegroups/nativesdk-packagegroup-sdk-host.bb | 1 > - > > 1 file changed, 1 deletion(-) > > > > diff --git > > a/meta/re

Re: [yocto] about add python3 modules

Hi, 1.7.1 is pretty old, there were some packaging problems. Try adding python3-misc to the image too. If that doesn't work, use 'oe-pkgdata-util list-pkg-files -r python3' to list all the files built by the python3 recipe and to find out what files are missing. Ross On 30 October 2017 at 20:3

Re: [yocto] Bitwise Operations in BBClass

That would be https://bugzilla.yoctoproject.org/show_bug.cgi?id=11314, $(( isn't supported by our shell parser. Shouldn't be that difficult to fix in bitbake. Ross On 31 October 2017 at 11:27, Ayoub Zaki wrote: > Hello, > > I'm trying to get a bitwise operation working in a bitbake bblcass > fu

Re: [yocto] Bitwise Operations in BBClass

Two options: 1) fix the bug 2) write the logic in a Python function On 31 October 2017 at 11:38, Ayoub Zaki wrote: > Hi, > > > On 31.10.2017 12:34, Burton, Ross wrote: > >> That would be https://bugzilla.yoctoproject.org/show_bug.cgi?id=11314, >> $(( isn'

Re: [yocto] Using site.conf

On 31 October 2017 at 14:15, Michael Habibi wrote: > Is there an example of this somewhere? I haven't had any luck in > documentation or example code to see how to make the site.conf be used. > > site.conf is loaded if it is present in a conf/ directory anywhere. I have a meta-ross which contain

Re: [yocto] ptest - single package

On 31 October 2017 at 21:51, Dave Cobbley wrote: > Hey, > > I am trying to add a single ptest to my image without adding all ptests > from all other packages in my distro. > > https://wiki.yoctoproject.org/wiki/Ptest only has instructions to add > ptest-pkgs, but this is too large for my embedded

Re: [yocto] Checking for xwayland

On 1 November 2017 at 15:58, Adam Lee wrote: > Thanks Fabien, I definitely don't have Xwayland in my rootfs. My manifest > is missing xserver-xorg-xwayland as well. > > Which image are you using? I thought including of "x11 wayland" was > sufficient. Perhaps not..? > > Are you refering to DISTRO

Re: [yocto] Debugging a build issue in an isolated enviroment

On 1 November 2017 at 17:38, Alan Martinovic wrote: > Is there a way to run the above listed make command with the same > environment as it is run when the error is produced? > $ bitbake -c devshell This drops you in a new terminal with the same environment that bitbake sets up, and in ../temp

Re: [yocto] Debugging a build issue in an isolated enviroment

The patching is done by a bbclass (patch.bbclass) and helper modules (meta/oe/lib/patch.py), so you can't execute it like a shell task (such as do_compile). Ross On 2 November 2017 at 11:05, Alan Martinovic wrote: > Thanks for the suggestions > Am currently implementing both of them and am tryi

Re: [yocto] Debugging a build issue in an isolated enviroment

the devshell to debug why the patch hasn't been > correctly applied. > > The answer you gave help for debugging actual build and configure problems. > Debugging patching seems to be out scope for this thread. > Will start a new one. > > > On Thu, Nov 2, 2017 at 12:13 PM

Re: [yocto] Debugging a build issue in an isolated enviroment

On 2 November 2017 at 13:31, Alan Martinovic wrote: > Found what I was asking for with: > > bitbake -e > > going through the output, there are mentions of patch_do_patch(). > I've traced it to meta/classes/patch.bbclass. > > However, trying to execute just the patching for the recipe doesn't wor

Re: [yocto] Annoying "rerun to fix" bug for bitbake: task failed, but rerun can fix it.

On 8 November 2017 at 15:49, Jerry Lian wrote: > I am not sure whether it is a bug or an error: > * Quite often, bitbake will fail before finishing, with message like: ... > task failed with exit code 1... > * But if you rerun bitbake, it will continue to build. > * So sometimes I have to rerun m

Re: [yocto] Annoying "rerun to fix" bug for bitbake: task failed, but rerun can fix it.

The autobuilder does about 50 builds a night using pure poky and we don't see this, so again: what recipe and what errors? Ross On 8 November 2017 at 16:22, Jerry Lian wrote: > I am not talking about my own layer or recipe. > It happens even when I run the demo QEMU/beaglebone builds. > (I just

Re: [yocto] yocto documentation: no content, no PDF?

On 8 November 2017 at 15:41, Jerry Lian wrote: > Just wondering: > * As an active project, why yocto documentation does not provide a content > (better be clickable)? > The megamanual (Complete Documentation) doesn't have a top-level table of contents as that basically exists to search globally.

Re: [yocto] Annoying "rerun to fix" bug for bitbake: task failed, but rerun can fix it.

60%, 80% > * And the failure last time may not appear next time. > * So it just pop-up randomly > > (By the way, I just build brand new PC with 16 threads CPU, 32G memory, > and install Ubuntu 16.4.3 with ESXI-6.5) > (so really confused) > > > > On Wed, Nov 8, 2017 at 11:24 A

Re: [yocto] Annoying "rerun to fix" bug for bitbake: task failed, but rerun can fix it.

! > Do you mean the random failure also help you for debugging? > > > > > On Wed, Nov 8, 2017 at 11:33 AM, Burton, Ross > wrote: > >> Well next time it happens feel free to reply to this thread. Otherwise >> you're asking us "fix my problem"

Re: [yocto] Annoying "rerun to fix" bug for bitbake: task failed, but rerun can fix it.

On 8 November 2017 at 16:41, Ayoub Zaki wrote: > (By the way, I just build brand new PC with 16 threads CPU, 32G > >> memory, and install Ubuntu 16.4.3 with ESXI-6.5) >> >> > Do you have a Ryzen 7 based CPU ?! > > In this case Ubuntu 16.4 with Linux kernel 4.4.x is know to be broken > You

Re: [yocto] yocto documentation: no content, no PDF?

On 8 November 2017 at 16:45, Jerry Lian wrote: > The mega-manual should have content like: at least one line for each > chapter, so that we can have a big picture. > > By the way, where is the "real docs"? > > https://www.yoctoproject.org/documentation Ross -- __

Re: [yocto] apt-get

Set PACKAGE_CLASSES to package_deb, and then ensure IMAGE_FEATURES includes package-management. Ross On 8 November 2017 at 19:16, Ran Shalit wrote: > Hello, > > Is there a way to add "apt-get" command (and package manager) in yocto ? > > Thank you, > Ran > -- > _

Re: [yocto] apt-get

quot;?=" means that it shall be defined only if not defined previously, > so if it is already defined as package_rpm , it might not install > package_ipk? > Doesn't it mean that "opkg" might be installed without the required > package_ipk ? > > Thank yo

Re: [yocto] apt-get

, only rpm command. > > Regards, > Ran > > On Thu, Nov 9, 2017 at 1:25 PM, Burton, Ross > wrote: > > (adding yocto@ back to CC) > > > > I don't know where you saw that but that is very wrong. > > > > Set PACKAGE_CLASSES to the package mana

Re: [yocto] Bitbake fails when enabling tools-testapps

On 12 November 2017 at 08:18, Chris Hughes <89dra...@gmail.com> wrote: > - nothing provides at needed by ltp-20170116-r0.corei7_64 > Well at is part of oe-core so that should have been built. "bitbake at" to see why, or if that works then rebuilding your image should work (although it really s

Re: [yocto] libnetconf 0.9.0 configuring error in yocto pyro 2.3

On 15 November 2017 at 12:03, Amit Gondaliya wrote: > *ERROR: /usr/bin/xml2-config should not be used, use an alternative such > as pkg-config* > > > > *ERROR: /usr/bin/xslt-config should not be used, use an alternative such as > pkg-config*does anybody know how to patch configuration.ac file to

Re: [yocto] How to build a native python extension

inherit native to make the recipe native. Ross On 20 November 2017 at 11:33, cddatemp wrote: > Hi, > > I add "inherit distutils" in my recipe. > It will make my recipe depends on "python-native" and "python". > Finally it use arm-gcc to build the python extension. > But I want to use x86-gcc to

Re: [yocto] Build Issue in pyro 2.3

A good start would be to remove the inherits you don't need such as autotools-brokensep. And the empty do_configure() do_compile() functions. You're not telling install where to install which is why the files are going into the sysroot and not packaged up. Just delete your do_install() and let the

Re: [yocto] How to build a native python extension

There's numerous u-boot recipes out there, including on in oe-core. Ideally customise the u-boot in oe-core instead of writing your own recipe from scratch. Ross On 20 November 2017 at 12:07, cddatemp wrote: > At 2017-11-20 19:35:31, "Burton, Ross" wrote: > > inherit n

Re: [yocto] Build is using host x86_64 python2.7 instead of cross-compiled

During the build it wont/can't use the target python as that won't be compatible (say x86-64 host, ARM target). This isn't a problem. Ross On 20 November 2017 at 14:52, Amit Gondaliya wrote: > Hello All, > > > I am configuring one package and found the following error. > > > > > > > > > * File

Re: [yocto] [libfakekey] Missing new version releases in yocto repository

There are tags in git so I'd recommend building from the 0.3 tag instead of a tarball. I'll make a note to try and roll a release this week. Ross On 19 November 2017 at 22:11, Petr Cvek wrote: > Hello, > > I was playing with libfakekey and I've found the source repository at > > http://downloa

Re: [yocto] Makefile library and debian naming

You don't need to inherit debian in a recipe, that is meant to be a distro-level inherit (and is inherited out of the box). Deleting the .so breaks non-static linking as that is the file which is used to link against, so don't delete it. It should be in the -dev package. The QA error is probably

Re: [yocto] Makefile library and debian naming

e is written by myself. The library is built as follow: >> $(SHARED_OUT_DIR)/%.o: %.c >> $(CC) $(CFLAGS) -fPIC -c -o $@ $< >> >> $(SHARED_OUT_DIR)/$(SHARED_LIB_NAME): $(SHARED_OBJS) >> $(CC) -shared $(LDFLAGS) $(SHARED_OBJS) -o $@ >> >> What do you mean with "lack

Re: [yocto] Contribute meta-installer to yocto

On 21 November 2017 at 08:55, Hongxu Jia wrote: > If yocto is interested in this layer and will accept it, > I could send pull request or some one directly fetch > from above github master branch. Are you asking for a git repo on git.yoctoproject.org? If you want one I believe the process is t

Re: [yocto] BKM for Importing Python Modules

Python functions in classes are executed by the Python that is executing bitbake, which doesn't have access to the modules in the native sysroot (and won't, as any compiled modules in there are linked against the native python, not the host python). You can solve this by either mandating python-cr

Re: [yocto] BKM for Importing Python Modules

On 30 November 2017 at 16:42, wrote: > "Burton, Ross" wrote on 11/30/2017 02:47:43 AM: > > Python functions in classes are executed by the Python that is > > executing bitbake, which doesn't have access to the modules in the > > native sysroot (and won

Re: [yocto] [PATCH] yocto: matchbox-window-manager-2: Makefile with spaces instead of a tab refuses to compile

This patch was corrupted because you copied/pasted it into Thunderbird instead of using git-send-email, but I applied it by hand. Ross On 19 November 2017 at 19:58, Petr Cvek wrote: > A wrong spacing in Makefile.am generates a Makefile which will refuse > to compile. This patch fixes it. > > Si

Re: [yocto] Morty Branch: Error in building core-image-sato | matchbox-panel recipe

gdk-x11 is part of the gtk+3 recipe, which is a dependency of matchbox-desktop. matchbox-desktop needs X11, so has your BSP disabled X11? Ross On 8 December 2017 at 03:02, Gunasekaran Srinivasan < gunaseka...@solitontech.com> wrote: > Hi all, > > I am trying to build core-image-sato image with

Re: [yocto] Morty Branch: Error in building core-image-sato | matchbox-panel recipe

ed by default. Can you tell how to enable in > conf/local.conf file? > > Thanks, > Guna > > On Fri, Dec 8, 2017 at 3:54 PM, Burton, Ross > wrote: > >> gdk-x11 is part of the gtk+3 recipe, which is a dependency of >> matchbox-desktop. matchbox-desktop needs X11, s

Re: [yocto] Morty Branch: Error in building core-image-sato | matchbox-panel recipe

Guna > > On Fri, Dec 8, 2017 at 4:11 PM, Burton, Ross > wrote: > >> I'm surprised it go that far as libx11 should have refused to build if X >> was disabled. To enable X: >> >> DISTRO_FEATURES_append = " x11" >> >> Ross >> &g

Re: [yocto] [PATCH 09/12] upgradehelper.py: use git user in commit when recipes are specified

On 8 December 2017 at 14:07, Alexander Kanavin < alexander.kana...@linux.intel.com> wrote: > On 12/08/2017 03:51 AM, Robert Yang wrote: > > I'm not sure about this one. Commits shouldn't be created automatically on >>> a person's behalf and then also signed-off - I'd say you need to first look >>>

Re: [yocto] [meta-gplv2][PATCH 0/3] Consolidated re-send of previously submitted patches

Merged to master, sorry for the delay. The gnutls one was already merged locally but I forgot to push... Ross On 18 December 2017 at 22:08, Andre McCurdy wrote: > Andre McCurdy (2): > gnutls: update 3.3.27 -> 3.3.28 > elfutils_0.148: musl build fixes > > Phong Tran (1): > gettext: fix co

Re: [yocto] call custom sh script in do_compile

On 20 December 2017 at 09:08, Mircea Gliga wrote: > Hello > > I have a build.sh script used to build outside yocto, after sourcing the > build environment. > I want to use the same build.sh script inside the recipe, in the > do_compile task, something like: > > do_compile () { > > ./build.sh ${M

Re: [yocto] rfkill cannot open control device

On 20 December 2017 at 10:18, Zoran Stojsavljevic < zoran.stojsavlje...@gmail.com> wrote: > > IMAGE_INSTALL_append += "rfkill" (my best guess, easiest way). > > My bad! :-( > > Should read: IMAGE_INSTALL_append += "Bluez5" > Typo in the package name, no need to use += with _append, and missing wh

Re: [yocto] Rocko and Circular Dependencies

Nobody else has seen this as far as I'm aware, and the autobuilder doesn't see it. Is that a pure oe-core/bitbake or Poky, or do you have custom layers? Can you replicate with a stock configuration? On 20 December 2017 at 03:02, Barry Grussling wrote: > Hello all, > > I am trying to move one o

Re: [yocto] rfkill cannot open control device

On 20 December 2017 at 10:30, Zoran Stojsavljevic < zoran.stojsavlje...@gmail.com> wrote: > > IMAGE_INSTALL_append = " bluez5" > > I see. > > This should be the another way, should'n it? > > CORE_IMAGE_EXTRA_INSTALL += "bluez5" > If you're using core-image then that's the preferred way, yes. Ros

Re: [yocto] rfkill cannot open control device

On 20 December 2017 at 12:09, Sherif Omran wrote: > this does not solve the issue so far. It seems a package installed by > rpi-basic-image does the trick. > > what is the difference between : > > core-image-minimal > rpi-basic-image > I've never used meta-raspberrypi but you can just look at t

Re: [yocto] call custom sh script in do_compile

On 20 December 2017 at 12:19, Mircea Gliga wrote: > > Let's put it the other way around. Does anyone know a recipe that uses an > shell script to build something (which must set the environment correctly > and call make itself) ? > I can't see the difficulty. Tasks are shell scripts by default,

Re: [yocto] how to deal with the dependency explosion caused by enabling x11vnc

On 22 December 2017 at 02:53, Davis Roman wrote: > > Hello, > > I'd like to put a vnc server on my target. > > My embedded target has an onboard display and runs an application that > drives the display directly via the framebuffer. ( no xorg onboard ) > > I would like to use x11vnc ( with the --

Re: [yocto] running autoreconf during a configuration step

On 4 January 2018 at 15:45, Rail Shafigulin wrote: > I'm somewhat new to Yocto. Trying to build libsoc, > https://github.com/jackmitch/libsoc. The steps are outlined here, > https://github.com/jackmitch/libsoc#manually-building. The first one > is to run autoreconf -i. I've been looking through d

Re: [yocto] running autoreconf during a configuration step

If you look at autotools.bbclass you'll see it already passes -i. Ross On 4 January 2018 at 16:20, Rail Shafigulin wrote: > How do I add parameters to it? I need to run autoreconf -i. Didn't > find any EXTRA_OE variables. > > On Thu, Jan 4, 2018 at 8:15 AM, Burton, R

Re: [yocto] applying patches depending on the image's name

No, because images are built from packages, and the packages have already been built by the time the image is considered. Using master you can build two different kernels in the same build and have different kernels in different images. Ross On 9 January 2018 at 15:54, Vadim Intelegator < v.inte

Re: [yocto] Remove libjpeg.so (default built even in core-image-minimal) from the rootfs when build yocto

On 16 January 2018 at 04:28, Nguyễn Thanh Vũ wrote: > I have statically linked the libjpeg of my own to the exe file, so I do > not need the libjpeg.so default built in the /lib of rootfs. How can I > modify or specify in the local.conf file so that I can remove that > component? It takes quite a

Re: [yocto] Error do_compile libepoxy

I suggest you ask the upstream maintainers of libepoxy. Ross On 17 January 2018 at 12:46, Mathias Rudnik wrote: > Hello, > > I am trying to build libepoxy but the do_compile tasks breaks. > I found following error messages in the logs: > > arm-poky-linux-gnueabi-gcc -march=armv6 -mfpu=vfp -mflo

Re: [yocto] Error do_compile libepoxy

On 18 January 2018 at 08:58, Andrea Galbusera wrote: > Looks like my first guess was not that bad. Reverting below commit, > which switched to meson build system brought my build back to green. > Also CC-ing the patch author who might suggest further investigations. > So you've implicated the Me

Re: [yocto] do_roots braking after a SRCREV update for non master branch

I'd check (using oe-pkgdata-util and/or buildhistory-diff) that the new package is building the same files and packages as the old one. If PN wasn't being generated, that would explain why the provides isn't working. Ross On 18 January 2018 at 14:46, Alan Martinovic wrote: > Hi, > I've updated

Re: [yocto] eSDK and Multilib

Don't install both into the SDK? If you must, oe_multlib_header might help. Ross On 22 January 2018 at 17:51, wrote: > I'm running pyro, and I'm struggling to create an eSDK for multilib > custom image. I keep running into FileExistsError errors during the > do_sdk_depends task. > > It seems

Re: [yocto] [RFT] Glibc 2.27

On 29 January 2018 at 07:45, Zoran Stojsavljevic < zoran.stojsavlje...@gmail.com> wrote: > This one will be tough to integrate. Most of the packages depend on > this one, which is critical one. On the very bottom. I would say, this > is a big step, since here somewhere you should draw clear line.

Re: [yocto] [OE-core] [RFT] Glibc 2.27

The yocto autobuilder was idle so I fired it, fingers crossed :) On 27 January 2018 at 21:44, Khem Raj wrote: > Hi All > > glibc 2.27 is releasing soon in few weeks. I have put together the recipes > for upgrade, along with fixes for some of packages that I ran into here > > http://git.openembed

Re: [yocto] [RFT] Glibc 2.27

On 29 January 2018 at 13:56, Zoran Stojsavljevic < zoran.stojsavlje...@gmail.com> wrote: > > Khem Raj writes: This has gotten limited testing. > > Burton Ross writes: This one will be easy to integrate. > > Time Will Tell. > I guess I meant easy in that it just won&#x

Re: [yocto] Installing an rpm without repackaging

So first, You can't put ROOTFS_POSTPROCESS_COMMAND inside a recipe as it needs to be inside an image recipe specifically. You generally can't take an RPM from somewhere else and inject it into OE to use directly. One good reason is that the package manager used is configurable, so what do you wan

Re: [yocto] [PATCH][meta-mingw] gcc-crosssdk: use oe.utils.str_filter_out

On 30 January 2018 at 11:46, Richard Purdie < richard.pur...@linuxfoundation.org> wrote: > Why aren't we using > EXTRA_OECONF_remove_mingw32 = "--with-linker-hash-style=${ > LINKER_HASH_STYLE}" > out of interest? > > I thought (hoped) the filter-out stuff was dead now? > I'll admit I just fixed t

Re: [yocto] Generating Yocto SDK as .deb (Debian) pacakge

There's no support for this, but it should be fairly simple to write a debian/rules yourself to package the SDK in a deb. Ross On 31 January 2018 at 08:05, Gaurang Shastri wrote: > Hi Team, > > How can I generate Yocto generated SDK as .deb package? Currently it is in > the form of installable

Re: [yocto] Patching only the target version of a package?

On 1 February 2018 at 14:29, Michael Habibi wrote: > I'm sure this is really simple but I haven't quite wrapped my head around > it. > > We have a bbappend file that supplies a set of patches. It currently has > the unintended side-effect of patching both the native version used during > the Yoct

Re: [yocto] Patching only the target version of a package?

On 1 February 2018 at 15:03, Michael Habibi wrote: > So let's say my whole bbappend file is only necessary for the target > version. Can I rename the whole thing package-target.bbappend (add the > -target suffix) and it will only append it to the recipe when building the > target? Is "target" the

Re: [yocto] Patching only the target version of a package?

docs, but not an actual explanation of how > that all works and is put together. Any ideas? > > On Thu, Feb 1, 2018 at 9:34 AM, Burton, Ross > wrote: > >> On 1 February 2018 at 15:03, Michael Habibi wrote: >> >>> So let's say my whole bbappend file is only

Re: [yocto] How to create lighttpd with minimal configure options?

On 1 February 2018 at 12:02, Frank Smith wrote: > I want to create a minimal lighttpd package as small as possible. > Therefore I created a bbappendfile with extra configure flags. As follows. > But the changes seems to not have any effect at all. The size of my minimal > rootfs.jffs2 increases f

Re: [yocto] db-native fetching error

On 2 February 2018 at 14:44, Staffa, Christian AVL/DE < christian.sta...@avl.com> wrote: > I am trying to setup a yocto build environment. I am using win 10 with WSL > and an ubuntu environment. > > After coping with the company proxy to route the traffic properly I have > an error with db-native

Re: [yocto] Yocto Recipe for LibRXE.

It's not in the layer index ( http://layers.openembedded.org/layerindex/branch/master/recipes/?q=librxe), so I suggest you start with devtool to create a new recipe. Ross On 7 February 2018 at 17:43, Vish (Vishwanath) Maram < vishwanat...@samsung.com> wrote: > Hi, > > I am looking for a yocto re

Re: [yocto] Yocto uses UTC time for DATETIME instead of localtime

On 12 February 2018 at 04:24, Davis Roman wrote: > DATE := "${@time.strftime('%Y%m%d',time.localtime())}" > TIME := "${@time.strftime('%H%M%S',time.localtime())}" > > > Can you suggest a different way of making this change? > Use bitbake -e to see if there's a good reason why that didn't work. P

Re: [yocto] [meta][PATCH] ptest.bbclass: fix path for multilib

On 16 February 2018 at 21:41, Kyle Russell wrote: > ptest-runner always looks at /usr/lib, so make this arch independent. > I'd say the bug here is in ptest-runner. I'd expect to be able to install libfoo-ptest and lib32-libfoo-ptest in parallel. Ross -- __

Re: [yocto] [Yocto][Meta-Raspberrypi] Yocto apt sources.list for Raspberry Pi

Running your own feed for personal use is trivial, just point lighttpd or any other HTTP server at the deploy/deb directory on your build machine. If you set PACKAGE_FEED_URLS in your local.conf to the URL of the server then future images will contain a pre-populated sources.list. However the only

Re: [yocto] Adding Gnome to X11

Because by doing IMAGE_INSTALL += you wiped out the default value which is a ?=. gnome-desktop3 isn't the GNOME interface though, it's just a small library. If you want the full GNOME 3 desktop then you'll need to start with meta-gnome and write more recipes, as it's not entirely packaged. Ross

Re: [yocto] error: possibly undefined macro: PKG_CONFIG_SYSROOT_DIR

That usually means that the recipe doesn't inherit pkgconfig, but as this is an oe-core recipe it should be doing this. Can you verify this, and if you can still reproduce it after deleting tmp/ then please attach the entire log.do_configure. Ross On 1 March 2018 at 10:21, Abhishekh Awanti wrot

Re: [yocto] error: possibly undefined macro: PKG_CONFIG_SYSROOT_DIR

e? > > > Thanks and Regards, > Abhishek Awanti > Mob: +919620666017 <+91%2096206%2066017> > > On Thu, Mar 1, 2018 at 4:37 PM, Burton, Ross > wrote: > >> That usually means that the recipe doesn't inherit pkgconfig, but as this >> is an oe-core recipe i

Re: [yocto] RREPLACE is not applied do_package_qa() ?

That isn't what replaces is for: RREPLACES is used to hint to the package manager what package should be removed when there are conflicts. It won't have any impact on package dependencies at any other time. Ross On 1 March 2018 at 03:29, ikjn wrote: > Hi. > > I'm building mali userspace librar

Re: [yocto] [OE-core] Subject: Yocto Project Status WW10’18

On 5 March 2018 at 16:30, akuster808 wrote: > >- Performance metrics indicate that a recent merge has caused a >slowdown in build times. > > Is this data publicly available? > https://lists.yoctoproject.org/pipermail/yocto-perf/2018-March/thread.html The HTML mails are much more readabl

Re: [yocto] Are Windows SDKs (mingw layer) supposed to work?

Have you tried using 2.4 to identify when it broke? Clearly we need to extend the selftest so the mingw SDK is actually tested... Ross On 6 March 2018 at 05:32, Reyna, David wrote: > Hi all, > > > > I am trying to enable a customer for using YP SDKs on Windows. It > apparently is supposed to w

Re: [yocto] SDK without qemu

Do you mean "how can I build a SDK without using qemu" or "how can I build a SDK that doesn't contain qemu"? On 5 March 2018 at 15:37, Avishay Orpaz wrote: > Is there a way to build an SDK without qemu? > > > Avishay > > > > > -- > ___ > yocto mailing

<    8   9   10   11   12   13   14   15   16   >