date:20200825

Re: [yocto] #sdk -Standard SDK build with cmake and meta-clang gives error when I attempt topull in compiler-rt

2020-08-25 Thread Monsees, Steven C (US) via lists.yoctoproject.org

I think there is a problem with compiler-rt component and cmake…

Doing bitbake compiler-rt produces:

Initialising tasks: 100% 
|#| Time: 0:00:00

NOTE: Executing SetScene Tasks

NOTE: Executing RunQueue Tasks

ERROR: compiler-rt-5.0.1+gitAUTOINC+4b38c4038a-r0 do_configure: Function 
failed: do_configure (log file is located at 
/disk0/scratch/smonsees/yocto/workspace_2/meta-bae/meta-limws/builds/sbcb-default/tmp/work/corei7-64-poky-linux/compiler-rt/5.0.1+gitAUTOINC+4b38c4038a-r0/temp/log.do_configure.17534)

ERROR: Logfile of failure stored in: 
/disk0/scratch/smonsees/yocto/workspace_2/meta-bae/meta-limws/builds/sbcb-default/tmp/work/corei7-64-poky-linux/compiler-rt/5.0.1+gitAUTOINC+4b38c4038a-r0/temp/log.do_configure.17534

Log data follows:

| DEBUG: Executing shell function do_configure

| -- The C compiler identification is GNU 7.3.0

| -- The CXX compiler identification is GNU 7.3.0

| -- The ASM compiler identification is GNU

| -- Found assembler: 
/disk0/scratch/smonsees/yocto/workspace_2/meta-bae/meta-limws/builds/sbcb-default/tmp/work/corei7-64-poky-linux/compiler-rt/5.0.1+gitAUTOINC+4b38c4038a-r0/recipe-sysroot-native/usr/bin/x86_64-poky-linux/x86_64-poky-linux-gcc

| -- Check for working C compiler: 
/disk0/scratch/smonsees/yocto/workspace_2/meta-bae/meta-limws/builds/sbcb-default/tmp/work/corei7-64-poky-linux/compiler-rt/5.0.1+gitAUTOINC+4b38c4038a-r0/recipe-sysroot-native/usr/bin/x86_64-poky-linux/x86_64-poky-linux-gcc

| -- Check for working C compiler: 
/disk0/scratch/smonsees/yocto/workspace_2/meta-bae/meta-limws/builds/sbcb-default/tmp/work/corei7-64-poky-linux/compiler-rt/5.0.1+gitAUTOINC+4b38c4038a-r0/recipe-sysroot-native/usr/bin/x86_64-poky-linux/x86_64-poky-linux-gcc
 -- works

| -- Detecting C compiler ABI info

| -- Detecting C compiler ABI info - done

| -- Detecting C compile features

| -- Detecting C compile features - done

| -- Check for working CXX compiler: 
/disk0/scratch/smonsees/yocto/workspace_2/meta-bae/meta-limws/builds/sbcb-default/tmp/work/corei7-64-poky-linux/compiler-rt/5.0.1+gitAUTOINC+4b38c4038a-r0/recipe-sysroot-native/usr/bin/x86_64-poky-linux/x86_64-poky-linux-g++

| -- Check for working CXX compiler: 
/disk0/scratch/smonsees/yocto/workspace_2/meta-bae/meta-limws/builds/sbcb-default/tmp/work/corei7-64-poky-linux/compiler-rt/5.0.1+gitAUTOINC+4b38c4038a-r0/recipe-sysroot-native/usr/bin/x86_64-poky-linux/x86_64-poky-linux-g++
 -- works

| -- Detecting CXX compiler ABI info

| -- Detecting CXX compiler ABI info - done

| -- Detecting CXX compile features

| -- Detecting CXX compile features - done

| -- Looking for unwind.h

| -- Looking for unwind.h - found

| CMake Error at CMakeLists.txt:38 (find_package):

|   By not providing "FindLLVM.cmake" in CMAKE_MODULE_PATH this project has

|   asked CMake to find a package configuration file provided by "LLVM", but

|   CMake did not find one.

|

|   Could not find a package configuration file provided by "LLVM" with any of

|   the following names:

|

| LLVMConfig.cmake

| llvm-config.cmake

|

|   Add the installation prefix of "LLVM" to CMAKE_PREFIX_PATH or set

|   "LLVM_DIR" to a directory containing one of the above files.  If "LLVM"

|   provides a separate development package or SDK, be sure it has been

|   installed.

|

|

| -- Configuring incomplete, errors occurred!

| See also 
"/disk0/scratch/smonsees/yocto/workspace_2/meta-bae/meta-limws/builds/sbcb-default/tmp/work/corei7-64-poky-linux/compiler-rt/5.0.1+gitAUTOINC+4b38c4038a-r0/build/CMakeFiles/CMakeOutput.log".

| WARNING: 
/disk0/scratch/smonsees/yocto/workspace_2/meta-bae/meta-limws/builds/sbcb-default/tmp/work/corei7-64-poky-linux/compiler-rt/5.0.1+gitAUTOINC+4b38c4038a-r0/temp/run.do_configure.17534:1
 exit 1 from 'cmake $oecmake_sitefile 
/disk0/scratch/smonsees/yocto/workspace_2/meta-bae/meta-limws/builds/sbcb-default/tmp/work/corei7-64-poky-linux/compiler-rt/5.0.1+gitAUTOINC+4b38c4038a-r0/git
 -DCMAKE_INSTALL_PREFIX:PATH=/usr -DCMAKE_INSTALL_BINDIR:PATH=bin 
-DCMAKE_INSTALL_SBINDIR:PATH=sbin -DCMAKE_INSTALL_LIBEXECDIR:PATH=libexec 
-DCMAKE_INSTALL_SYSCONFDIR:PATH=/etc -DCMAKE_INSTALL_SHAREDSTATEDIR:PATH=../com 
-DCMAKE_INSTALL_LOCALSTATEDIR:PATH=/var -DCMAKE_INSTALL_LIBDIR:PATH=lib 
-DCMAKE_INSTALL_INCLUDEDIR:PATH=include -DCMAKE_INSTALL_DATAROOTDIR:PATH=share 
-DCMAKE_INSTALL_SO_NO_EXE=0 
-DCMAKE_TOOLCHAIN_FILE=/disk0/scratch/smonsees/yocto/workspace_2/meta-bae/meta-limws/builds/sbcb-default/tmp/work/corei7-64-poky-linux/compiler-rt/5.0.1+gitAUTOINC+4b38c4038a-r0/toolchain.cmake
 -DCMAKE_VERBOSE_MAKEFILE=1 -DCMAKE_NO_SYSTEM_FROM_IMPORTED=1 
-DCOMPILER_RT_STANDALONE_BUILD=ON 
-DCOMPILER_RT_DEFAULT_TARGET_TRIPLE=x86_64-poky-linux 
-DCOMPILER_RT_BUILD_XRAY=OFF -G Ninja ${PACKAGECONFIG_CONFARGS} -Wno-dev'

| ERROR: Function failed: do_configure (log file is located at 
/disk0/scratch/smonsees/yocto/workspace_2/meta-bae/meta-limws/builds/sbcb-default/tmp/work/corei7-64-poky-linux/c

[yocto] [meta-security][PATCH] sssd: Make manpages buildable

2020-08-25 Thread Jonatan Pålsson

Some XML related fixes are needed to make the sssd manpages buildable

Signed-off-by: Jonatan Pålsson 
---
 ...AC_CHECK_FILE-when-building-manpages.patch | 34 +++
 recipes-security/sssd/sssd_1.16.4.bb  |  4 ++-
 2 files changed, 37 insertions(+), 1 deletion(-)
 create mode 100644 
recipes-security/sssd/files/0001-build-Don-t-use-AC_CHECK_FILE-when-building-manpages.patch

diff --git 
a/recipes-security/sssd/files/0001-build-Don-t-use-AC_CHECK_FILE-when-building-manpages.patch
 
b/recipes-security/sssd/files/0001-build-Don-t-use-AC_CHECK_FILE-when-building-manpages.patch
new file mode 100644
index 000..b64670c
--- /dev/null
+++ 
b/recipes-security/sssd/files/0001-build-Don-t-use-AC_CHECK_FILE-when-building-manpages.patch
@@ -0,0 +1,34 @@
+From d54aa109600bcd02bf72cfe64c01935890a102a1 Mon Sep 17 00:00:00 2001
+From: =?UTF-8?q?Jonatan=20P=C3=A5lsson?= 
+Date: Fri, 21 Aug 2020 14:45:10 +0200
+Subject: [PATCH] build: Don't use AC_CHECK_FILE when building manpages
+MIME-Version: 1.0
+Content-Type: text/plain; charset=UTF-8
+Content-Transfer-Encoding: 8bit
+
+AC_CHECK_FILE does not support cross-compilation, and will only check
+the host rootfs. Replace AC_CHECK_FILE with a 'test -f ' instead,
+to allow building manpages when cross-compiling.
+
+Upstream-status: Submitted [https://github.com/SSSD/sssd/pull/5289]
+Signed-off-by: Jonatan Pålsson 
+---
+ src/external/docbook.m4 | 2 +-
+ 1 file changed, 1 insertion(+), 1 deletion(-)
+
+diff --git a/src/external/docbook.m4 b/src/external/docbook.m4
+index deb8632fa..acdc89a68 100644
+--- a/src/external/docbook.m4
 b/src/external/docbook.m4
+@@ -18,7 +18,7 @@ dnl Checks if the XML catalog given by FILE exists and
+ dnl if a particular URI appears in the XML catalog
+ AC_DEFUN([CHECK_STYLESHEET],
+ [
+-  AC_CHECK_FILE($1, [], [AC_MSG_ERROR([could not find XML catalog])])
++  AS_IF([test -f "$1"], [], [AC_MSG_ERROR([could not find XML catalog])])
+ 
+   AC_MSG_CHECKING([for ifelse([$3],,[$2],[$3]) in XML catalog])
+   if AC_RUN_LOG([$XSLTPROC --catalogs --nonet --noout "$2" >&2]); then
+-- 
+2.26.1
+
diff --git a/recipes-security/sssd/sssd_1.16.4.bb 
b/recipes-security/sssd/sssd_1.16.4.bb
index 2c3c803..916f1ac 100644
--- a/recipes-security/sssd/sssd_1.16.4.bb
+++ b/recipes-security/sssd/sssd_1.16.4.bb
@@ -17,6 +17,7 @@ SRC_URI = 
"https://releases.pagure.org/SSSD/${BPN}/${BP}.tar.gz \
file://sssd.conf \
file://volatiles.99_sssd \
file://fix-ldblibdir.patch \
+   
file://0001-build-Don-t-use-AC_CHECK_FILE-when-building-manpages.patch \
"
 
 SRC_URI[md5sum] = "757bbb6f15409d8d075f4f06cb678d50"
@@ -41,7 +42,7 @@ PACKAGECONFIG[autofs] = "--with-autofs, --with-autofs=no"
 PACKAGECONFIG[crypto] = "--with-crypto=libcrypto, , libcrypto"
 PACKAGECONFIG[curl] = "--with-kcm, --without-kcm, curl jansson"
 PACKAGECONFIG[infopipe] = "--with-infopipe, --with-infopipe=no, "
-PACKAGECONFIG[manpages] = "--with-manpages, --with-manpages=no"
+PACKAGECONFIG[manpages] = "--with-manpages, --with-manpages=no, libxslt-native 
docbook-xml-dtd4-native docbook-xsl-stylesheets-native"
 PACKAGECONFIG[nl] = "--with-libnl, --with-libnl=no, libnl"
 PACKAGECONFIG[nscd] = "--with-nscd=${sbindir}, --with-nscd=no "
 PACKAGECONFIG[nss] = "--with-crypto=nss, ,nss,"
@@ -60,6 +61,7 @@ EXTRA_OECONF += " \
 --enable-pammoddir=${base_libdir}/security \
 --without-python2-bindings \
 --without-secrets \
+--with-xml-catalog-path=${STAGING_ETCDIR_NATIVE}/xml/catalog \
 "
 
 do_configure_prepend() {
-- 
2.26.1

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#50352): https://lists.yoctoproject.org/g/yocto/message/50352
Mute This Topic: https://lists.yoctoproject.org/mt/76404961/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[yocto] #yocto #devtool

2020-08-25 Thread majid . nasiry65

Hi
I using a freescale-bsp release (based on Krogoth yocto version ) to build my 
board images, and I need to update some packages (e.g php) to newer versions. 
There is no new version of freescale-bsp that support my board (or I could't 
find it after search a lot!).
What is the best way to update my FSB?

Tanks.
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#50353): https://lists.yoctoproject.org/g/yocto/message/50353
Mute This Topic: https://lists.yoctoproject.org/mt/76405733/21656
Mute #yocto: https://lists.yoctoproject.org/g/yocto+yocto/mutehashtag/yocto
Mute #devtool: https://lists.yoctoproject.org/g/yocto+yocto/mutehashtag/devtool
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[yocto] [devtool] problem with PACKAGE_ARCH and TARGET_OS

2020-08-25 Thread Adrian

Hi,

After recent update of poky, I started to experience an issue with
devtool. Currently, I am using the latest zeus version. I have a
multiconfig environment (Xilinx ZynqMP+ with ARM64 and Microblaze). I am
modifying my recipe compiled from local sources. The custom target
machine configuration sets DEAULTTUNE="cortexa53"

When I call:

$> devtool build peary
$>devtool deploy-target peary root@192.168.33.167

I get the error:

ERROR: No files to deploy - have you built the peary recipe? If so, the
install step has not installed any files.

In fact, I see that 'devtool build' creates image under
'/home/afiergol/poky/build/tmp/work/aarch64-poky-linux/peary/1.0+git999-r0/image',
while 'devtool deploy-target' search for files under
'/home/afiergol/poky/build/tmp/work/cortexa53-poky-linux-gnueabi/peary/1.0+git999-r0/image'

If in the 'peary' recipe I add a line

PACKAGE_ARCH = "${MACHINE_ARCH}"

'devtool deploy-target' starts to search under
'/home/afiergol/poky/build/tmp/work/aarch64-poky-linux-gnueabi/peary/1.0+git999-r0/image'

If further, I fix in the 'peary' recipe:

TARGET_OS = "linux"

'devtool deploy-target' properly deploys the binaries to the target machine.

However, as I explained, I had to fix in the recipe PACKAGE_ARCH and
TARGET_OS variables. It is required only for devtool to work, as bitbake
builds properly my custom Linux image containing the recipe without
those variables being set anywhere in my layer.

Has anybody else experienced a similar issue? Could somebody give a
reference (I didn't find) to documentation which explains why and how
those variables need to be set (I especially concerned about TARGET_OS)?

Regards,

Adrian

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#50354): https://lists.yoctoproject.org/g/yocto/message/50354
Mute This Topic: https://lists.yoctoproject.org/mt/76405761/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[yocto] #yocto #devtool -Update packages

2020-08-25 Thread majid . nasiry65

Hi
I using a freescale-bsp release (based on Krogoth yocto version ) to build my 
board images, and I need to update some packages (e.g php) to newer versions. 
There is no new version of freescale-bsp that support my board (or I could't 
find it after search a lot!).
What is the best way to update my FSB?

Tanks.
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#50355): https://lists.yoctoproject.org/g/yocto/message/50355
Mute This Topic: https://lists.yoctoproject.org/mt/76406012/21656
Mute #yocto: https://lists.yoctoproject.org/g/yocto+yocto/mutehashtag/yocto
Mute #devtool: https://lists.yoctoproject.org/g/yocto+yocto/mutehashtag/devtool
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [yocto] [OE-core] [devtool] problem with PACKAGE_ARCH and TARGET_OS

2020-08-25 Thread Richard Purdie

On Tue, 2020-08-25 at 14:47 +0200, Adrian wrote:
> Hi,
> 
> After recent update of poky, I started to experience an issue with
> devtool. Currently, I am using the latest zeus version. I have a
> multiconfig environment (Xilinx ZynqMP+ with ARM64 and Microblaze). I
> am
> modifying my recipe compiled from local sources. The custom target
> machine configuration sets DEAULTTUNE="cortexa53"
> 
> When I call:
> 
> $> devtool build peary
> $>devtool deploy-target peary root@192.168.33.167
> 
> I get the error:
> 
> ERROR: No files to deploy - have you built the peary recipe? If so,
> the
> install step has not installed any files.
> 
> In fact, I see that 'devtool build' creates image under
> '/home/afiergol/poky/build/tmp/work/aarch64-poky-
> linux/peary/1.0+git999-r0/image',
> while 'devtool deploy-target' search for files under
> '/home/afiergol/poky/build/tmp/work/cortexa53-poky-linux-
> gnueabi/peary/1.0+git999-r0/image'
> 
> If in the 'peary' recipe I add a line
> 
> PACKAGE_ARCH = "${MACHINE_ARCH}"
> 
> 'devtool deploy-target' starts to search under
> '/home/afiergol/poky/build/tmp/work/aarch64-poky-linux-
> gnueabi/peary/1.0+git999-r0/image'
> 
> If further, I fix in the 'peary' recipe:
> 
> TARGET_OS = "linux"
> 
> 'devtool deploy-target' properly deploys the binaries to the target
> machine.
> 
> However, as I explained, I had to fix in the recipe PACKAGE_ARCH and
> TARGET_OS variables. It is required only for devtool to work, as
> bitbake
> builds properly my custom Linux image containing the recipe without
> those variables being set anywhere in my layer.
> 
> Has anybody else experienced a similar issue? Could somebody give a
> reference (I didn't find) to documentation which explains why and how
> those variables need to be set (I especially concerned about
> TARGET_OS)?

devtool is working for other recipes in oe-core so this peary recipe is
probably doing something which is confusing devtool. Or its perhaps the
machine configuration. Is that a public recipe? If not, is there a
recipe you could share which shows the issue?

Basically we need some way to reproduce the issue to be able to
comment. You certainly should not have to set those variables.

Cheers,

Richard

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#50356): https://lists.yoctoproject.org/g/yocto/message/50356
Mute This Topic: https://lists.yoctoproject.org/mt/76406086/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[yocto] Yocto Project Status WW34'20

2020-08-25 Thread Stephen Jolley

Current Dev Position: YP 3.2 M3

Next Deadline: YP 3.2 M3 build date 2020/8/31 - FEATURE FREEZE

 

Next Team Meetings:

*   Bug Triage meeting Thursday  Aug. 27th at 7:30am PDT (
 https://zoom.us/j/454367603)
*   Monthly Project Meeting Tuesday Sept. 1st at 8am PDT (
 https://zoom.us/j/990892712)
*   Weekly Engineering Sync Tuesday  Aug. 25th at 8am PDT (
 https://zoom.us/j/990892712)
*   Twitch -  See https://www.twitch.tv/theyoctojester

 

Key Status/Updates:

*   YP 3.0.4 was released
*   M3 is due to close at the end of the week and this is the feature
freeze point for 3.2
*   After much debugging, we've concluded the bitbake cooker/server
launch process is terminally flawed, you can't fork a python process into
two independent python processes and have the internal python state
machinery work correctly. As such, we're going to have to make some major
changes to the way the bitbake cooker/server startup happens.
*   On a positive note, those server changes have forced many of the
memory resident bitbake bugs to the surface and the new code appears to fix
them, bringing memres bitbake much closer to being usable, maybe even
becoming a default in this release if testing goes well.
*   There is concern about invasive changes like this with regard to
LTS/dunfell where these bitbake bugs are also present. Ultimately we will
make a decision about backporting based upon patch stability and user
feedback from the LTS users.
*   We may delay M3 slightly to enable the bitbake server changes to
merge since these are important for release and work making/merging.
*   The number of autobuilder intermittent bugs has continued to rise
unfortunately.

You can see the list of failures we're continuing to see by searching for
the "AB-INT" tag in bugzilla:

https://bugzilla.yoctoproject.org/buglist.cgi?quicksearch=AB-INT

Help with any of these would be much appreciated, unfortunately it is
proving hard to find anyone interested in helping figure these out and they
significantly hamper our testing.

*   One way to help the project is to help us with bugs that are
currently unassigned but ideally needed during YP 3.2. See:

https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium.2B_3.2_Unassigned_Enhan
cements.2FBugs
*   There is a proposal on the bitbake list to remove globbing support
from file:// urls. Usage of these urls currently breaks source file
checksumming which users don't realize, it can't be fixed in a sane way so
and the most common use cases has easy alternatives such as referencing a
directory as a file:// url without globs so removing globbing support
appears to be the best way forward.
*   We have switched to the 5.8 kernel by default, it's taken a while to
get through all the different issues but we appear to be there now, thanks
to Bruce for working through many of them!
*   Some long standing musl SDK issues should be resolved now.

 

YP 3.2 Milestone Dates:

*   YP 3.2 M3 build date 2020/8/31
*   YP 3.2 M3 Release date 2020/9/11
*   YP 3.2 M4 build date 2020/10/5
*   YP 3.2 M4 Release date 2020/10/30

 

Planned upcoming dot releases:

*   YP 3.0.4 was released
*   YP 3.1.3 build date 2020/9/14
*   YP 3.1.3 release date 2020/9/25

 

Tracking Metrics:

*   WDD 2424 (last week 2429) (

https://wiki.yoctoproject.org/charts/combo.html)
*   Poky Patch Metrics  

*   Total patches found: 1273 (last week 1271)
*   Patches in the Pending State: 502 (39%) [last week 495 (39%)]

 

The Yocto Project's technical governance is through its Technical Steering
Committee, more information is available at:

 
https://wiki.yoctoproject.org/wiki/TSC

 

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

*Cell:(208) 244-4460

* Email:  sjolley.yp...@gmail.com
 

 

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#50357): https://lists.yoctoproject.org/g/yocto/message/50357
Mute This Topic: https://lists.yoctoproject.org/mt/76408036/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [yocto] [OE-core] [devtool] problem with PACKAGE_ARCH and TARGET_OS

2020-08-25 Thread Adrian

Hi Richard,

Thank you for your reply.

On 25.08.2020 15:05, Richard Purdie wrote:
> On Tue, 2020-08-25 at 14:47 +0200, Adrian wrote:
>> Hi,
>>
>> After recent update of poky, I started to experience an issue with
>> devtool. Currently, I am using the latest zeus version. I have a
>> multiconfig environment (Xilinx ZynqMP+ with ARM64 and Microblaze). I
>> am
>> modifying my recipe compiled from local sources. The custom target
>> machine configuration sets DEAULTTUNE="cortexa53"
>>
>> When I call:
>>
>> $> devtool build peary
>> $>devtool deploy-target peary root@192.168.33.167
>>
>> I get the error:
>>
>> ERROR: No files to deploy - have you built the peary recipe? If so,
>> the
>> install step has not installed any files.
>>
>> In fact, I see that 'devtool build' creates image under
>> '/home/afiergol/poky/build/tmp/work/aarch64-poky-
>> linux/peary/1.0+git999-r0/image',
>> while 'devtool deploy-target' search for files under
>> '/home/afiergol/poky/build/tmp/work/cortexa53-poky-linux-
>> gnueabi/peary/1.0+git999-r0/image'
>>
>> If in the 'peary' recipe I add a line
>>
>> PACKAGE_ARCH = "${MACHINE_ARCH}"
>>
>> 'devtool deploy-target' starts to search under
>> '/home/afiergol/poky/build/tmp/work/aarch64-poky-linux-
>> gnueabi/peary/1.0+git999-r0/image'
>>
>> If further, I fix in the 'peary' recipe:
>>
>> TARGET_OS = "linux"
>>
>> 'devtool deploy-target' properly deploys the binaries to the target
>> machine.
>>
>> However, as I explained, I had to fix in the recipe PACKAGE_ARCH and
>> TARGET_OS variables. It is required only for devtool to work, as
>> bitbake
>> builds properly my custom Linux image containing the recipe without
>> those variables being set anywhere in my layer.
>>
>> Has anybody else experienced a similar issue? Could somebody give a
>> reference (I didn't find) to documentation which explains why and how
>> those variables need to be set (I especially concerned about
>> TARGET_OS)?
> devtool is working for other recipes in oe-core so this peary recipe is
> probably doing something which is confusing devtool. Or its perhaps the
> machine configuration. Is that a public recipe? If not, is there a
> recipe you could share which shows the issue?
>
> Basically we need some way to reproduce the issue to be able to
> comment. You certainly should not have to set those variables.
>
> Cheers,
>
> Richard
>
I am enclosing the recipe to this message (peary.bb).

When it comes to the machine configuration, its an extension of
meta-xilinx
(https://github.com/adrianf0/meta-xilinx/tree/rel-v2020.1_fastree3d).
Though, I can't share with you the full conf file, the issue related parts:

#@TYPE: Machine
#@NAME: falcon-zynqmp
#@DESCRIPTION: Machine support for Fastree SoC board.
#
SOC_VARIANT ?= "eg"
DEFAULTTUNE_falcon-zynqmp = "cortexa53"
require conf/machine/include/soc-zynqmp.inc
require conf/machine/include/machine-xilinx-default.inc

MACHINE_FEATURES = "rtc ext2 ext3 vfat"

SERIAL_CONSOLE = "115200 ttyPS0"
SERIAL_CONSOLES_CHECK = "${SERIAL_CONSOLES}"

PREFERRED_PROVIDER_virtual/kernel ?= "linux-xlnx"
PREFERRED_PROVIDER_virtual/bootloader ?= "u-boot-xlnx"

EXTRA_IMAGEDEPENDS += " \
        u-boot-zynq-scr \
        arm-trusted-firmware \
        virtual/boot-bin \
        virtual/bootloader \
        virtual/bitstream \
        "

The local.conf, has nothing special, probably this is the most related
to the issue: MACHINE ??= "falcon-zynqmp"

Regards,

Adrian

DESCRIPTION = "DAQ framework for the Caribou DAQ System"

LICENSE = "LGPLv3"
LIC_FILES_CHKSUM = "file://LICENSE.md;md5=c160dd417c123daff7a62852761d8706"

SRC_URI = "git://gitlab.cern.ch/Caribou/peary.git;protocol=https;"

PV = "1.0+git${SRCPV}"
SRCREV = "2274c0873453dcd667b30ea61779b1273b329f80"

S = "${WORKDIR}/git"

inherit cmake pkgconfig

DEPENDS = "i2c-tools readline libiio"

# Specify any options you want to pass to cmake using EXTRA_OECMAKE:
EXTRA_OECMAKE = " -DBUILD_example=ON \
  -DINSTALL_PREFIX=/usr/ \
  -DCMAKE_SKIP_RPATH=ON \
  -DCMAKE_BUILD_TYPE=Release \
  -DBUILD_server=ON \
   "
FILES_${PN} += "${FILES_SOLIBSDEV}"
FILES_${PN} += "${libdir}/*"
FILES_${PN} += "usr/etc/*"

FILES_${PN}-dev = "${includedir} usr/share/*"

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#50358): https://lists.yoctoproject.org/g/yocto/message/50358
Mute This Topic: https://lists.yoctoproject.org/mt/76406086/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [yocto] #sdk -Standard SDK build with cmake and meta-clang gives error when I attempt topull in compiler-rt

2020-08-25 Thread Monsees, Steven C (US) via lists.yoctoproject.org

How can I resolve the "cmake" error we are seeing ?

* 

What Is this the correct method to add/configure compiler-rt components to work 
in my SDK ?

* 

All are yocto based components, the only llvm components are pulled in by 
meta-clang, what am I expected to edit to resolve ?,  Can someone explain to me 
what this error is attempting to convey, and what I need to do to address ?

* 

Is it correct to expect the cmake and clang components to  be able to  work 
together under Yocto, under the SDK ?

Thanks,

Steve
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#50359): https://lists.yoctoproject.org/g/yocto/message/50359
Mute This Topic: https://lists.yoctoproject.org/mt/76393119/21656
Mute #sdk: https://lists.yoctoproject.org/g/yocto+yocto/mutehashtag/sdk
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[yocto] Mono build has unresolved QA errors

2020-08-25 Thread John Klug

I am building the following version of meta-mono:
commit 7a1e79ec48508edc19a33e8df567c49d0be3eb8c (HEAD, origin/thud)
Merge: 6de5152 9977cab
Author: Alex J Lennon 
Date:   Wed May 27 13:36:43 2020 +0100

The package mono 6.8.123 was built using Ubuntu 16.04.1.

I am seeing RDEPENDS QA errors when building mono in Thud.  This is the first:

ERROR: mono-6.8.0.123-r0 do_package_qa: QA Issue: 
/usr/lib/mono/4.0-api/System.Web.Http.dll contained in package mono-libs-4.0 
requires mono(System.Net.Http), but no providers found in 
RDEPENDS_mono-libs-4.0? [file-rdeps]

These errors are also seen in these two posts that seem to be unresolved:

https://www.yoctoproject.org/pipermail/yocto/2018-February/039930.html

https://www.yoctoproject.org/pipermail/yocto/2018-September/042625.html
 
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#50360): https://lists.yoctoproject.org/g/yocto/message/50360
Mute This Topic: https://lists.yoctoproject.org/mt/76414969/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[yocto] [PATCH 1/2] poky-tiny: set preferred version to 5.8

2020-08-25 Thread Bruce Ashfield

From: Bruce Ashfield 

Even though tiny isn't extensively used (it was referencing a
removed kernel version), it still should be updated to the latest.

Build testing passed with the 5.8 kernel, so we make it the
preferred version.

Signed-off-by: Bruce Ashfield 
---
 meta-poky/conf/distro/poky-tiny.conf | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/meta-poky/conf/distro/poky-tiny.conf 
b/meta-poky/conf/distro/poky-tiny.conf
index c6d4b88f83..57826037f0 100644
--- a/meta-poky/conf/distro/poky-tiny.conf
+++ b/meta-poky/conf/distro/poky-tiny.conf
@@ -38,7 +38,7 @@ TCLIBC = "musl"
 # Distro config is evaluated after the machine config, so we have to explicitly
 # set the kernel provider to override a machine config.
 PREFERRED_PROVIDER_virtual/kernel = "linux-yocto-tiny"
-PREFERRED_VERSION_linux-yocto-tiny ?= "5.0%"
+PREFERRED_VERSION_linux-yocto-tiny ?= "5.8%"
 
 # We can use packagegroup-core-boot, but in the future we may need a new 
packagegroup-core-tiny
 #POKY_DEFAULT_EXTRA_RDEPENDS += "packagegroup-core-boot"
-- 
2.19.1

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#50361): https://lists.yoctoproject.org/g/yocto/message/50361
Mute This Topic: https://lists.yoctoproject.org/mt/76421642/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[yocto] [PATCH 2/2] poky: add preferred version for linux-yocto-rt

2020-08-25 Thread Bruce Ashfield

From: Bruce Ashfield 

As a step towards getting more testing on -rt, we should explicitly
set the preferred version for linux-yocto-rt.

Newly introduced kernels lag in -rt support (as we wait for upstream
projects), so we don't want the version to always be the latest by
default.

Signed-off-by: Bruce Ashfield 
---
 meta-poky/conf/distro/poky.conf | 1 +
 1 file changed, 1 insertion(+)

diff --git a/meta-poky/conf/distro/poky.conf b/meta-poky/conf/distro/poky.conf
index 826f0d633a..b89dc5c1d9 100644
--- a/meta-poky/conf/distro/poky.conf
+++ b/meta-poky/conf/distro/poky.conf
@@ -22,6 +22,7 @@ POKY_DEFAULT_EXTRA_RRECOMMENDS = "kernel-module-af-packet"
 DISTRO_FEATURES ?= "${DISTRO_FEATURES_DEFAULT} ${POKY_DEFAULT_DISTRO_FEATURES}"
 
 PREFERRED_VERSION_linux-yocto ?= "5.8%"
+PREFERRED_VERSION_linux-yocto-rt ?= "5.4%"
 
 SDK_NAME = 
"${DISTRO}-${TCLIBC}-${SDKMACHINE}-${IMAGE_BASENAME}-${TUNE_PKGARCH}-${MACHINE}"
 SDKPATH = "/opt/${DISTRO}/${SDK_VERSION}"
-- 
2.19.1

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#50362): https://lists.yoctoproject.org/g/yocto/message/50362
Mute This Topic: https://lists.yoctoproject.org/mt/76421644/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[yocto] Help with yocto poky quick start

2020-08-25 Thread Brendan Simon (SEPL)


Hi,

I'm new to Yocto and am trying to follow the quick start guide to get up 
and running with poky.  I'm using the latest Dunfel 3.1.2.


I'm running Debian 10 Buster in a VirtualBox VM (guest), on a Windows 10 
Pro (host).


I'm having trouble with the build fetching files and getting checksum 
mismatch, however if I download the troublesome file with wget then the 
checksum is correct.


How do I fix this?

Everything seems very complex with Yocto, but maybe that's because I'm 
new to it.



   $ time bitbake core-image-sato
   Loading cache: 100%
   
|###|
   Time: 0:00:01Loaded 1312 entries from dependency cache.
   NOTE: Resolving any missing task queue dependencies

   Build Configuration:
   BB_VERSION   = "1.46.0"
   BUILD_SYS    = "x86_64-linux"
   NATIVELSBSTRING  = "universal"
   TARGET_SYS   = "x86_64-poky-linux"
   MACHINE  = "qemux86-64"
   DISTRO   = "poky"
   DISTRO_VERSION   = "3.1.2"
   TUNE_FEATURES    = "m64 core2"
   TARGET_FPU   = ""
   meta
   meta-poky
   meta-yocto-bsp   =
   "my-yocto-3.1.2:569b1f5d67c57de957e243997c53ec2f81dc8dfe"

   Initialising tasks: 100%
   |##|
   Time: 0:00:09Checking sstate mirror object availability: 100%
   |##| Time:
   0:36:41Sstate summary: Wanted 2547 Found 0 Missed 2547 Current 228
   (0% match, 8% complete)
   NOTE: Executing Tasks
   WARNING: m4-native-1.4.18-r0 do_fetch: Checksum mismatch for local
   file
   
/home/brendan/SEPL/Projects/Erntec/PMU/yocto_trial/poky/build/downloads/m4-1.4.18.tar.gz
   Cleaning and trying again.
   WARNING: m4-native-1.4.18-r0 do_fetch: Renaming
   
/home/brendan/SEPL/Projects/Erntec/PMU/yocto_trial/poky/build/downloads/m4-1.4.18.tar.gz
   to
   
/home/brendan/SEPL/Projects/Erntec/PMU/yocto_trial/poky/build/downloads/m4-1.4.18.tar.gz_bad-checksum_e64407f9097a607b4463e0c82d898c19b0a3bfd2199d30337b5464d8b416e59c
   WARNING: m4-native-1.4.18-r0 do_fetch: Checksum failure encountered
   with download of https://ftp.gnu.org/gnu/m4/m4-1.4.18.tar.gz - will
   attempt other sources if available
   WARNING: m4-native-1.4.18-r0 do_fetch: Checksum mismatch for local
   file
   
/home/brendan/SEPL/Projects/Erntec/PMU/yocto_trial/poky/build/downloads/m4-1.4.18.tar.gz
   Cleaning and trying again.
   WARNING: m4-native-1.4.18-r0 do_fetch: Renaming
   
/home/brendan/SEPL/Projects/Erntec/PMU/yocto_trial/poky/build/downloads/m4-1.4.18.tar.gz
   to
   
/home/brendan/SEPL/Projects/Erntec/PMU/yocto_trial/poky/build/downloads/m4-1.4.18.tar.gz_bad-checksum_6a1537c79ea613aa70849d8f1f7eeb5a5dbbea3a9527d4aea33a1c8a88e80b9c
   ERROR: m4-native-1.4.18-r0 do_fetch: Checksum failure fetching
   https://ftp.gnu.org/gnu/m4/m4-1.4.18.tar.gz
   ERROR: m4-native-1.4.18-r0 do_fetch: Fetcher failure for URL:
   'https://ftp.gnu.org/gnu/m4/m4-1.4.18.tar.gz'. Checksum mismatch!
   File:
   
'/home/brendan/SEPL/Projects/Erntec/PMU/yocto_trial/poky/build/downloads/m4-1.4.18.tar.gz'
   has md5 checksum 6a289f7da1478d63683eb4ad976c3c99 when
   a09db287adf4e12a035029002d28 was expected
   File:
   
'/home/brendan/SEPL/Projects/Erntec/PMU/yocto_trial/poky/build/downloads/m4-1.4.18.tar.gz'
   has sha256 checksum
   6a1537c79ea613aa70849d8f1f7eeb5a5dbbea3a9527d4aea33a1c8a88e80b9c
   when
   ab2633921a5cd38e48797bf5521ad259bdc4b979078034a3b790d7fec5493fab was
   expected
   If this change is expected (e.g. you have upgraded to a new version
   without updating the checksums) then you can use these lines within
   the recipe:
   SRC_URI[sha256sum] =
   "6a1537c79ea613aa70849d8f1f7eeb5a5dbbea3a9527d4aea33a1c8a88e80b9c"
   Otherwise you should retry the download and/or check with upstream
   to determine if the file has become corrupted or--- Starting bitbake
   server pid 6121 at 2020-08-25 19:29:32.273325 ---
   Started bitbake server pid 6121
   DEBUG: BBCooker starting 1598398172.2817702
   DEBUG: BBCooker pyinotify1 1598398172.2922668
   DEBUG: BBCooker pyinotify2 1598398172.2926114
   DEBUG: BBCooker pyinotify3 1598398172.2971811
   DEBUG: BBCooker pyinotify complete 1598398172.2975075
   DEBUG: Found bblayers.conf
   
(/home/brendan/SEPL/Projects/Erntec/PMU/yocto_trial/poky/build/conf/bblayers.conf)

   DEBUG: Adding layer
   /home/brendan/SEPL/Projects/Erntec/PMU/yocto_trial/poky/meta
   DEBUG: Adding layer
   /home/brendan/SEPL/Projects/Erntec/PMU/yocto_trial/poky/meta-poky
   DEBUG: Adding layer
   /home/brendan/SEPL/Projects/Erntec/PMU/yocto_trial/poky/meta-yocto-bsp
   DEBUG: CONF
   
/home/brendan/SEPL/Projects/Erntec/PMU/yocto_trial/poky/meta/conf/bitbake.conf:755:
   including conf/abi_version.conf
   DEBUG: CONF
   
/home/brendan/SEPL/Projects/Erntec/PMU/yocto_trial/poky/meta/conf/bitbake.conf:756:
   including conf/site.conf
   DEBUG: CONF file 'conf/site.conf' not found
   DE

[yocto] [PATCH] meta-yocto-bsp: Bump to the v5.8 kernel

2020-08-25 Thread Kevin Hao

Boot test for all the supported boards. There is a kernel config
check warning for beaglebone-yocto, the fix [1] has been sent to
kernel-meta for merging.

[1] https://lists.yoctoproject.org/g/linux-yocto/message/8992

Signed-off-by: Kevin Hao 
---
 .../conf/machine/beaglebone-yocto.conf|  2 +-
 meta-yocto-bsp/conf/machine/edgerouter.conf   |  2 +-
 .../linux/linux-yocto_5.8.bbappend| 23 +++
 3 files changed, 25 insertions(+), 2 deletions(-)
 create mode 100644 meta-yocto-bsp/recipes-kernel/linux/linux-yocto_5.8.bbappend

diff --git a/meta-yocto-bsp/conf/machine/beaglebone-yocto.conf 
b/meta-yocto-bsp/conf/machine/beaglebone-yocto.conf
index 5b481434bd89..b7defb0d0170 100644
--- a/meta-yocto-bsp/conf/machine/beaglebone-yocto.conf
+++ b/meta-yocto-bsp/conf/machine/beaglebone-yocto.conf
@@ -24,7 +24,7 @@ SERIAL_CONSOLES ?= "115200;ttyS0 115200;ttyO0 115200;ttyAMA0"
 SERIAL_CONSOLES_CHECK = "${SERIAL_CONSOLES}"
 
 PREFERRED_PROVIDER_virtual/kernel ?= "linux-yocto"
-PREFERRED_VERSION_linux-yocto ?= "5.4%"
+PREFERRED_VERSION_linux-yocto ?= "5.8%"
 
 KERNEL_IMAGETYPE = "zImage"
 KERNEL_DEVICETREE = "am335x-bone.dtb am335x-boneblack.dtb am335x-bonegreen.dtb"
diff --git a/meta-yocto-bsp/conf/machine/edgerouter.conf 
b/meta-yocto-bsp/conf/machine/edgerouter.conf
index d6fd934fa583..75bc5e5f28e7 100644
--- a/meta-yocto-bsp/conf/machine/edgerouter.conf
+++ b/meta-yocto-bsp/conf/machine/edgerouter.conf
@@ -11,7 +11,7 @@ KERNEL_ALT_IMAGETYPE = "vmlinux.bin"
 KERNEL_IMAGE_STRIP_EXTRA_SECTIONS  = ".comment"
 
 PREFERRED_PROVIDER_virtual/kernel ?= "linux-yocto"
-PREFERRED_VERSION_linux-yocto ?= "5.4%"
+PREFERRED_VERSION_linux-yocto ?= "5.8%"
 
 SERIAL_CONSOLES = "115200;ttyS0"
 USE_VT ?= "0"
diff --git a/meta-yocto-bsp/recipes-kernel/linux/linux-yocto_5.8.bbappend 
b/meta-yocto-bsp/recipes-kernel/linux/linux-yocto_5.8.bbappend
new file mode 100644
index ..5d844423afce
--- /dev/null
+++ b/meta-yocto-bsp/recipes-kernel/linux/linux-yocto_5.8.bbappend
@@ -0,0 +1,23 @@
+KBRANCH_genericx86  = "v5.8/standard/base"
+KBRANCH_genericx86-64  = "v5.8/standard/base"
+KBRANCH_edgerouter = "v5.8/standard/edgerouter"
+KBRANCH_beaglebone-yocto = "v5.8/standard/beaglebone"
+
+KMACHINE_genericx86 ?= "common-pc"
+KMACHINE_genericx86-64 ?= "common-pc-64"
+KMACHINE_beaglebone-yocto ?= "beaglebone"
+
+SRCREV_machine_genericx86 ?= "912adf166eb0688e011154048f5fa0e5863249c3"
+SRCREV_machine_genericx86-64 ?= "912adf166eb0688e011154048f5fa0e5863249c3"
+SRCREV_machine_edgerouter ?= "912adf166eb0688e011154048f5fa0e5863249c3"
+SRCREV_machine_beaglebone-yocto ?= "912adf166eb0688e011154048f5fa0e5863249c3"
+
+COMPATIBLE_MACHINE_genericx86 = "genericx86"
+COMPATIBLE_MACHINE_genericx86-64 = "genericx86-64"
+COMPATIBLE_MACHINE_edgerouter = "edgerouter"
+COMPATIBLE_MACHINE_beaglebone-yocto = "beaglebone-yocto"
+
+LINUX_VERSION_genericx86 = "5.8.2"
+LINUX_VERSION_genericx86-64 = "5.8.2"
+LINUX_VERSION_edgerouter = "5.8.2"
+LINUX_VERSION_beaglebone-yocto = "5.8.2"
-- 
2.26.2

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#50364): https://lists.yoctoproject.org/g/yocto/message/50364
Mute This Topic: https://lists.yoctoproject.org/mt/76423360/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [yocto] #yocto #devtool -Update packages

2020-08-25 Thread Khem Raj




On 8/25/20 6:01 AM, majid.nasir...@gmail.com wrote:

Hi
I using a freescale-bsp release (based on Krogoth yocto version) to 
build my board images, and I need to update some packages (e.g php) to 
newer versions. There is no new version of freescale-bsp that support my 
board (or I could't find it after search a lot!).

What is the best way to update my FSB?



look at layer index
http://layers.openembedded.org/layerindex/recipe/39864/

and you would need to then do a backport of desired version.


Tanks.



-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#50365): https://lists.yoctoproject.org/g/yocto/message/50365
Mute This Topic: https://lists.yoctoproject.org/mt/76406012/21656
Mute #yocto: https://lists.yoctoproject.org/g/yocto+yocto/mutehashtag/yocto
Mute #devtool: https://lists.yoctoproject.org/g/yocto+yocto/mutehashtag/devtool
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [yocto] Help with yocto poky quick start

2020-08-25 Thread Brendan Simon (SEPL)


Hi Erik,

Nope.  It's ot a HTML file.  It is (they are) archives with a 
files/directories for m4 sources.


   $ find -name "m4*"
   
./m4-1.4.18.tar.gz_bad-checksum_6a1537c79ea613aa70849d8f1f7eeb5a5dbbea3a9527d4aea33a1c8a88e80b9c
   
./m4-1.4.18.tar.gz_bad-checksum_e64407f9097a607b4463e0c82d898c19b0a3bfd2199d30337b5464d8b416e59c
   
./m4-1.4.18.tar.gz_bad-checksum_d8a6ce0c8a97f9f13af9d15d72e4e398daf24ceba4afa4c6925314c39bd81206
   
./m4-1.4.18.tar.gz_bad-checksum_b295109d6ddd3c387b794fb6e4b4dfe31d42991a6a537bd92b1a385c2ed3b616

   $ find -name "m4*" | xargs file
   
./m4-1.4.18.tar.gz_bad-checksum_6a1537c79ea613aa70849d8f1f7eeb5a5dbbea3a9527d4aea33a1c8a88e80b9c:
   gzip compressed data, max compression, from Unix, original size 9789440
   
./m4-1.4.18.tar.gz_bad-checksum_e64407f9097a607b4463e0c82d898c19b0a3bfd2199d30337b5464d8b416e59c:
   gzip compressed data, max compression, from Unix, original size 9789440
   
./m4-1.4.18.tar.gz_bad-checksum_d8a6ce0c8a97f9f13af9d15d72e4e398daf24ceba4afa4c6925314c39bd81206:
   gzip compressed data, max compression, from Unix, original size 9789440
   
./m4-1.4.18.tar.gz_bad-checksum_b295109d6ddd3c387b794fb6e4b4dfe31d42991a6a537bd92b1a385c2ed3b616:
   gzip compressed data, max compression, from Unix, original size 9789440

   $ tar ztvf
   
m4-1.4.18.tar.gz_bad-checksum_6a1537c79ea613aa70849d8f1f7eeb5a5dbbea3a9527d4aea33a1c8a88e80b9c
   | head
   drwxrwxr-x 0/0   0 2016-12-31 17:37 m4-1.4.18/
   -rw-rw-r-- 0/0  195907 2016-12-31 17:00 m4-1.4.18/ChangeLog-2014
   -rw-rw-r-- 0/0   63687 2016-12-31 16:34 m4-1.4.18/maint.mk
   -rw-rw-r-- 0/0    3912 2016-12-31 17:37 m4-1.4.18/ChangeLog
   -rw-rw-r-- 0/0   69156 2016-12-31 17:25 m4-1.4.18/aclocal.m4
   -rw-rw-r-- 0/0    2590 2016-12-29 15:32 m4-1.4.18/BACKLOG
   drwxrwxr-x 0/0   0 2016-12-31 17:37 m4-1.4.18/tests/
   -rw-rw-r-- 0/0    3126 2016-12-31 08:54
   m4-1.4.18/tests/getcwd-lgpl.c
   -rw-rw-r-- 0/0    6134 2016-12-31 08:54
   m4-1.4.18/tests/test-dup2.c
   -rw-rw-r-- 0/0    4998 2016-12-31 08:54
   m4-1.4.18/tests/test-dup-safer.c

Brendan.

--


On 26/08/2020 4:22 pm, Erik Botö wrote:

Hi Brendan,

Could you inspect the file in
/home/brendan/SEPL/Projects/Erntec/PMU/yocto_trial/poky/build/downloads/m4-1.4.18.tar.gz
to see if it is some kind of HTML file stating a download error?

Check the file size, if it's small it's probably an error so open it
using an editor to see if you get any hints. Many corporate networks
will require the use of a proxy server, see e.g.
https://wiki.yoctoproject.org/wiki/Working_Behind_a_Network_Proxy for
hints on that.

Cheers,
Erik

On Wed, Aug 26, 2020 at 7:36 AM Brendan Simon (SEPL)
 wrote:

Hi,

I'm new to Yocto and am trying to follow the quick start guide to get up and 
running with poky.  I'm using the latest Dunfel 3.1.2.

I'm running Debian 10 Buster in a VirtualBox VM (guest), on a Windows 10 Pro 
(host).

I'm having trouble with the build fetching files and getting checksum mismatch, 
however if I download the troublesome file with wget then the checksum is 
correct.

How do I fix this?

Everything seems very complex with Yocto, but maybe that's because I'm new to 
it.


$ time bitbake core-image-sato
Loading cache: 100% 
|###|
 Time: 0:00:01Loaded 1312 entries from dependency cache.
NOTE: Resolving any missing task queue dependencies

Build Configuration:
BB_VERSION   = "1.46.0"
BUILD_SYS= "x86_64-linux"
NATIVELSBSTRING  = "universal"
TARGET_SYS   = "x86_64-poky-linux"
MACHINE  = "qemux86-64"
DISTRO   = "poky"
DISTRO_VERSION   = "3.1.2"
TUNE_FEATURES= "m64 core2"
TARGET_FPU   = ""
meta
meta-poky
meta-yocto-bsp   = "my-yocto-3.1.2:569b1f5d67c57de957e243997c53ec2f81dc8dfe"

Initialising tasks: 100% 
|##| 
Time: 0:00:09Checking sstate mirror object availability: 100% 
|##| Time: 0:36:41Sstate 
summary: Wanted 2547 Found 0 Missed 2547 Current 228 (0% match, 8% complete)
NOTE: Executing Tasks
WARNING: m4-native-1.4.18-r0 do_fetch: Checksum mismatch for local file 
/home/brendan/SEPL/Projects/Erntec/PMU/yocto_trial/poky/build/downloads/m4-1.4.18.tar.gz
Cleaning and trying again.
WARNING: m4-native-1.4.18-r0 do_fetch: Renaming 
/home/brendan/SEPL/Projects/Erntec/PMU/yocto_trial/poky/build/downloads/m4-1.4.18.tar.gz
 to 
/home/brendan/SEPL/Projects/Erntec/PMU/yocto_trial/poky/build/downloads/m4-1.4.18.tar.gz_bad-checksum_e64407f9097a607b4463e0c82d898c19b0a3bfd2199d30337b5464d8b416e59c
WARNING: m4-native-1.4.18-r0 do_fetch: Checksum failure encountered with 
download of https://ftp.gnu.org/gnu/m4/m4-1.4.18.tar.gz - will attempt other 
sources if available
WARNING: m4-native-1.4.18-r0 do_fetch: Checksum mismatch for local file

Re: [yocto] #sdk -Standard SDK build with cmake and meta-clang gives error when I attempt topull in compiler-rt

2020-08-25 Thread Khem Raj




On 8/25/20 3:47 AM, Monsees, Steven C (US) via lists.yoctoproject.org wrote:

I think there is a problem with compiler-rt component and cmake…



it seems to be using gcc to compile, perhaps you can add TOOLCHAIN = 
"claing" inside compiler-rt recipe and see if it makes progress.



Doing bitbake compiler-rt produces:

Initialising tasks: 100% 
|#| Time: 0:00:00


NOTE: Executing SetScene Tasks

NOTE: Executing RunQueue Tasks

ERROR: compiler-rt-5.0.1+gitAUTOINC+4b38c4038a-r0 do_configure: Function 
failed: do_configure (log file is located at 
/disk0/scratch/smonsees/yocto/workspace_2/meta-bae/meta-limws/builds/sbcb-default/tmp/work/corei7-64-poky-linux/compiler-rt/5.0.1+gitAUTOINC+4b38c4038a-r0/temp/log.do_configure.17534)


ERROR: Logfile of failure stored in: 
/disk0/scratch/smonsees/yocto/workspace_2/meta-bae/meta-limws/builds/sbcb-default/tmp/work/corei7-64-poky-linux/compiler-rt/5.0.1+gitAUTOINC+4b38c4038a-r0/temp/log.do_configure.17534


Log data follows:

| DEBUG: Executing shell function do_configure

| -- The C compiler identification is GNU 7.3.0

| -- The CXX compiler identification is GNU 7.3.0

| -- The ASM compiler identification is GNU

| -- Found assembler: 
/disk0/scratch/smonsees/yocto/workspace_2/meta-bae/meta-limws/builds/sbcb-default/tmp/work/corei7-64-poky-linux/compiler-rt/5.0.1+gitAUTOINC+4b38c4038a-r0/recipe-sysroot-native/usr/bin/x86_64-poky-linux/x86_64-poky-linux-gcc


| -- Check for working C compiler: 
/disk0/scratch/smonsees/yocto/workspace_2/meta-bae/meta-limws/builds/sbcb-default/tmp/work/corei7-64-poky-linux/compiler-rt/5.0.1+gitAUTOINC+4b38c4038a-r0/recipe-sysroot-native/usr/bin/x86_64-poky-linux/x86_64-poky-linux-gcc


| -- Check for working C compiler: 
/disk0/scratch/smonsees/yocto/workspace_2/meta-bae/meta-limws/builds/sbcb-default/tmp/work/corei7-64-poky-linux/compiler-rt/5.0.1+gitAUTOINC+4b38c4038a-r0/recipe-sysroot-native/usr/bin/x86_64-poky-linux/x86_64-poky-linux-gcc 
-- works


| -- Detecting C compiler ABI info

| -- Detecting C compiler ABI info - done

| -- Detecting C compile features

| -- Detecting C compile features - done

| -- Check for working CXX compiler: 
/disk0/scratch/smonsees/yocto/workspace_2/meta-bae/meta-limws/builds/sbcb-default/tmp/work/corei7-64-poky-linux/compiler-rt/5.0.1+gitAUTOINC+4b38c4038a-r0/recipe-sysroot-native/usr/bin/x86_64-poky-linux/x86_64-poky-linux-g++


| -- Check for working CXX compiler: 
/disk0/scratch/smonsees/yocto/workspace_2/meta-bae/meta-limws/builds/sbcb-default/tmp/work/corei7-64-poky-linux/compiler-rt/5.0.1+gitAUTOINC+4b38c4038a-r0/recipe-sysroot-native/usr/bin/x86_64-poky-linux/x86_64-poky-linux-g++ 
-- works


| -- Detecting CXX compiler ABI info

| -- Detecting CXX compiler ABI info - done

| -- Detecting CXX compile features

| -- Detecting CXX compile features - done

| -- Looking for unwind.h

| -- Looking for unwind.h - found

| CMake Error at CMakeLists.txt:38 (find_package):

|   By not providing "FindLLVM.cmake" in CMAKE_MODULE_PATH this project has

|   asked CMake to find a package configuration file provided by "LLVM", but

|   CMake did not find one.

|

|   Could not find a package configuration file provided by "LLVM" with 
any of


|   the following names:

|

| LLVMConfig.cmake

| llvm-config.cmake

|

|   Add the installation prefix of "LLVM" to CMAKE_PREFIX_PATH or set

|   "LLVM_DIR" to a directory containing one of the above files.  If "LLVM"

|   provides a separate development package or SDK, be sure it has been

|   installed.

|

|

| -- Configuring incomplete, errors occurred!

| See also 
"/disk0/scratch/smonsees/yocto/workspace_2/meta-bae/meta-limws/builds/sbcb-default/tmp/work/corei7-64-poky-linux/compiler-rt/5.0.1+gitAUTOINC+4b38c4038a-r0/build/CMakeFiles/CMakeOutput.log".


| WARNING: 
/disk0/scratch/smonsees/yocto/workspace_2/meta-bae/meta-limws/builds/sbcb-default/tmp/work/corei7-64-poky-linux/compiler-rt/5.0.1+gitAUTOINC+4b38c4038a-r0/temp/run.do_configure.17534:1 
exit 1 from 'cmake $oecmake_sitefile 
/disk0/scratch/smonsees/yocto/workspace_2/meta-bae/meta-limws/builds/sbcb-default/tmp/work/corei7-64-poky-linux/compiler-rt/5.0.1+gitAUTOINC+4b38c4038a-r0/git 
-DCMAKE_INSTALL_PREFIX:PATH=/usr -DCMAKE_INSTALL_BINDIR:PATH=bin 
-DCMAKE_INSTALL_SBINDIR:PATH=sbin 
-DCMAKE_INSTALL_LIBEXECDIR:PATH=libexec 
-DCMAKE_INSTALL_SYSCONFDIR:PATH=/etc 
-DCMAKE_INSTALL_SHAREDSTATEDIR:PATH=../com 
-DCMAKE_INSTALL_LOCALSTATEDIR:PATH=/var -DCMAKE_INSTALL_LIBDIR:PATH=lib 
-DCMAKE_INSTALL_INCLUDEDIR:PATH=include 
-DCMAKE_INSTALL_DATAROOTDIR:PATH=share -DCMAKE_INSTALL_SO_NO_EXE=0 
-DCMAKE_TOOLCHAIN_FILE=/disk0/scratch/smonsees/yocto/workspace_2/meta-bae/meta-limws/builds/sbcb-default/tmp/work/corei7-64-poky-linux/compiler-rt/5.0.1+gitAUTOINC+4b38c4038a-r0/toolchain.cmake 
-DCMAKE_VERBOSE_MAKEFILE=1 -DCMAKE_NO_SYSTEM_FROM_IMPORTED=1 
-DCOMPILER_RT_STANDALONE_BUILD=ON 
-DCOMPILER_RT_DEFAULT_TARGET_TRIPLE=x86_64-poky-linux 
-DCOMPILER_RT_BUIL

Re: [yocto] Help with yocto poky quick start

2020-08-25 Thread Khem Raj




On 8/25/20 11:41 PM, Brendan Simon (SEPL) wrote:

Hi Erik,

Nope.  It's ot a HTML file.  It is (they are) archives with a 
files/directories for m4 sources.


$ find -name "m4*"

./m4-1.4.18.tar.gz_bad-checksum_6a1537c79ea613aa70849d8f1f7eeb5a5dbbea3a9527d4aea33a1c8a88e80b9c

./m4-1.4.18.tar.gz_bad-checksum_e64407f9097a607b4463e0c82d898c19b0a3bfd2199d30337b5464d8b416e59c

./m4-1.4.18.tar.gz_bad-checksum_d8a6ce0c8a97f9f13af9d15d72e4e398daf24ceba4afa4c6925314c39bd81206

./m4-1.4.18.tar.gz_bad-checksum_b295109d6ddd3c387b794fb6e4b4dfe31d42991a6a537bd92b1a385c2ed3b616

$ find -name "m4*" | xargs file

./m4-1.4.18.tar.gz_bad-checksum_6a1537c79ea613aa70849d8f1f7eeb5a5dbbea3a9527d4aea33a1c8a88e80b9c:
gzip compressed data, max compression, from Unix, original size 9789440

./m4-1.4.18.tar.gz_bad-checksum_e64407f9097a607b4463e0c82d898c19b0a3bfd2199d30337b5464d8b416e59c:
gzip compressed data, max compression, from Unix, original size 9789440

./m4-1.4.18.tar.gz_bad-checksum_d8a6ce0c8a97f9f13af9d15d72e4e398daf24ceba4afa4c6925314c39bd81206:
gzip compressed data, max compression, from Unix, original size 9789440

./m4-1.4.18.tar.gz_bad-checksum_b295109d6ddd3c387b794fb6e4b4dfe31d42991a6a537bd92b1a385c2ed3b616:
gzip compressed data, max compression, from Unix, original size 9789440

$ tar ztvf

m4-1.4.18.tar.gz_bad-checksum_6a1537c79ea613aa70849d8f1f7eeb5a5dbbea3a9527d4aea33a1c8a88e80b9c
| head
drwxrwxr-x 0/0   0 2016-12-31 17:37 m4-1.4.18/
-rw-rw-r-- 0/0  195907 2016-12-31 17:00 m4-1.4.18/ChangeLog-2014
-rw-rw-r-- 0/0   63687 2016-12-31 16:34 m4-1.4.18/maint.mk
-rw-rw-r-- 0/0    3912 2016-12-31 17:37 m4-1.4.18/ChangeLog
-rw-rw-r-- 0/0   69156 2016-12-31 17:25 m4-1.4.18/aclocal.m4
-rw-rw-r-- 0/0    2590 2016-12-29 15:32 m4-1.4.18/BACKLOG
drwxrwxr-x 0/0   0 2016-12-31 17:37 m4-1.4.18/tests/
-rw-rw-r-- 0/0    3126 2016-12-31 08:54
m4-1.4.18/tests/getcwd-lgpl.c
-rw-rw-r-- 0/0    6134 2016-12-31 08:54
m4-1.4.18/tests/test-dup2.c
-rw-rw-r-- 0/0    4998 2016-12-31 08:54
m4-1.4.18/tests/test-dup-safer.c


everytime checksum is changing, thats not normal. Have you tried

bitbake -cccleanall m4 ; bitbake m4

and see if that helps ?

secondly, check for any mirrors or pre-mirror settings your distro might 
have which is getting this tarball from elsewhere, the checksums are 
correctly mentioned in recipe, it should match those of downloaded tarball.




Brendan.

--


On 26/08/2020 4:22 pm, Erik Botö wrote:

Hi Brendan,

Could you inspect the file in
/home/brendan/SEPL/Projects/Erntec/PMU/yocto_trial/poky/build/downloads/m4-1.4.18.tar.gz
to see if it is some kind of HTML file stating a download error?

Check the file size, if it's small it's probably an error so open it
using an editor to see if you get any hints. Many corporate networks
will require the use of a proxy server, see e.g.
https://wiki.yoctoproject.org/wiki/Working_Behind_a_Network_Proxy  for
hints on that.

Cheers,
Erik

On Wed, Aug 26, 2020 at 7:36 AM Brendan Simon (SEPL)
  wrote:

Hi,

I'm new to Yocto and am trying to follow the quick start guide to get up and 
running with poky.  I'm using the latest Dunfel 3.1.2.

I'm running Debian 10 Buster in a VirtualBox VM (guest), on a Windows 10 Pro 
(host).

I'm having trouble with the build fetching files and getting checksum mismatch, 
however if I download the troublesome file with wget then the checksum is 
correct.

How do I fix this?

Everything seems very complex with Yocto, but maybe that's because I'm new to 
it.


$ time bitbake core-image-sato
Loading cache: 100% 
|###|
 Time: 0:00:01Loaded 1312 entries from dependency cache.
NOTE: Resolving any missing task queue dependencies

Build Configuration:
BB_VERSION   = "1.46.0"
BUILD_SYS= "x86_64-linux"
NATIVELSBSTRING  = "universal"
TARGET_SYS   = "x86_64-poky-linux"
MACHINE  = "qemux86-64"
DISTRO   = "poky"
DISTRO_VERSION   = "3.1.2"
TUNE_FEATURES= "m64 core2"
TARGET_FPU   = ""
meta
meta-poky
meta-yocto-bsp   = "my-yocto-3.1.2:569b1f5d67c57de957e243997c53ec2f81dc8dfe"

Initialising tasks: 100% 
|##| 
Time: 0:00:09Checking sstate mirror object availability: 100% 
|##| Time: 0:36:41Sstate 
summary: Wanted 2547 Found 0 Missed 2547 Current 228 (0% match, 8% complete)
NOTE: Executing Tasks
WARNING: m4-native-1.4.18-r0 do_fetch: Checksum mismatch for local file 
/home/brendan/SEPL/Projects/Erntec/PMU/yocto_trial/poky/build/downloads/m4-1.4.18.tar.gz
Cleaning and trying again.
WARNING: m4-native-1.4.18-r0 do_fetch: Renaming 
/home/brendan/SEPL/Projects/Erntec/PMU/yocto_trial/poky/build/download

Re: [yocto] Help with yocto poky quick start

2020-08-25 Thread Josef Holzmayr-Khosh Amoz

Howdy!

Its a long shot, but are you also using WSL2 on the Windows 10 Host?
In that case, downloads into a VirtualBox VM can be corrupted, see
https://www.virtualbox.org/ticket/19695

Greetz

Am Mi., 26. Aug. 2020 um 08:41 Uhr schrieb Brendan Simon (SEPL)
:
>
> Hi Erik,
>
> Nope.  It's ot a HTML file.  It is (they are) archives with a 
> files/directories for m4 sources.
>
> $ find -name "m4*"
> ./m4-1.4.18.tar.gz_bad-checksum_6a1537c79ea613aa70849d8f1f7eeb5a5dbbea3a9527d4aea33a1c8a88e80b9c
> ./m4-1.4.18.tar.gz_bad-checksum_e64407f9097a607b4463e0c82d898c19b0a3bfd2199d30337b5464d8b416e59c
> ./m4-1.4.18.tar.gz_bad-checksum_d8a6ce0c8a97f9f13af9d15d72e4e398daf24ceba4afa4c6925314c39bd81206
> ./m4-1.4.18.tar.gz_bad-checksum_b295109d6ddd3c387b794fb6e4b4dfe31d42991a6a537bd92b1a385c2ed3b616
>
> $ find -name "m4*" | xargs file
> ./m4-1.4.18.tar.gz_bad-checksum_6a1537c79ea613aa70849d8f1f7eeb5a5dbbea3a9527d4aea33a1c8a88e80b9c:
>  gzip compressed data, max compression, from Unix, original size 9789440
> ./m4-1.4.18.tar.gz_bad-checksum_e64407f9097a607b4463e0c82d898c19b0a3bfd2199d30337b5464d8b416e59c:
>  gzip compressed data, max compression, from Unix, original size 9789440
> ./m4-1.4.18.tar.gz_bad-checksum_d8a6ce0c8a97f9f13af9d15d72e4e398daf24ceba4afa4c6925314c39bd81206:
>  gzip compressed data, max compression, from Unix, original size 9789440
> ./m4-1.4.18.tar.gz_bad-checksum_b295109d6ddd3c387b794fb6e4b4dfe31d42991a6a537bd92b1a385c2ed3b616:
>  gzip compressed data, max compression, from Unix, original size 9789440
>
> $ tar ztvf 
> m4-1.4.18.tar.gz_bad-checksum_6a1537c79ea613aa70849d8f1f7eeb5a5dbbea3a9527d4aea33a1c8a88e80b9c
>  | head
> drwxrwxr-x 0/0   0 2016-12-31 17:37 m4-1.4.18/
> -rw-rw-r-- 0/0  195907 2016-12-31 17:00 m4-1.4.18/ChangeLog-2014
> -rw-rw-r-- 0/0   63687 2016-12-31 16:34 m4-1.4.18/maint.mk
> -rw-rw-r-- 0/03912 2016-12-31 17:37 m4-1.4.18/ChangeLog
> -rw-rw-r-- 0/0   69156 2016-12-31 17:25 m4-1.4.18/aclocal.m4
> -rw-rw-r-- 0/02590 2016-12-29 15:32 m4-1.4.18/BACKLOG
> drwxrwxr-x 0/0   0 2016-12-31 17:37 m4-1.4.18/tests/
> -rw-rw-r-- 0/03126 2016-12-31 08:54 m4-1.4.18/tests/getcwd-lgpl.c
> -rw-rw-r-- 0/06134 2016-12-31 08:54 m4-1.4.18/tests/test-dup2.c
> -rw-rw-r-- 0/04998 2016-12-31 08:54 
> m4-1.4.18/tests/test-dup-safer.c
>
> Brendan.
>
> --
>
>
> On 26/08/2020 4:22 pm, Erik Botö wrote:
>
> Hi Brendan,
>
> Could you inspect the file in
> /home/brendan/SEPL/Projects/Erntec/PMU/yocto_trial/poky/build/downloads/m4-1.4.18.tar.gz
> to see if it is some kind of HTML file stating a download error?
>
> Check the file size, if it's small it's probably an error so open it
> using an editor to see if you get any hints. Many corporate networks
> will require the use of a proxy server, see e.g.
> https://wiki.yoctoproject.org/wiki/Working_Behind_a_Network_Proxy for
> hints on that.
>
> Cheers,
> Erik
>
> On Wed, Aug 26, 2020 at 7:36 AM Brendan Simon (SEPL)
>  wrote:
>
> Hi,
>
> I'm new to Yocto and am trying to follow the quick start guide to get up and 
> running with poky.  I'm using the latest Dunfel 3.1.2.
>
> I'm running Debian 10 Buster in a VirtualBox VM (guest), on a Windows 10 Pro 
> (host).
>
> I'm having trouble with the build fetching files and getting checksum 
> mismatch, however if I download the troublesome file with wget then the 
> checksum is correct.
>
> How do I fix this?
>
> Everything seems very complex with Yocto, but maybe that's because I'm new to 
> it.
>
>
> $ time bitbake core-image-sato
> Loading cache: 100% 
> |###|
>  Time: 0:00:01Loaded 1312 entries from dependency cache.
> NOTE: Resolving any missing task queue dependencies
>
> Build Configuration:
> BB_VERSION   = "1.46.0"
> BUILD_SYS= "x86_64-linux"
> NATIVELSBSTRING  = "universal"
> TARGET_SYS   = "x86_64-poky-linux"
> MACHINE  = "qemux86-64"
> DISTRO   = "poky"
> DISTRO_VERSION   = "3.1.2"
> TUNE_FEATURES= "m64 core2"
> TARGET_FPU   = ""
> meta
> meta-poky
> meta-yocto-bsp   = 
> "my-yocto-3.1.2:569b1f5d67c57de957e243997c53ec2f81dc8dfe"
>
> Initialising tasks: 100% 
> |##| 
> Time: 0:00:09Checking sstate mirror object availability: 100% 
> |##| Time: 0:36:41Sstate 
> summary: Wanted 2547 Found 0 Missed 2547 Current 228 (0% match, 8% complete)
> NOTE: Executing Tasks
> WARNING: m4-native-1.4.18-r0 do_fetch: Checksum mismatch for local file 
> /home/brendan/SEPL/Projects/Erntec/PMU/yocto_trial/poky/build/downloads/m4-1.4.18.tar.gz
> Cleaning and trying again.
> WARNING: m4-native-1.4.18-r0 do_fetch: Renaming 
> /home/brendan/SEPL/Projects/Erntec/PMU/yocto_trial/poky/build/downloads/m4-1.4.18.tar.gz
>  to 
> /home/brendan/SEPL/Projects/Erntec/PMU/yoc

Re: [yocto] #sdk -Standard SDK build with cmake and meta-clang gives error when I attempt topull in compiler-rt

[yocto] [meta-security][PATCH] sssd: Make manpages buildable

[yocto] #yocto #devtool

[yocto] [devtool] problem with PACKAGE_ARCH and TARGET_OS

[yocto] #yocto #devtool -Update packages

Re: [yocto] [OE-core] [devtool] problem with PACKAGE_ARCH and TARGET_OS

[yocto] Yocto Project Status WW34'20

Re: [yocto] [OE-core] [devtool] problem with PACKAGE_ARCH and TARGET_OS

Re: [yocto] #sdk -Standard SDK build with cmake and meta-clang gives error when I attempt topull in compiler-rt

[yocto] Mono build has unresolved QA errors

[yocto] [PATCH 1/2] poky-tiny: set preferred version to 5.8

[yocto] [PATCH 2/2] poky: add preferred version for linux-yocto-rt

[yocto] Help with yocto poky quick start

[yocto] [PATCH] meta-yocto-bsp: Bump to the v5.8 kernel

Re: [yocto] #yocto #devtool -Update packages

Re: [yocto] Help with yocto poky quick start

Re: [yocto] #sdk -Standard SDK build with cmake and meta-clang gives error when I attempt topull in compiler-rt

Re: [yocto] Help with yocto poky quick start

Re: [yocto] Help with yocto poky quick start

19 matches

Site Navigation

Mail list logo

Footer information