Re: [yocto] Signed RPMs

Hi Chris, On 04/02/16 23:57, "Chris Trobridge" wrote: >Hi, >I have been testing out the facility for generating signed RPMs. > >It's currently failing to find >'build/tmp/sysroots/x86_64-linux/etc/RPM-GPG-PUBKEY', log listed at end. > >I couldn't find a lot of documentation but from what I co

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

Hi, I noticed that during the build bitbake supplies you rather correct (if it is correct in the recipe) list of recipe build-time dependencies. However, this isn't true for run-time dependencies. Moreover it seems that when you define a recipe you don't have to list run-time dependencies, but

Re: [yocto] [PATCH][yocto-autobuilder] nightly-musl: also build core-image-weston

On 5 February 2016 at 02:08, Khem Raj wrote: > > diff --git a/buildset-config.controller/nightly-musl.conf > b/buildset-config.controller/nightly-musl.conf > > index 9a82e6b..5da90c3 100644 > > --- a/buildset-config.controller/nightly-musl.conf > > +++ b/buildset-config.controller/nightly-musl.co

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 08:27, Reshetova, Elena wrote: > I noticed that during the build bitbake supplies you rather correct (if it > is correct in the recipe) list of recipe build-time dependencies. However, > this isn’t true for run-time dependencies. Moreover it seems that when you > define a re

Re: [yocto] libQt5Network.so.5 - How does one get that please?

It turns out that the build is correct, in that the libraries are there, but the test program I am using is not finding them :-/ So, for future reference, at least part what is required to work is correct in my build. Regards Nathan > On 4 Feb 2016, at 17:39, Nathan Sowatskey wrote: > > Hi

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 08:27, Reshetova, Elena < elena.reshet...@intel.com> wrote: I noticed that during the build bitbake supplies you rather correct (if it is correct in the recipe) list of recipe build-time dependencies. However, this isn’t true for run-time

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 08:27, Reshetova, Elena < elena.reshet...@intel.com> wrote: I noticed that during the build bitbake supplies you rather correct (if it is correct in the recipe) list of recipe build-time dependencies. However, this isn’t true for run-time

Re: [yocto] Signed RPMs

On 05/02/16 11:15, "Chris Trobridge" wrote: >> Date: Fri, 5 Feb 2016 10:00:50 +0200 >> Subject: Re: [yocto] Signed RPMs >> From: markus.lehto...@linux.intel.com >> To: christrobri...@hotmail.com; yocto@yoctoproject.org >> >> Hi Chris, >> >> ... >> >> That really should not be needed. What ver

[yocto] libgcc_s not present in Yocto image

Hi I am working with a test program which has a dependency on libgcc_s. On Ubuntu that is available, for example from a 14.04 Ubuntu desktop build: find /usr/lib -name "*gcc*” ... /usr/lib/gcc/x86_64-linux-gnu/4.8/libgcc_s.so ... On the Yocto image I am building (see below for conf files), I d

Re: [yocto] libgcc_s not present in Yocto image

On Fri, 2016-02-05 at 12:40 +0100, Nathan Sowatskey wrote: > Hi > > I am working with a test program which has a dependency on libgcc_s.  > > On Ubuntu that is available, for example from a 14.04 Ubuntu desktop build: > > find /usr/lib -name "*gcc*” > ... > /usr/lib/gcc/x86_64-linux-gnu/4.8/libg

Re: [yocto] libgcc_s not present in Yocto image

On 5 February 2016 at 11:40, Nathan Sowatskey wrote: > Is there a way to get the libgcc_s library on a Yocto image? Is that even > the right thing to do? > It's fairly likely that your binary is actually linking to libgcc_s.so.1 (which by default is in /lib, part of libgcc). libgcc_s.so is the

Re: [yocto] libgcc_s not present in Yocto image

Thank you Burton and Tanu. The upshot here seems to be that there is a platform dependency on whether one links to libgcc_s.a or libgcc_s.so.1: "libgcc.a or libgcc_s.so.1 on some platforms”. I suspect that my test program, which was supplied to me as a .deb package, was compiled on Ubuntu, and

Re: [yocto] libgcc_s not present in Yocto image

-- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] libgcc_s not present in Yocto image

On 5 February 2016 at 15:24, Nathan Sowatskey wrote: > I suspect that my test program, which was supplied to me as a .deb > package, was compiled on Ubuntu, and so links to libgcc_s.so.1. I can’t see > any obvious way to get libgcc_s.so.1 on Yocto. I already have: > libgcc contains /lib/libgcc_s

Re: [yocto] [PATCH][yocto-autobuilder] nightly-musl: also build core-image-weston

On 5 February 2016 at 09:02, Burton, Ross wrote: > We can switch nightly-musl over to just opkg whilst rpm is known to be > broken. We already have a separate tiny buildset. > Revised patch sent. Ross -- ___ yocto mailing list yocto@yoctoproject.org

[yocto] [PATCH][yocto-autobuilder] nightly-musl: build core-image-weston, only use ipkg

Build core-image-weston for more coverage, and use ipkg explicitly as rpm is known to break with musl. Signed-off-by: Ross Burton --- buildset-config.controller/nightly-musl.conf | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/buildset-config.controller/nightly-musl.conf b

[yocto] Yocto Project Status WW06

Current Dev Position: YP 2.1 M3 Next Deadline: YP 2.1 M2 Target release date is February 12, 2016 SWAT team rotation: Alejandro Franco -> Juro https://wiki.yoctoproject.org/wiki/Yocto_Build_Failure_Swat_Team Key Status/Updates: * YP 2.1 M2-rc1 QA report has been published. The number of High

Re: [yocto] libQt5Network.so.5 - How does one get that please?

Did you try $ ldd program-name This should tell you which libraries are missing and where it is looking. Then you can do: $ find / -name libname.so To find them. Finally, you can fix your /etc/ld.so.conf with the path to your libs. Then do $ ldconfig # refresh library cache so your libs

Re: [yocto] libgcc_s not present in Yocto image

On Fri, 2016-02-05 at 15:50 +, Burton, Ross wrote: > > On 5 February 2016 at 15:24, Nathan Sowatskey > wrote: > > I suspect that my test program, which was supplied to me as a .deb > > package, was compiled on Ubuntu, and so links to libgcc_s.so.1. I > > can’t see any obvious way to get libgc

Re: [yocto] libgcc_s not present in Yocto image

Hi Ross Many thanks for following up. Fred also offered some helpful suggestions in a different thread. The program in question was supplied to me by a third party for testing, so I shall obscure the name here and call it testprog. It was installed by: dpkg -i ./testprog.deb Where the .deb

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

What are results of: $ file testprog Frederick From: Nathan Sowatskey Sent: Friday, February 5, 2016 9:47 AM To: Burton, Ross Cc: yocto@yoctoproject.org; Fred Ollinger Subject: Re: [yocto] libgcc_s not present in Yocto image Hi Ross Many thanks for fol

Re: [yocto] libgcc_s not present in Yocto image

My guess is that the executable is not compiled for his hardware. Frederick From: Burton, Ross Sent: Friday, February 5, 2016 9:56 AM To: Nathan Sowatskey Cc: yocto@yoctoproject.org; Fred Ollinger Subject: Re: [yocto] libgcc_s not present in Yocto image On 5 F

Re: [yocto] libgcc_s not present in Yocto image

Thanks guys :-) Suggestions played out below. find /lib -name libgcc_s.so.1 /lib/libgcc_s.so.1 So, that *is* there. Doh! file /usr/bin/testprog /usr/bin/testprog: ELF 64-bit LSB executable, x86-64, version 1 (SYSV), dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, for GNU/Linux 2.6

Re: [yocto] libgcc_s not present in Yocto image

Thanks Fred. I am using qemux86_64 on Intel i7 chips with OSX. The target is likewise Intel. I am assuming that is quite generic, but … Regards Nathan > On 5 Feb 2016, at 19:06, Fred Ollinger wrote: > > My guess is that the executable is not compiled for his hardware. > > > Frederick > >

Re: [yocto] libgcc_s not present in Yocto image

The results should tell us: $ files /usr/bin/testprog What are they? (Sitting on the edge of my seat.) From: Nathan Sowatskey Sent: Friday, February 5, 2016 10:09 AM To: Fred Ollinger Cc: Burton, Ross; yocto@yoctoproject.org Subject: Re: [yocto] libgcc_s

Re: [yocto] libgcc_s not present in Yocto image

file /usr/bin/testprog /usr/bin/testprog: ELF 64-bit LSB executable, x86-64, version 1 (SYSV), dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, for GNU/Linux 2.6.24, BuildID[sha1]=26317096ed83d21bc6808f0d2d47b12de1ab31ce, not stripped Thoughts? > On 5 Feb 2016, at 19:10, Fred Olling

Re: [yocto] libgcc_s not present in Yocto image

What's the result of: $ cat /proc/cpuinfo (So far, it seems like my hunch was wrong.) Frederick From: Nathan Sowatskey Sent: Friday, February 5, 2016 10:12 AM To: Fred Ollinger Cc: Burton, Ross; yocto@yoctoproject.org Subject: Re: [yocto] libgcc_s not p

Re: [yocto] libgcc_s not present in Yocto image

On Fri, Feb 5, 2016 at 10:12 AM, Nathan Sowatskey wrote: > file /usr/bin/testprog > /usr/bin/testprog: ELF 64-bit LSB executable, x86-64, version 1 (SYSV), > dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, for GNU/Linux > 2.6.24, BuildID[sha1]=26317096ed83d21bc6808f0d2d47b12de1ab31c

Re: [yocto] libgcc_s not present in Yocto image

Thanks for trying :-) cat /proc/cpuinfo processor : 0 vendor_id : AuthenticAMD cpu family : 6 model : 6 model name : QEMU Virtual CPU version 2.5+ stepping: 3 cpu MHz : 2394.533 cache size : 512 KB physical id : 0 siblings: 1 core id

Re: [yocto] libgcc_s not present in Yocto image

Hi Kem The testprog was given to me as a .deb package by a third party to test. I did not compile it and I don’t know what they did either. Regards Nathan > On 5 Feb 2016, at 19:21, Khem Raj wrote: > > On Fri, Feb 5, 2016 at 10:12 AM, Nathan Sowatskey wrote: >> file /usr/bin/testprog >> /us

Re: [yocto] libgcc_s not present in Yocto image

On Fri, Feb 5, 2016 at 10:23 AM, Nathan Sowatskey wrote: > Hi Kem > > The testprog was given to me as a .deb package by a third party to test. I > did not compile it and I don’t know what they did either. OK, paste the out of readelf -a on this binary its mosly looking for libraries in wrong pat

[yocto] Release Candidate Build for yocto-2.0.1.rc4.rc4 now available.

A release candidate build for yocto-2.0.1.rc4 is now available at: http://autobuilder.yoctoproject.org/pub/releases/yocto-2.0.1.rc4 Please begin QA on this build as soon as possible. Build hash information: meta-intel : 4e87c59bdedaa8c3e44fc02fd23be726c4d1dfb9 meta-fsl-arm : 35b8b9bd9863d

Re: [yocto] libgcc_s not present in Yocto image

Thanks Khem. Please see below: readelf -a /usr/bin/testprog ELF Header: Magic: 7f 45 4c 46 02 01 01 00 00 00 00 00 00 00 00 00 Class: ELF64 Data: 2's complement, little endian Version: 1 (cu

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 Fri, Feb 5, 2016 at 11:53 AM, Burton, Ross wrote: > > 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? no it wont. infact thats the loader.

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] libgcc_s not present in Yocto image

On Fri, Feb 5, 2016 at 12:46 PM, Burton, Ross wrote: > > 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 th

Re: [yocto] libgcc_s not present in Yocto image

Hi Khem Thanks for trying to help :-) I read what you have suggested below as trying to execute “ld.so” and passing my program as an argument. I can’t find a file called “ld.so” on either my Yocto image, or even the Ubuntu box that I am using to build it (which I use as a comparative reference

Re: [yocto] libgcc_s not present in Yocto image

Hi Khem Thanks for trying to help :-) I read what you have suggested below as trying to execute “ld.so” and passing my program as an argument. I can’t find a file called “ld.so” on either my Yocto image, or even the Ubuntu box that I am using to build it (which I use as a comparative reference

Re: [yocto] libgcc_s not present in Yocto image

by ld.so I mean dynamic linker shared lib not literally ld.so file it should be in /lib/ld*.so On Fri, Feb 5, 2016 at 11:36 PM, Nathan Sowatskey wrote: > Hi Khem > > Thanks for trying to help :-) > > I read what you have suggested below as trying to execute “ld.so” and passing > my program as a