On Thu, 2018-03-08 at 19:18 -0600, Mark Hatle wrote:
> Yes, the dlopen means the automated processing can't identify the
> need.. and
> then the RDEPEND is the correct solution.
>
> (This might be a reasonable bug/enhancement request to the
> system. Look for
> pthread_cancel and automatically in
Hello all
I'm confused with version numbering of shared libs dependencies on yocto
environment. I’m using Morty but the thing looks like same with newer releases.
Let me explain the problem.
I'll take Curl package for example. We all know that the Curl recipe makes
libcurl-package also. Ok, now
I have 2 extra users (added with useradd_example.bb). Login works for all 3
parties.
While login works, passwd (to change it) doesn't work for the extra users. They
will asked for the old one - which fails.
Root is not to be asked for old password. That's way root can change password
for all.
Stephano
On 03/08/2018 10:46 AM, Stephano Cetola wrote:
> The Yocto Project team is moving to a new release planning process and I
> want to provide an overview as there will be some things I need from
> those of you making changes and adding things to Bugzilla.
>
> Overview:
> We are moving to a
On 3/8/18 4:10 PM, Marcelo E. Magallon wrote:
> On Thu, Mar 08, 2018 at 03:16:44PM -0600, Mark Hatle wrote:
>
>> RDEPENDS are automatically promoted to DEPENDS (build-time). I would
>> normally
>> expect libgcc_s.so.1 to be present via the typical default depends. Does
>> your
>> recipe have a
Hi Stephen,
Those idle test cases are actually belongs to the outdated testcases inside
Testopia, GDC had opened a Bugzilla ticket to remove and replace outdated and
duplicated test cases. We are in progress of removing ducplicated test cases,
next step is to remove outdated test cases using au
On Thu, Mar 8, 2018 at 1:52 PM, Wayne Witzke wrote:
>
> However, now I am attempting to determine if mod_openssl is installed on my
> server, and using "CORE_EXTRA_IMAGES_INSTALL += 'lighttpd-module-openssl'"
> to simply add it does NOT magically work like it did with
> lighttpd-module-fastcgi. My
On Thu, Mar 08, 2018 at 01:30:28PM -0800, robert_jos...@selinc.com wrote:
In the case of btrfs-tools, it was simply that it needed libgcc_s.so.1 at
runtime on the target, which my patch fixed. For me, the image I was
building normally worked fine because some other package would pull in
libgcc,
On Thu, Mar 08, 2018 at 03:16:44PM -0600, Mark Hatle wrote:
RDEPENDS are automatically promoted to DEPENDS (build-time). I would normally
expect libgcc_s.so.1 to be present via the typical default depends. Does your
recipe have an INHIBIT_DEFAULT_DEPENDS (I think that is it?) defined? If so,
Hello everyone,
I'm very new to Yocto, and I'm currently building an embedded system
with a web interface. As I worked through the process of creating a
Yocto configuration and layer to configure the specific build I needed
(based on core-image-minimal), I discovered that I could add packages
"Marcelo E. Magallon" wrote on 03/08/2018
01:00:28 PM:
> From: "Marcelo E. Magallon"
> To: ,
> Cc: "yocto@yoctoproject.org"
> Date: 03/08/2018 01:01 PM
> Subject: Re: [yocto] btrfs-tools Requires libgcc_s.so.1
>
> Sorry to go off on a tangent:
>
> On Fri, Mar 04, 2016 at 04:12:54PM -0800, r
On 3/8/18 3:00 PM, Marcelo E. Magallon wrote:
> Sorry to go off on a tangent:
>
> On Fri, Mar 04, 2016 at 04:12:54PM -0800, robert_jos...@selinc.com wrote:
>
root@test:~# btrfs scrub start /
scrub started on /, fsid 79dc4fed-a0f7-43e2-b9e7-056b1a2c4cdd
>> (pid=333)
libgcc_s.so.1 mu
Sorry to go off on a tangent:
On Fri, Mar 04, 2016 at 04:12:54PM -0800, robert_jos...@selinc.com wrote:
> root@test:~# btrfs scrub start /
> scrub started on /, fsid 79dc4fed-a0f7-43e2-b9e7-056b1a2c4cdd
(pid=333)
> libgcc_s.so.1 must be installed for pthread_cancel to work
>
> I can solve thi
On 8 March 2018 at 09:41, Yeoh, Ee Peng wrote:
> [1] 12587 - [2.4.2 rc2] test_sstate_sametune_samesigs
> (sstatetests.SStateTests)
Can't replicate this reliably with rm_work disabled. Does the QA
autobuilder run with rm_work enabled?
$ oe-selftest -r sstatetests
...
2018-03-08 20:35:41,863 -
The Yocto Project team is moving to a new release planning process and I
want to provide an overview as there will be some things I need from
those of you making changes and adding things to Bugzilla.
Overview:
We are moving to a “Pull” process for planning rather than a “Push”
process. What this
Why are we showing 62 (2%) of the test cases as Idle. (Not Run). Were they
blocked? What happened to them?
Thanks,
Stephen
-Original Message-
From: Yeoh, Ee Peng
Sent: Thursday, March 08, 2018 1:41 AM
To: 'yocto@yoctoproject.org' ; Purdie, Richard
; Jolley, Stephen K ;
Jordan, Robi
On Thu, Mar 8, 2018 at 11:17 AM, Paul Barker wrote:
> On Thu, Mar 8, 2018 at 6:20 AM, kk wrote:
> > This is ok:
> > $ bitbake rpi-config
> > But I check the image directory under workdir, I found nothing in it,
> and no
> > command raspi-config.
> >
>
> The rpi-config recipe creates the conf
On Thu, Mar 8, 2018 at 6:20 AM, kk wrote:
> This is ok:
> $ bitbake rpi-config
> But I check the image directory under workdir, I found nothing in it, and no
> command raspi-config.
>
The rpi-config recipe creates the config.txt file in the
"tmp/deploy/images//bcm2835-bootfiles/" directory (i
Hello All,
Resend the full report for 2.4.2 RC2 with updated information:
https://wiki.yoctoproject.org/wiki/WW10_-_2018-03-05-_Full_Test_Cycle_-_2.4.2_rc2
=== Summary
The QA cycle for release 2.4.2 RC2 was completed including the performance
test. Team had discovered 3 new bugs
19 matches
Mail list logo
