[yocto] Failed to populate SDK after upgrade from sumo to thud

[Stelling2 Carsten]

Hi,

after upgrade from sumo (2.5.2) to thud (2.6.0) populating the SDK fails with 
following error:

ERROR: kernel-devsrc-1.0-r0 do_install: Function failed: do_install
...
cp cannot stat 'arch/arm/tools/syscall*': No such file or directory.

When I remove the following line from the recipe 
meta/recipes-kernel/linux/kernel-devsrc.bb
cp -a --parents arch/arm/tools/syscall* $kerneldir/build
the SDK can be build.

My kernel version is 4.9.26 (no YP kernel).

Possibly, I missed to set a variable, which wasn't needed in sumo, but required 
by thud?

Any help would be very appreciated.

Thanks

Carsten



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

Re: [yocto] Triggering rebuild on a recipe when MACHINE changes

[Burton, Ross]

PACKAGE_ARCH = "${MACHINE}"

The default is that the package is tune-specific, so it won't need to
rebuild on MACHINE changes.

Ross

On Tue, 29 Jan 2019 at 07:09, Kristupas Savickas
 wrote:
>
> I have a few recipes that should rebuild when value of MACHINE variable
> changes. How can this be accomplished? I tried using do_compile[vardeps]
> += "MACHINE", but this didn't seem to have any affect.
>
> --
> Pagarbiai,
> Linux programuotojas
> Kristupas Savickas
> +370 633 36795
>
> --
> ___
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Triggering rebuild on a recipe when MACHINE changes

[Burton, Ross]

I meant PACKAGE_ARCH = "${MACHINE_ARCH}", sorry.

Ross

On Tue, 29 Jan 2019 at 09:57, Burton, Ross  wrote:
>
> PACKAGE_ARCH = "${MACHINE}"
>
> The default is that the package is tune-specific, so it won't need to
> rebuild on MACHINE changes.
>
> Ross
>
> On Tue, 29 Jan 2019 at 07:09, Kristupas Savickas
>  wrote:
> >
> > I have a few recipes that should rebuild when value of MACHINE variable
> > changes. How can this be accomplished? I tried using do_compile[vardeps]
> > += "MACHINE", but this didn't seem to have any affect.
> >
> > --
> > Pagarbiai,
> > Linux programuotojas
> > Kristupas Savickas
> > +370 633 36795
> >
> > --
> > ___
> > yocto mailing list
> > yocto@yoctoproject.org
> > https://lists.yoctoproject.org/listinfo/yocto
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] yocto build ruby-augeas gem

[Ollie]

Hello,

Can anyone please help with install issues when building the
ruby-augeas gem? Seems to be a cross compiler error.

Build error:
...
| Building native extensions.  This could take a while...
| ERROR:  Error installing ruby-augeas-0.5.0.gem:
| ERROR: Failed to build gem native extension.
|
| current directory:
...build/arago-tmp/work/armv7ahf-neon-poky-linux-gnueabi/ruby-augeas/0.5.0-r0/image/usr/lib/ruby/gems/2.4.0/gems/ruby-augeas-0.5.0/ext/augeas
| 
...build/arago-tmp/work/armv7ahf-neon-poky-linux-gnueabi/ruby-augeas/0.5.0-r0/recipe-sysroot-native/usr/bin/ruby
-r ./siteconf20190129-83521-qp9ixi.rb extconf.rb
| *** extconf.rb failed ***
| Could not create Makefile due to some reason, probably lack of necessary
| libraries and/or headers.  Check the mkmf.log file for more details.  You may
| need configuration options.
|
| Provided configuration options:
| --with-opt-dir
| --without-opt-dir
| --with-opt-include
| --without-opt-include=${opt-dir}/include
| --with-opt-lib
| --without-opt-lib=${opt-dir}/lib
| --with-make-prog
| --without-make-prog
| --srcdir=.
| --curdir
| 
--ruby=.../build/arago-tmp/work/armv7ahf-neon-poky-linux-gnueabi/ruby-augeas/0.5.0-r0/recipe-sysroot-native/usr/bin/$(RUBY_BASE_NAME)
| --with-augeas-config
| --without-augeas-config
| --with-pkg-config
| --without-pkg-config
| extconf.rb:27:in `': augeas-devel not installed (RuntimeError)
|
| To see why this extension failed to compile, please check the
mkmf.log which can be found here:

Abbreviated output of mkmf.log:

"pkg-config --exists augeas"
| pkg-config --libs augeas
=> "-laugeas\n"
...
build/arago-tmp/work/armv7ahf-neon-poky-linux-gnueabi/ruby-augeas/0.5.0-r0/recipe-sysroot-native/lib
-Wl,-O1 -fstack-protector -rdynamic -Wl,-export-dynamic -lruby
-laugeas -lpthread -ldl -lcrypt -lm   -lc"
...build/arago-tmp/hosttools/ld: cannot find -laugeas
collect2: error: ld returned 1 exit status
checked program was:
/* begin */
1: #include "ruby.h"
2:
3: int main(int argc, char **argv)
4: {
5:   return 0;
6: }
/* end */

package configuration for augeas is not found

And the recipe:

SUMMARY = "Shadow Password Module"
HOMEPAGE = "http://download.augeas.net/ruby";
LICENSE = "LGPLv2.1"
LIC_FILES_CHKSUM = "file://COPYING;md5=bbb461211a33b134d42ed5ee802b37ff"

SRC_URI = "http://download.augeas.net/ruby/ruby-augeas-${PV}.tgz \
file://add_ruby_augeas_gemspec.patch \
"
SRCREV = "4231a4838fd50022b112838f114ee0586e119605"

SRC_URI[md5sum] = "a132eace43ce13ccd059e22c0b1188ac"
SRC_URI[sha256sum] =
"b82189dcc5cfa18ffaf906f1c5d57e4c3a06054d84100a0699d15fe7d92d9be1"

S = "${WORKDIR}/ruby-augeas-${PV}"

inherit ruby

DEPENDS += " \
ruby \
augeas \
"

RDEPENDS_${PN} += " \
ruby \
   "

RUBY_INSTALL_GEMS = "ruby-augeas-${PV}.gem"

do_compile_prepend() {
   cp ${S}/ext/augeas/extconf.rb ${S}
}

I have also installed the ruby class cross compile patch:
https://lists.yoctoproject.org/pipermail/meta-virtualization/2016-January/001685.html
This patch looks for the extconf.rb file in the root directory, hence
the do_compile_prepend in the recipe.

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

[yocto] (no subject)

[Antonio Santagiuliana]

Hi,
I am missing the steps required to add to an image the support for an RTC
plugged in to I2C1 interface, with autostart.
is there a page with instructions ?
thank you
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] Yocto Project Status WW05'19

[Jolley, Stephen K]

Current Dev Position: YP 2.7 M3

Next Deadline: YP 2.7 M3 Cutoff is Feb. 25, 2019


SWAT Team Rotation:

* SWAT lead is currently: Armin

* SWAT team rotation: Armin -> Anuj on Feb. 1, 2019

* SWAT team rotation: Anuj -> Paul on Feb. 8, 2019

* https://wiki.yoctoproject.org/wiki/Yocto_Build_Failure_Swat_Team


Key Status/Updates:

* YP 2.6.1 should release this week. The transition to automated QA is 
raising some questions about test results but we're working through those.

* YP 2.7 M2 was built and is in QA and is 8% done.  See: 
https://wiki.yoctoproject.org/wiki/2.7_QA_Status

* There have been a further round of gitsm fixes (and new test case 
additions). If anyone is seeing gitsm fetcher issues please report them. There 
are requests to backport these changes to the stable series. This has risks but 
people are reporting bugs there so is something we need to consider.

* There has been little follow up from the last round of AUH patches. 
Please can maintainers work on this and get these submitted!

* There has been little feedback on the proposed virtgl changes, these 
will likely merge as no discussion will be taken to mean there are no 
objections. This will have a performance impact.

* There have been changes to the way the arm tunes are handled which 
merged after much discussion. The solution that merged should be safe and 
uncontroversial but if these do cause problems for anyone, please report ASAP.

* We're getting much improved results from our automated testing but 
these are highlighting a number of problems. There is an email about issues 
found in ptest. The biggest challenge here now is finding people able to step 
up and help improve things.


Planned Releases for YP 2.7:

* YP 2.7 M2 is built and in QA.

* YP 2.7 M2 Release Target is Feb. 1, 2019

* YP 2.7 M3 Cutoff is Feb. 25, 2019

* YP 2.7 M3 Release Target is Mar. 8, 2019

* YP 2.7 M4 Cutoff is Apr. 1, 2019

* YP 2.7 M4 Release Target is Apr. 26, 2019


Planned upcoming dot releases:

* YP 2.6.1 (Thud) will release shortly.

* YP 2.5.3 (Sumo) will be targeted after YP 2.7 M2 is done.

* YP 2.5.4 (Sumo) will be targeted after YP 2.7 M4 is done.

* YP 2.6.2 (Thud) will be targeted after YP 2.5.4 is done.


Tracking Metrics:

* WDD 2393 (last week 2421) 
(https://wiki.yoctoproject.org/charts/combo.html)

* Poky Patch Metrics

oTotal patches found: 1583 (last week 1572)

oPatches in the Pending State: 677 (43%) [last week 677 (43%)]


Key Status Links for YP:

https://wiki.yoctoproject.org/wiki/Yocto_Project_v2.7_Status

https://wiki.yoctoproject.org/wiki/Yocto_2.7_Schedule

https://wiki.yoctoproject.org/wiki/Yocto_2.7_Features


The Status reports are now stored on the wiki at: 
https://wiki.yoctoproject.org/wiki/Weekly_Status


[If anyone has suggestions for other information you'd like to see on this 
weekly status update, let us know!]

Thanks,

Stephen K. Jolley
Yocto Project Program Manager
INTEL, MS JF1-255, 2111 N.E. 25th Avenue, Hillsboro, OR 97124
*Cell:(208) 244-4460
* Email: stephen.k.jol...@intel.com

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

Re: [yocto] (no subject)

[Scott Rifenbark]

Hi,

Have you tried adding the feature through MACHINE_FEATURES variable? (
https://yoctoproject.org/docs/2.6/ref-manual/ref-manual.html#ref-features-machine
and
https://yoctoproject.org/docs/2.6/ref-manual/ref-manual.html#var-MACHINE_FEATURES
).

A developer can probably provide more detailed information Antonio.

Thanks,
Scott

On Tue, Jan 29, 2019 at 8:12 AM Antonio Santagiuliana <
santantonios...@gmail.com> wrote:

> Hi,
> I am missing the steps required to add to an image the support for an RTC
> plugged in to I2C1 interface, with autostart.
> is there a page with instructions ?
> thank you
> --
> ___
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
>
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [YP Core] Thud moved out of active releases

[Scott Rifenbark]

Denis,

I don't understand this myself.  I don't believe 2.6.1 has released just
yet.  I have symlinks set such that the "current" documentation points to
"2.6" so any URL for a manual such as
https://yoctoproject.org/docs/current/ref-manual/ref-manual.html resolves
to the "2.6" manual.

Scott

On Mon, Jan 28, 2019 at 10:33 PM Hopp, Denis 
wrote:

> Hello all,
>
> is it intended that the thud release 2.6 documents overview went
> into archived documents? I can't find any news about it and thud is
> still promoted as latest release on the frontpage.
> (https://www.yoctoproject.org/)
> Or is this standard procedure and 2.6.1 will follow shortly?
>
> Greetings
> --
> ___
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
>
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] : [meta]: [recipes-bsp]: u-boot: update commit id to the latest one of u-boot upstream

[Tom Rini]

On Mon, Jan 28, 2019 at 06:20:02PM +0800, meng...@windriver.com wrote:

> From: Limeng 
> 
> Hi Richard,
> 
> Could you please help to merge this patch into meta/recipes-bsp/u-boot, 
> branch is master?
> 
> There are 2 CVE issues fixing in latest u-boot upstream, so
> update commit id to involve these fixing patches.

With my U-Boot maintainer hat on, NAK.  While there are two CVEs that
have been addressed now (and present for a long while) I would say both:
- The issues themselves are not so catastrophic that you should move to
  a pre-release (I haven't even tagged v2019.04-rc1 yet!) to get them
  nor blindly back-port the changes.  I intentionally didn't apply them
  to the last release as I expected unintended consequences.  Surprise!
  There have been unintended consequences of those changes and I haven't
  pulled in the changes for that just yet.
- Even once the patches to address the CVEs are addressed, I don't see
  why you would move to "top of tree" rather than as is normal practice
  backport the changes.  Simon's fix here is a clear series in patchwork
  (as well as git history) to apply as needed, if after evaluating the
  CVEs it's something that you feel should be addressed in this way and
  not with the workaround (telling U-Boot to load at most $X bytes).

Thanks!

-- 
Tom


signature.asc
Description: PGP signature
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] Deactivating KERNEL_FEATURES

[Chuck Wolber]

This question is with respect to the Yocto thud (2.6.x) branch. I have also
reviewed section 2.3.3 and 2.3.4 of the Kernel Development document
.


My kernel configuration (cfg) seems to be overridden by KERNEL_FEATURES and
it is not clear how to stop this behavior. To take one specific example,
nothing I have tried seems to successfully deactivate the sound
configuration kernel options.

My linux-yocto_4.18.%.bbappend file has the following contents:

FILESEXTRAPATHS_prepend := "${THISDIR}/files:"
SRC_URI_append += "file://0001-kernel-config.cfg"

The following line appears in 0001-kernel-config.cfg:

# CONFIG_SOUND is not set

And yet when I configure the kernel (bitbake -c configure linux-yocto) the
resultant .config in the linux-yocto ${WORKDIR} contains "CONFIG_SOUND=m"
and a plethora of other sound related options that should be turned off. I
did the full kernel build and verified that the .config reflects the final
result in the kernel.

"bitbake -e linux-yocto" contains the following, which seems to explain a
bit:

KERNEL_FEATURES=" features/nfsd/nfsd-enable.scc features/debug/printk.scc
 features/kernel-sample/kernel-sample.scc features/netfilter/netfilter.scc
cfg/virtio.scc cfg/sound.scc cfg/paravirt_kvm.scc "

I should also add that our configuration includes:

DISTRO_FEATURES_remove = " alsa pulseaudio"
DISTRO_FEATURES_BACKFILL_CONSIDERED = " alsa pulseaudio".


How do I ensure that my kernel config gets the last say and is not
overridden?

Thank you,

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

[yocto] adding task before a task T but after all other tasks that T depends on?

[Ulf Samuelsson]

Is there a way to express this?

Assume three classes X,Y,Z, each adding a task.
X: addtask x after S before T
Y: addtask y after S before T
Z: addtask w after S before T

Images might inherit one of the classes X,Y,Z.
Thus x, y, or z might run, but only one of them, and which depends on the image 
I build.

How do I add a task z, which runs after any of x,y,z, but before T?

The list of possible tasks might be extended in the future, so I really would 
want to
specify:  ”addtask w after T[depends] before T” or similar.

Best Regards,
Ulf Samuelsson
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [YP Core] Thud moved out of active releases

[Hopp, Denis]

Hi Scott,

thanks for the verification, I will believe it just went there unintended, 
then. 2.6.1 is not far, anyways. From yesterdays key notes:
"•  YP 2.6.1 should release this week. The transition to automated QA is 
raising some questions about test results but we’re working through those."

> On Tuesday, 29. Jan 2019 at 18:53 by Scott Rifenbark 
> Denis, 
> 
> I don't understand this myself.  I don't believe 2.6.1 has released just yet. 
>  I have symlinks set such that the "current" documentation points to "2.6" so 
> any URL for a manual such as 
> https://yoctoproject.org/docs/current/ref-manual/ref-manual.html resolves to 
> the "2.6" manual.  
> 
> Scott
>> On Mon, Jan 28, 2019 at 10:33 PM Hopp, Denis 
>>  wrote:
>> Hello all,
>> 
>> is it intended that the thud release 2.6 documents overview went 
>> into archived documents? I can't find any news about it and thud is
>> still promoted as latest release on the frontpage.
>> (https://www.yoctoproject.org/)
>> Or is this standard procedure and 2.6.1 will follow shortly?
>> 
>> Greetings


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

Re: [yocto] Deactivating KERNEL_FEATURES

[Bruce Ashfield]

On Tue, Jan 29, 2019 at 9:50 PM Chuck Wolber  wrote:
>
> This question is with respect to the Yocto thud (2.6.x) branch. I have also 
> reviewed section 2.3.3 and 2.3.4 of the Kernel Development document.
>
>
> My kernel configuration (cfg) seems to be overridden by KERNEL_FEATURES and 
> it is not clear how to stop this behavior. To take one specific example, 
> nothing I have tried seems to successfully deactivate the sound configuration 
> kernel options.
>
> My linux-yocto_4.18.%.bbappend file has the following contents:
>
> FILESEXTRAPATHS_prepend := "${THISDIR}/files:"
> SRC_URI_append += "file://0001-kernel-config.cfg"
>
> The following line appears in 0001-kernel-config.cfg:
>
> # CONFIG_SOUND is not set
>
> And yet when I configure the kernel (bitbake -c configure linux-yocto) the 
> resultant .config in the linux-yocto ${WORKDIR} contains "CONFIG_SOUND=m" and 
> a plethora of other sound related options that should be turned off. I did 
> the full kernel build and verified that the .config reflects the final result 
> in the kernel.
>
> "bitbake -e linux-yocto" contains the following, which seems to explain a bit:
>
> KERNEL_FEATURES=" features/nfsd/nfsd-enable.scc features/debug/printk.scc  
> features/kernel-sample/kernel-sample.scc features/netfilter/netfilter.scc 
> cfg/virtio.scc cfg/sound.scc cfg/paravirt_kvm.scc "
>
> I should also add that our configuration includes:
>
> DISTRO_FEATURES_remove = " alsa pulseaudio" 
> DISTRO_FEATURES_BACKFILL_CONSIDERED = " alsa pulseaudio".
>
>
> How do I ensure that my kernel config gets the last say and is not overridden?

KERNEL_FEATURES is a variable like any other. Have you tried using
KERNEL_FEATURES_remove to pull the sound configs out ? We've also only
enabled those features for the qemux86* machines, so it shouldn't be
leaking into other configs .. but as you mentioned, perhaps the sound
configs are just something you picked as an example.

Bruce

>
> Thank you,
>
> ..Ch:W..
> --
> ___
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto



-- 
- Thou shalt not follow the NULL pointer, for chaos and madness await
thee at its end
- "Use the force Harry" - Gandalf, Star Trek II
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto