Re: [yocto] Sato image touchscreen calibration is borked

Hi, On 13 November 2014 13:19, Mike Looijmans wrote: > I've been using "ts_calibrate" in the past, and that worked just fine on > this board. > Modern X servers don't use tslib, so this won't work since we stopped using kdrive about two years ago. DEBUG: Adding click 0 (X=1023, Y=599) > DEBUG:

Re: [yocto] Sato image touchscreen calibration is borked

On 13 November 2014 14:09, Mike Looijmans wrote: > So it seems related to the little I2C touchscreen controller, or some kind > of rotation. The coordinate system for the small touchscreen looks rotated > 180 degrees, looking at the numbers. xinput cannot handle that? My touchscreen is Y-invert

Re: [yocto] Sato image touchscreen calibration is borked

On 13 November 2014 17:58, Michael Gloff wrote: > BTW, you can use tslib with xorg. This is what I have set up as I find > ts_calibrate easier to work with. The only mention of e.g. ts_read() that I can see in the xserver source is in the kdrive server. Is there some compatibility mode or some

Re: [yocto] Sato image touchscreen calibration is borked

On 14 November 2014 08:17, Michael Gloff wrote: > I am using the xf86-input-tslib X driver. I forgot about that piece of the > puzzle. > Genuinely surprised that still works, but good to know! Ross -- ___ yocto mailing list yocto@yoctoproject.org htt

Re: [yocto] Sato image touchscreen calibration is borked

On 17 November 2014 07:25, Mike Looijmans wrote: > BTW, you can use tslib with xorg. This is what I have set up as I find >> ts_calibrate easier to work with. >> > > Interesting option, can you elaborate on that (in particular, in > combination with Yocto builds)? meta-oe has xf86-input-tslib.

Re: [yocto] Layer model doomed, unless we all work together

Hi Philip, Yes. What you said. Some comments: On 18 November 2014 21:28, Philip Balister wrote: > > 1) recipes that need to move closer to core because a range of other > packages use them. > alsa-plugins is one of these - meta-multimedia or maybe oe-core is an obvious home for this. As a "m

Re: [yocto] Custom recipe not working with 1.7.0 any more

On 1 December 2014 at 15:45, Jens Lucius wrote: > do_configure_prepend () { > echo "#define PJMEDIA_AUDIO_DEV_HAS_ALSA 1" > > pjlib/include/pj/config_site.h > echo "#define PJMEDIA_AUDIO_DEV_HAS_PORTAUDIO 0" >> > pjlib/include/pj/config_site.h > } > > Does complain about no

Re: [yocto] Custom recipe not working with 1.7.0 any more

On 1 December 2014 at 16:59, Jens Lucius wrote: > What should be used with aconfigure? > Well, what is aconfigure? Is it actually generated by autoconf, or something hand-coded? If it's not autoconf then you shouldn't be using the autotools classes. Ross -- __

Re: [yocto] [autobuilder][PATCH] buildset-config.controller: add nightly-arm64 target

On 1 December 2014 at 22:39, Flanagan, Elizabeth < elizabeth.flana...@intel.com> wrote: > Pulled into master, I'll bring it into production this week. Note: it > will not be part of nightly, so if you want it kicked on prod > autobuilders for nightlies, we'll have to do some extra work for that >

Re: [yocto] Issue with compiling x264 package in Yocto

On 3 December 2014 at 05:40, Yu, Chan KitX wrote: > Weirdly, git cloning that repository worked marvelously. I’m out of my > depth here so I’m posting here so more minds can dig this. I have also > attached the full log files so those interested can read the whole error > log. I think I have set

Re: [yocto] What drives automounting volumes?

On 4 December 2014 at 15:58, Gary Thomas wrote: > I've noticed this before - the /run/media mounts were sometimes > present, other times not. Any clues what drives this and why > they worked on Tuesday and not on Thursday (this week)? udev-extraconf is the recipe that installs these rules. If

Re: [yocto] [PATCH v2] distro/poky: Add Debian 8 (Jessie) as sanity tested

On 9 December 2014 at 15:32, Otavio Salvador wrote: > Richard, can you pick the v1 or want me to send a v3? > I had v1 in my MUT, then dropped it and added v2. I can drop that and go back to v1. ;) Ross -- ___ yocto mailing list yocto@yoctoproject.o

Re: [yocto] Package Feature compile/runtime dependency

On 12 December 2014 at 14:13, Koehler, Yannick (HP Networking) < yannick.koeh...@hp.com> wrote: > > > DEPENDS="linux-yocto-tiny:fhandle,autofs4,ipv6?,devtmpfs,libc:ftraverse,posix-clang-wchar,spawn,utmpx" > > Etc... Disregard the syntax as it is simply an idea/example and not > intended as a speci

Re: [yocto] How to properly add new qemu target + testimage support?

On 11 December 2014 at 19:56, Robert Berger < gm...@reliableembeddedsystems.com> wrote: > > I hacked together a qemu target which supports vexpress-a9. > > In order to get > > core-image-minimal -c testimage > > to work as well I had to cook > > meta/lib/oeqa/utils/qemurunner.py > scripts/runqemu >

Re: [yocto] Package Feature compile/runtime dependency

On 12 December 2014 at 15:44, Koehler, Yannick (HP Networking) < yannick.koeh...@hp.com> wrote: > > My hope, was that somehow, adding systemd to DISTRO_FEATURE would not only > add the packages I need, but also add feature to some package like the > kernel/libc that are required by such addition. >

Re: [yocto] Microcontroller Cross Compiler

On 21 December 2014 at 22:57, João Henrique Ferreira de Freitas < joa...@gmail.com> wrote: > > I will try it. But in my case I need to use this > https://launchpad.net/gcc-arm-embedded. > > There are some way to yocto creates the gcc-arm-embedded SDK? Instead of > use the gcc-arm-embedded packages.

Re: [yocto] Build Server Questions?

On 22 December 2014 at 18:41, nick wrote: > > I am wondering if a build server is a good idea for Yocto Builds. In > addition what specs are good for > a build server if I am to purchase one. Further more I am assuming as many > cores as possible for making > the build be parallel and faster. I wa

Re: [yocto] Selective append

On 2 January 2015 at 21:37, Moore, Thomas (FtWorth) wrote: > My question is this: is there a way to only apply the kernel patch when > the out-of-tree kernel module recipe is included in an image? > No. One solution would be to configure the driver as a module in the kernel and putting it in a

Re: [yocto] PDF manual support

On 13 January 2015 at 14:28, Rifenbark, Scott M wrote: > I am seriously considering dumping the PDF manuals for the 1.8 release. > The PDF output is less than good and there seems to have been no enthusiasm > for this form during the past 4 years. Comments? > Assuming that the source remains in

Re: [yocto] [PATCH] libidn_0.6.14: fix the QA Issue

Hi Lei, Patches for oe-core should go to the openembedded-core@ mailing list, not yocto@. But thanks, I've queued this for master. Ross On 23 January 2015 at 04:15, Lei Maohui wrote: > To fix the QA Issue as following: > ERROR: QA Issue: libidn: Files/directories were installed but not shippe

Re: [yocto] [meta-yocto] [PATCH 0/1] tiny-init: set proper S value

On 24 January 2015 at 09:22, Petter Mabäcker wrote: > Since bug [5627] has reached poky repo, can you please consider propose > merging of below change to meta-yocto, to avoid the warning about 'S' not > set to a proper value? > Whoops, I missed that when merging the other pieces, thanks for pin

Re: [yocto] Google Chrome recipe and systemd => how to satisfy runtime requirement for libudev.so.0?

On 27 January 2015 at 11:46, Timo Pulkkinen wrote: > i'm trying to create a recipe for Google Chrome for my first Yocto project > for Intel NUC (based on the Chrome rpm package). The recipe seems to build > ok, and I was able to > build a working system using sysvinit, but when I enabled systemd

Re: [yocto] recipe for smstools

Hi Kai, On 27 January 2015 at 15:44, Kai Ulrich wrote: > is there a recipe for smstools or smstools 3? > http://layers.openembedded.org/layerindex/branch/master/recipes/?q=smstools Layer index says no. Ross -- ___ yocto mailing list yocto@yoctoproj

Re: [yocto] Google Chrome recipe and systemd => how to satisfy runtime requirement for libudev.so.0?

On 27 January 2015 at 19:19, Timo Pulkkinen wrote: > tried this (I wasn't sure if I had done -ccleanstate for google-chrome > before together after removing the tmp), but it doesn't help. Sysroot > correctly contains /lib/libudev.so.1 (libudev.so.1.6.0, systemd). > tmp/deploy/rpm/ contains udev r

Re: [yocto] HEADSUP - CVE 2015-023 remote code execution in glibc

On 28 January 2015 at 11:17, Damian, Alexandru wrote: > Do we need to open a bug to track this ? > Probably for the best to ensure it goes into all the branches we support. Ross -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproj

Re: [yocto] [RFT] upcoming glibc 2.21 and gcc 4.9 upgrade

Hi Khem, On 2 February 2015 at 10:02, Khem Raj wrote: > I have put together upgrade to gcc 4.9.2 as well as glibc 2.21 ( > upcoming ) on a contrib branch ( top 2 patches) its has not got much > testing besides x86 qemu thus far. > I'm seeing these failures when cherry-picking the top two commi

Re: [yocto] COMPATIBLE_HOST

Hi Thomas, On 2 February 2015 at 15:17, Moore, Thomas (FtWorth) wrote: > I have a binary recipe that is only compatible with x86 and x86_64 > systems. I *think* specifying the COMPATIBLE_HOST in my recipe would be a > good idea. However, I've been unable to find any documentation, or even a > go

Re: [yocto] Need help for custom recipe

On 2 February 2015 at 16:54, Paul Eggleton wrote: > I'd have to say this is something we don't support. If you want to do this > you > would need to disable the current packaging tasks and stage the package > files > yourself, but that's going to take almost as much work as converting over > your

Re: [yocto] [RFT] upcoming glibc 2.21 and gcc 4.9 upgrade

On 2 February 2015 at 10:54, Khem Raj wrote: > On Mon, Feb 2, 2015 at 2:40 AM, Burton, Ross > wrote: > > cross-localdef-native: > > > > | In file included from glibc/locale/programs/locarchive.c:696:0: > > | glibc/locale/programs/../../intl/l10nflist.c: In funct

Re: [yocto] [RFT] upcoming glibc 2.21 and gcc 4.9 upgrade

Armin, On 2 February 2015 at 16:41, akuster wrote: > If I knew what "testing' entailed I would through some time at this. > "Please build your stuff with this glibc/gcc and check it still works". Ross -- ___ yocto mailing list yocto@yoctoproject.org

Re: [yocto] sstate management

On 2 February 2015 at 16:48, Christopher Larson wrote: > Is there some maintenance to be done on the sstate-cache? >> I'm thinking I want to set up a shared cache which might >> last for a long time and I would like to only keep the bits >> that are really needed. >> > > In the past i've

Re: [yocto] [RFT] upcoming glibc 2.21 and gcc 4.9 upgrade

On 2 February 2015 at 17:40, Khem Raj wrote: > Yeah, you must be using a weirdly compiled gcc on your host which is > defaulting to -std < c99 and hence the problem. I have fix for that issue > already locally. $ gcc --version gcc (Debian 4.7.2-5) 4.7.2 This is the default gcc in current Debi

Re: [yocto] [RFT] upcoming glibc 2.21 and gcc 4.9 upgrade

On 2 February 2015 at 18:33, Khem Raj wrote: > Yeah, I am on archlinux (the other end of spectrum). Nevertheless, I have > updated the contrib tree which fixes cross-localedef-native compile time > issue. So you should be good > to go now. > Bad news, glibc is now failing: | x86_64-poky-linux-g

Re: [yocto] [RFT] upcoming glibc 2.21 and gcc 4.9 upgrade

On 3 February 2015 at 05:03, Khem Raj wrote: > I think this issue was there even with older version of glibc for i7 > but it was flagged as a warning, glibc 2.21 now uses -Werror by > default. Can you confirm that via inspecting 2.20 glibc build logs for > this machine ? > dl-caller.c:1:0: warni

Re: [yocto] [RFC]provide native recipe for every package

On 3 February 2015 at 09:55, Paul Eggleton wrote: > Assuming what you mean is BBCLASSEXTEND = "native" for every recipe, I > don't > think we want to do this. There are a lot of things that should simply be > provided by the host rather than us building them; we need to be selective > about what

Re: [yocto] ACPI powerbtn

On 3 February 2015 at 21:30, Jim Abernathy wrote: > I need to add something that will 'shutdown -h now' when the power button > is pressed. I would figure that ACPI is already included in the > core-image-base of the NUC bsp. > > Do I need to include a new file in /etc/acpi/events or do I need t

Re: [yocto] [error-report-web] New errors-report-web

On 10 February 2015 at 14:26, Michael Wood wrote: > I've updated the errors.yoctoproject.org site with the latest version of > error-report-web [1] that myself and Belén have been working on. > \o/ Ross -- ___ yocto mailing list yocto@yoctoproject.or

Re: [yocto] [oe] meta-selinux

On 11 February 2015 at 21:39, Joe MacDonald wrote: > > What's more likely happening I suspect is that you are on a newer > > branch/revision of OE-Core/Poky than the meta-selinux maintainers have > tested. > > I can't speak to the maintenance schedule for meta-selinux but maybe > others > > with

Re: [yocto] Why did my build need to redo so many tasks?

On 12 February 2015 at 21:25, Gary Thomas wrote: > Yesterday, I built a large image using Poky/Yocto 870323cac1e > Today I updated my Poky repo to 231d4a9d3 > > When I rebuilt the same image, bitbake kicked off more than > 5200 tasks, building virtually every package from scratch. > > How can I t

Re: [yocto] [OE-core] [RFT] upcoming glibc 2.21 and gcc 4.9 upgrade

Hi Khem, On 12 February 2015 at 07:35, Khem Raj wrote: > I have refreshed the branch to include the patch which moves the src > uri to use the newly released glibc 2.21 branch > and please run it via autobuilder ( top 5 commits ) > I did a preliminary test on my local build machines (core-image

Re: [yocto] [OE-core] [RFT] upcoming glibc 2.21 and gcc 4.9 upgrade

Hi, On 14 February 2015 at 10:06, Richard Purdie < richard.pur...@linuxfoundation.org> wrote: > Right now, poky-tiny failed due to warning are errors and unused > symbols. Minnow failed due to SSE instruction issues. Full build logs > are also available on the autobuilder: > Now those SSE errors

Re: [yocto] Busybox error

On 19 February 2015 at 13:43, Pavel Daniel wrote: > ERROR: Function failed: SYSTEMD_SERVICE_busybox-syslog value > busybox-syslog.service does not exist meta-ivi disables busybox's syslog building but doesn't stop the systemd packaging from happening, which then fails. You can probably work ar

Re: [yocto] glibc fetching problems

On 20 February 2015 at 12:50, Gary Thomas wrote: > This is because any attempt to clone that repo breaks: > $ git clone git://sourceware.org/git/glibc.git > Cloning into 'glibc'... > fatal: read error: Connection reset by peer > Works for me: $ git clone git://sourceware.org/git/glibc.git

Re: [yocto] glibc fetching problems

On 20 February 2015 at 13:19, Gary Thomas wrote: > Transient error? >> > > Must have been, it's working for me now as well. My magic touch. ;) Ross -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [PATCH] Add mpich support

Patches for meta-oe should go to the openembedded-devel list, not yocto@. Ross On 19 February 2015 at 21:43, Alexandru.Vaduva wrote: > From: Victor Rodriguez > > This patch add mpich support to yocto in order to run MPI framework on > embedded > systems. > > Signed-off-by: Alejandro Hernandez

Re: [yocto] [psplash][PATCH] Adding support for systemd and its service files

Hi Petter, On 22 February 2015 at 21:20, Petter Mabäcker wrote: > Anyone who knows what happened with this change? Any problem detected? I > was looking into adding support for systemd in psplash and found this old > changeset that is not included in the psplash repo yet. > > I dropped the ball

Re: [yocto] Recipe reporting system Announcement

On 25 February 2015 at 23:45, Aníbal Limón wrote: > I'm glad to announce the available of the Recipe reporting system (a.k.a, > RRS) [1]. > Woohoo! \o/ Ross -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yoct

Re: [yocto] meta-lxcbench

Hi Rickard, This must be a very old layer, these syntax changes were made a long time ago... On 27 February 2015 at 09:22, Rickard Bremer wrote: > ERROR: There is a confusing multiline, partially commented expression on > line 27 of file /home/rickardb/poky/lxcbench/meta-lxcbench/recipes-misc/l

Re: [yocto] New gst-player

On 4 March 2015 at 23:45, Gary Thomas wrote: > I like that owl has been replaced by gst-player, but I need > some help figuring out how to get it working :-( If you ask > it to play something and it doesn't have the appropriate > plugins available, it just sits there and acts stupid (no > error

Re: [yocto] New gst-player

On 5 March 2015 at 12:16, Gary Thomas wrote: > Using gstreamer1.0-libav seems to work, but it's really power hungry > (i.e can cause my board's power supply over current!). Does this > plugin just hook into libav? I've tried playing the same file using > mplayer (which does use libav) and it do

Re: [yocto] New gst-player

On 5 March 2015 at 14:10, Gary Thomas wrote: > Given that it's the same file being played on the same hardware, > shouldn't both programs need to be doing the same conversions, etc? > In theory, yes. I note that in this pipeline GStreamer is using libav to decode the video and then displaying i

Re: [yocto] Adding new library to yocto project

On 9 March 2015 at 16:50, Kfrell wrote: > I added "libxerces" to my bb image by using IMAGE_INSTALL += " libxerces". > Then, I try to build my image thru bitbake my-image-test and eveything is > done correctly but libxerces returns some errors : > Packages containing libraries get renamed (by de

Re: [yocto] Adding new library to yocto project

On 9 March 2015 at 18:30, Kfrell wrote: > ERROR: This autoconf log indicates errors, it looked at host include and/or > library paths while determining system capabilities. > Rerun configure task after fixing this. > build/tmp/work/oe-linux-gnueabi/libxerces/3.1.1-r1/xerces-c-3.1.1' > ERROR: Func

Re: [yocto] 2 images with single Bitbake recipe

On 9 March 2015 at 19:56, Nikolay Dimitrov wrote: > bitbake myproduct-combined-image > > ...which should create 2 separate images. > If typing both is too much bother, have a recipe that just has DEPENDS=myproduct-image myproduct-initramfs-image and stub out all the other tasks so it doesn't do

Re: [yocto] libgcc_s not present in Yocto image

On 5 February 2016 at 17:47, Nathan Sowatskey wrote: > find /usr/lib -name libgcc_s.so.1 > root@qemux86-64:~# > > I don’t have that lib. > As I said, libgcc_s.so.1 is in /lib, not /usr/lib. > With ldd I get: > > ldd /usr/bin/testprog > /usr/bin/ldd: line 117: /usr/bin/testprog: No such file or

Re: [yocto] libgcc_s not present in Yocto image

On 5 February 2016 at 18:12, Nathan Sowatskey wrote: > interpreter /lib64/ld-linux-x86-64.so.2 Does the loader hunt around for this, as this is certainly not present in a default OE image? Ross -- ___ yocto mailing list yocto@yoctoproject.org https:

Re: [yocto] libgcc_s not present in Yocto image

On 5 February 2016 at 19:56, Khem Raj wrote: > >> interpreter /lib64/ld-linux-x86-64.so.2 > > > > > > Does the loader hunt around for this, as this is certainly not present > in a > > default OE image? > > no it wont. infact thats the loader. Yeah, what I meant is would the kernel hunt for that

Re: [yocto] Installing only part of linux-firmware

On 7 February 2016 at 21:49, Chris Tapp wrote: > I’ve now done this by creating a bbappend for linux-firmware: > > PACKAGES =+ "${PN}-rtl_nic" > > FILES_${PN}-rtl_nic = " \ > /lib/firmware/rtl_nic/* \ > “ > > Does what I want, but is that the best way of doing it? > This is the best way for yo

Re: [yocto] What is the correct way to get a list of package run-time dependencies during the build process?

On 5 February 2016 at 10:45, Reshetova, Elena wrote: > recipe.r_deps = d.getVar('RDEPENDS_' + recipe.name, True) > > > > or even simple: > > > > recipe.r_deps = d.getVar('RDEPENDS’, True) > > Did you mean RDEPENDS_ + package name? Ross -- ___ yocto ma

Re: [yocto] how to create a named_pipe in my image

On 8 February 2016 at 16:12, Baumann, Michael wrote: > Possibly it's because named pipes cannot be packed into an archive? If > yes, how can I circumvent this? > It would be interesting to see what happens if you change PACKAGE_CLASSES to use rpm instead of ipkg. One workaround would be to crea

Re: [yocto] What is the correct way to get a list of package run-time dependencies during the build process?

On 8 February 2016 at 16:20, Reshetova, Elena wrote: > >Did you mean RDEPENDS_ + package name? > > > > I have it like this: > > > > recipe.name = d.getVar('PN', True) > > recipe.r_deps = d.getVar('RDEPENDS_' + recipe.name, True) > So I wasn't quite right - I think you also need to come after do_

Re: [yocto] how to create a named_pipe in my image

On 8 February 2016 at 16:39, Baumann, Michael wrote: > Switching to rpm package showed the same behavior. > > Is there another workaround than a post install script? > > So I had a quick look at this. The fifo certainly ends up in the resulting ipk at least, but as you say package_qa hangs. It'

Re: [yocto] how to create a named_pipe in my image

On 8 February 2016 at 17:36, Burton, Ross wrote: > So I had a quick look at this. The fifo certainly ends up in the > resulting ipk at least, but as you say package_qa hangs. It's probably > encountering a non-file and breaking somewhere. A really nasty workaround > until th

Re: [yocto] Where should I append Yocto bitbake task to create work folder symlink ?

On 9 February 2016 at 08:37, Woronicz, Bartosz ( NSN - PL/Wroclaw) < bartosz.woron...@nokia.com> wrote: > Ok, but I don't want to run it everytime, just after the do_unpack. What I > need to put it in requirements for each recipe ? > Maybe something like > > do_unpack[require] = "latest_link" > d

Re: [yocto] Where should I append Yocto bitbake task to create work folder symlink ?

On 9 February 2016 at 13:51, Woronicz, Bartosz ( NSN - PL/Wroclaw) < bartosz.woron...@nokia.com> wrote: > Here is the whole bbclass > *: * > > DESCRIPTION = "Creates symlink to the latest version workdir of the > package" > > do_latest_link() { > if [ -n "${WORKDIR}" ]; then > linkname

Re: [yocto] valgrind-native

Hi, On 11 February 2016 at 10:44, Woronicz, Bartosz ( NSN - PL/Wroclaw) < bartosz.woron...@nokia.com> wrote: > Any ideas why I cannot build native valgrind ? > http://pastebin.com/e2h6AWxN > "Missing or unbuildable dependency chain was: ['valgrind-native', > 'glibc-dbg-native']" > > Also tried bi

Re: [yocto] valgrind-native

On 11 February 2016 at 12:38, Woronicz, Bartosz ( NSN - PL/Wroclaw) < bartosz.woron...@nokia.com> wrote: > many thanks for nice explanation. At my shallow research, I notice, that > valgrind is somewhat special demanding packages with debugging symbols, > sooo... I actually don't need all packages

[yocto] Dropping Debian 7 as supported?

Hi, I'm proposing that we drop Debian 7 from the supported distributions list in master, so that the 2.1 release supports Debian 8. Debian 7 was released in 2013, Debian 8 superceded it in April 2015 so will have been out for a year when 2.1 is released, which also means that is when Debian 7 sto

Re: [yocto] Dropping Debian 7 as supported?

On 11 February 2016 at 14:21, Nick Leverton wrote: > Possibly a little early - Debian 7 will be going onto LTS security support > for > two years, starting some time this month. Quoting from > https://wiki.debian.org/LTS > Ah yes, I'd forgotten about the LTS project and was looking at the secur

Re: [yocto] native tool is not installed before it is used

On 12 February 2016 at 06:10, Sridhar Pitchai wrote: > I have a recipe, where It need protobuf-c-compiler (natvily) to auto > generate files before it can be compiled. i have added protobuf-c-native in > the DEPENDS list. but the compilation is failling at do_autogen, compiling > the proto-c is n

Re: [yocto] Dropping Debian 7 as supported?

On 12 February 2016 at 17:14, Fred Ollinger wrote: > So far, I have zero problems, and it would be nice to not see a scary > message telling me to change distros if my distro actually works great. > You must have missed the bit where I said that Debian 8 was being supported, I just wanted to dro

Re: [yocto] ERROR: Error executing a python function in exec_python_func() autogenerated

On 14 February 2016 at 18:24, Ilya Katsnelson wrote: > Exception: IOError: [Errno 2] No such file or directory: > '~/work/angstrom/build/tmp-angstrom_v2015_12-glibc/work/armv7at2hf-vfp-neon-angstrom-linux-gnueabi/busybox/1.23.2-r0/image${sysconfdir}/busybox.links.nosuid' > > ERROR: Function faile

Re: [yocto] jethro 2.0.1/ubi-utils not installed on target

On 16 February 2016 at 09:03, wrote: > It seems to be insufficient to add mtd-utils to a packagegroup[1] and add > this to the image for it to be installed in the image. > The package is being built and I can install it afterwards e.g. opkg > install mtd-utils-ubifs_1.5.1+git0+9f107132a6-r0_armv7

Re: [yocto] [meta-selinux][PATCH] swig is in meta-oe, remove this copy

On 22 February 2016 at 15:33, Joe MacDonald wrote: > I'm also not against removing the local copy (I don't think it adds > anything to the layer and occasionally causes headaches), but I really > don't want to make meta-selinux dependent on meta-oe components, so I > guess I'm voting for keeping

Re: [yocto] How to deal with patch failures due to new source?

On 23 February 2016 at 20:16, Paul D. DeRocco wrote: > All of a sudden, I'm getting massive patch failures in OE's Samba 4 > package. (Last night it was fine.) Looking at the main log, the > samba-4.1.12-r0 recipe did a do_fetch, do_unpack and do_patch. This is a > huge patch, a megabyte in size,

Re: [yocto] [meta-selinux][PATCH] swig is in meta-oe, remove this copy

On 22 February 2016 at 14:51, Radzykewycz, T (Radzy) wrote: > It's easy enough to update the one in meta-selinux, if the decision is > to keep the duplicate. I have a 3.0.6 => 3.0.8 update ready to upload > to meta-oe, and I can do meta-selinux at the same time. > In master at least, swig isn't

Re: [yocto] Full Pass test report for YP 2.1_M2.rc3

Hi, On 24 February 2016 at 15:36, Georgescu, Alexandru C < alexandru.c.george...@intel.com> wrote: > -9131 - > We found that for some BSPs (detected on 32bit, qemuarm and qemuppc) > Applications can't be opened in SATO due matchbox i

Re: [yocto] Source for recipe on local drive

On 26 February 2016 at 14:55, Marius Liebenberg wrote: > How do I get all the source code for a specific recipe onto my local > drive. That is without sifting through all the config files to try and get > url's > "bitbake [recipe] -c fetch" will just run the fetch task. Ross -- ___

Re: [yocto] [OE-core] Yocto Project Status WW09

On 26 February 2016 at 20:16, Philip Balister wrote: > I must admit, I'm surprised this is tricky. I look forward to seeing > what needs doing. Hopefully, it shows me things I can avoid in my work. > The moral of the story is don't rename layers if you want to maintain a semblance of migration.

Re: [yocto] [xcursor-transparent-theme][Patch] Add several cursors

Hi Johannes, This and the other patch have been merged, thanks. However I just realised that we don't actually need this anymore and should instead be passing -nocursor when starting X11. Ross On 1 March 2016 at 23:52, Johannes Pointner wrote: > This patch adds several cursor to the transpar

Re: [yocto] [xcursor-transparent-theme][Patch] Add several cursors

Hi Johannes, On 2 March 2016 at 12:19, Burton, Ross wrote: > This and the other patch have been merged, thanks. > I've also merged in the patches that oe-core was carrying and did a bit of a spring clean, so if you can test and submit a srcrev bump and patch removal for oe-core th

Re: [yocto] [xcursor-transparent-theme][Patch] Add several cursors

On 2 March 2016 at 12:45, Johannes Pointner wrote: > I didn't know this option. > But I think there is still a use case for the > xcursor-transparent-theme. Because the cursor theme can be set before > starting a new application without restarting X11. > How do you handle users switching between

Re: [yocto] [xcursor-transparent-theme][Patch] Add several cursors

On 2 March 2016 at 12:48, Burton, Ross wrote: > How do you handle users switching between applications in that case? Or > the application crashing and leaving you without a cursor? If a particular > application should hide the cursor them it should just hide the cursor, if > t

Re: [yocto] [xcursor-transparent-theme][Patch] Add several cursors

On 2 March 2016 at 15:36, William Mills wrote: > How about transparent when last user input was touch-screen but normal > when last input was mouse/touchpad? > > This would be done on a per DISPLAY basis not a per app basis. > > Of course I don't know where to put that code and if I were doing it

Re: [yocto] btrfs-tools Requires libgcc_s.so.1

On 5 March 2016 at 00:12, wrote: > What is the process for getting this fixed upstream? Trivial patch is > below, if that is sufficient. > Would you be able to send that to the oe-core list ( openembedded-c...@lists.openembedded.org) using git-send-email (ideally, attaching the output of git for

Re: [yocto] Howto change the default shell in yocto?

On 5 March 2016 at 11:48, Oliver Graute wrote: > first the default *system* shell (/bin/sh) is this possible? or does this > affect > to much of the yoco system itself, if I change /bin/sh to /bin/dash? > bash is only the default shell (ie symlink from /bin/sh) if you install it, so if you don't

Re: [yocto] Building gdb-7.10 for arm with master

On 5 March 2016 at 21:19, Rudolf J Streif wrote: > compile fails with the following error message: > > | make[2]: *** No rule to make target '../readline/libreadline.a', needed > by 'gdb'. Stop. > | make[2]: *** Waiting for unfinished jobs > > The reason seems to be a broken path to the buil

Re: [yocto] How to add some additional enviroment variables to /etc/profile file while building IMAGE

On 7 March 2016 at 10:20, Vivek Per wrote: > i want to add some additional enviroment variables in /etc/profile > file. How can i add these while building, so that it reflect in my target > image. > base-files is the recipe that ships /etc/profile, so you can use a bbappend to either replac

Re: [yocto] Adding lxc support to image

On 7 March 2016 at 13:52, Biyani Arun (CM/ESC-NA) wrote: > I would like to include lxc style container support in poky image. I added > “meta-virtualization” to my > bblayers.conf. I now get errors when running “bitbake-layers show-recipes”. > > Parsing recipes..ERROR: No recipes available for: >

Re: [yocto] [PATCH] udev: Rename udev bbappend to eudev.

On 7 March 2016 at 17:15, Fred Ollinger wrote: > Can someone please let me know what the reasoning behind the switch to > eudev? > udev is unmaintained and many desktop Linux systems have already either migrated to systemd or are using a modern udev ripped out of systemd (which would be eudev).

Re: [yocto] Failed to fetch URL git://gitorious.org/raw2rgbpnm/raw2rgbpnm.git

On 7 March 2016 at 19:11, Mark Brown wrote: > WARNING: Failed to fetch URL git:// > gitorious.org/raw2rgbpnm/raw2rgbpnm.git;protocol=git, attempting MIRRORS > if available > ERROR: Fetcher failure: Fetch command failed with exit code 128, output: > Cloning into bare repository > '/home/bbusr/buil

Re: [yocto] Failed to fetch URL git://gitorious.org/raw2rgbpnm/raw2rgbpnm.git

On 7 March 2016 at 21:24, Mark Brown wrote: > I do not see anything in /poky/meta-gumstix-extras/recipes-images/gumstix/ > gumstix-console-image.bb > which mentions protocol or protocol=git. > In the raw2rgbpnm recipe, meta-gumstix-extras/recipes-graphics/raw2rgbpnm/ raw2rgbpnm_git.bb accordin

Re: [yocto] packages with PKGSIZE 0

On 7 March 2016 at 21:46, Bhanagay, Sagar wrote: > I was going through the list of packages installed in the image (as per > the manifest file). > > I noticed that metadata information for these packages is present at - > > */build/tmp/sysroots/NAME/pkgdata/runtime/* > > > > Now I do notice that

Re: [yocto] Failed to fetch URL git://gitorious.org/raw2rgbpnm/raw2rgbpnm.git

On 8 March 2016 at 00:20, Mark Brown wrote: > fatal: unable to access 'https://gitorious.org/raw2rgbpnm/raw2rgbpnm.git/': > server certificate verification failed. CAfile: > /etc/ssl/certs/ca-certificates.crt CRLfile: none > Your local certs are either missing or incomplete. You'll have to eith

Re: [yocto] how to compile ozone-wayland in own recipes?

On 11 March 2016 at 09:13, 윤영석 wrote: > I will compile ozone-wayland using my custom recipes. > I don't think you should do this. > if you want to know what is ozone-wayland, please reference this site. " > https://github.com/01org/ozone-wayland"; > > The chromium recipe in meta-browser has supp

Re: [yocto] Nettle from release Fido fails to build

On 11 March 2016 at 09:45, Leon Anavi wrote: > > Yesterday I noticed that the build of recipe nettle 2.7.1 from release > Fido fails: > https://gist.github.com/leon-anavi/dfd3afab567a9dc9fa2f > Theres a patch from a few days ago on this list to fix the issue: http://patchwork.openembedded.org/pa

Re: [yocto] Nettle from release Fido fails to build

On 11 March 2016 at 10:07, Leon Anavi wrote: > OK, thank you for the feedback. I will wait for the fix in the Poky > repository. > Obviously you can apply the fix locally until it ends up in a release branch. Hooray git! Ross -- ___ yocto mailing li

Re: [yocto] Strange build dependency

On 14 March 2016 at 12:41, Gary Thomas wrote: > How can I find out what's going on here? > bitbake-whatchanged is generally helpful here. Do a build in one configuration, switch to the other, run bitbake-whatchanged. It will identify the hashes that have changed and try and chase them down. T

Re: [yocto] New message

On 14 March 2016 at 03:10, Gary Thomas wrote: > I just started a new build and saw a message that's new to me: > NOTE: Fetching uninative binary shim from > http://downloads.yoctoproject.org/releases/uninative/0.95/x86_64-nativesdk-libc.tar.bz2;md5sum=4b6fb2106c2f18b8f9c8ac67e1cf9e57 > > * What

Re: [yocto] New message

On 14 March 2016 at 15:58, Christopher Larson wrote: > You're using the poky distribution which for build performance uses >> uninative (from 477b8fb), which means that instead of building native >> dependencies per-host-distribution there's a static libc which is built >> against to enable nativ

<    2   3   4   5   6   7   8   9   10   11   >