[yocto] -vfp arm tuning missing in builds and WORKDIR

[Dhanush K.S]

Currently the SDK that is being built, builds successfully but does not
contain the vfp arm tuning part included. Overriding the “TARGET_FPU”
variable in the local.conf and setting it to *“vfp-neon”*, does reflect in
the Build Configuration section, but that still has no difference in the
SDK being built. The TARGET_FPU by default is been set to *“hard”. *This
was possible in the earlier versions on Yocto though. Setting the CFLAGS in
the machine configuration to -mfpu=vfp-neon also has taken no effect.


Would it have something to do with GCC itself?



In other words, the SDK currently being built is “
poky-glibc-x86_64-my-meta-toolchain-cortexa8hf-neon-toolchain-2.5.sh” but
what is desired is “
poky-glibc-x86_64-my-meta-toolchain-cortexa8hf-vfp-neon-toolchain-2.5.sh”



Below is my Build Config,

Build Configuration:

BB_VERSION   = "1.37.0"

BUILD_SYS= "x86_64-linux"

NATIVELSBSTRING  = "universal-4.8"

TARGET_SYS   = "arm-poky-linux-gnueabi"

MACHINE  = "arm-cortex-a8"

DISTRO   = "poky"

DISTRO_VERSION   = "2.5"

TUNE_FEATURES= "arm armv7a vfp neon callconvention-hard cortexa8"

TARGET_FPU   = "hard"

meta-bsp-ti

meta

meta-poky

meta-yocto-bsp

meta-my-common

meta-oe  = ":"



Did something change in the Sumo version of Yocto and Is there any other
way of achieving this?

Any leads in achieving and helping better understand is appreciated.


Thanks!


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

[yocto] Fwd: bb-matrix.sh Script not working as expected

[Dhanush K.S]

Mit freundlichen Grüßen / Best Regards,
Dhanush Keshava Reddy Soppahalli
Mob: +4915216144064


-- Forwarded message -
From: Dhanush K.S 
Date: Tue, 7 May 2019 at 13:28
Subject: bb-matrix.sh Script not working as expected
To: Yocto discussion list 


Hello,

I'm trying to evaluate the performance of my builds and following the wiki
link https://wiki.yoctoproject.org/wiki/Build_Performance to determine the
accurate BB and PM values for my builds.

I have set "INHERIT += "buildstats"" in my local.conf and disabled
"BB_NUMBER_THREADS" & "PARALLEL_MAKE" during the execution of the build and
the script.

Executing the script bb-matrix.sh from the BUILDDIR with the command ".
../poky-sumo-19.0.0/scripts/contrib/bb-perf/bb-matrix.sh ." deletes the
TMPDIR entirely and then complains 'cp: cannot stat ‘tmp/buildstats’: No
such file or directory' for each iteration of BB and PM values.

I don't understand where I am going wrong and how do I go about generating
the dat file and in turn plotting the graph to determine the performance of
the build?

Thanks!

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

[yocto] bb-matrix.sh Script not working as expected

[Dhanush K.S]

Hello,

I'm trying to evaluate the performance of my builds and following the wiki
link https://wiki.yoctoproject.org/wiki/Build_Performance to determine the
accurate BB and PM values for my builds.

I have set "INHERIT += "buildstats"" in my local.conf and disabled
"BB_NUMBER_THREADS" & "PARALLEL_MAKE" during the execution of the build and
the script.

Executing the script bb-matrix.sh from the BUILDDIR with the command ".
../poky-sumo-19.0.0/scripts/contrib/bb-perf/bb-matrix.sh ." deletes the
TMPDIR entirely and then complains 'cp: cannot stat ‘tmp/buildstats’: No
such file or directory' for each iteration of BB and PM values.

I don't understand where I am going wrong and how do I go about generating
the dat file and in turn plotting the graph to determine the performance of
the build?

Thanks!

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

[yocto] bb-matrix.sh Script not working as expected

[Dhanush K.S]

Hello,

I'm trying to evaluate the performance of my builds and following the wiki
link https://wiki.yoctoproject.org/wiki/Build_Performance to determine the
accurate BB and PM values for my builds.

I have set "INHERIT += "buildstats"" in my local.conf and disabled
"BB_NUMBER_THREADS" & "PARALLEL_MAKE" during the execution of the build and
the script.

Executing the script bb-matrix.sh from the BUILDDIR with the command ".
../poky-sumo-19.0.0/scripts/contrib/bb-perf/bb-matrix.sh ." deletes the
TMPDIR entirely and then complains 'cp: cannot stat ‘tmp/buildstats’: No
such file or directory' for each iteration of BB and PM values.

I don't understand where I am going wrong and how do I go about generating
the dat file and in turn plotting the graph to determine the performance of
the build?

Thanks!

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

[yocto] Intentionally failing postinstall scriplets - Yocto Sumo

[Dhanush K.S]

Hello,

Building an image with Yocto Sumo throws out some warning messages during
do.rootfs. Although I'm partially clear that update-alternatives has
something to do with these warnings, but following the instructions in the
warning and placing the packages in pkg_postinst_ontarget_${PN} () does not
resolve the issue.

What am I missing here and what is the ideal solution to avoid these
warnings?

Here is my *BUILD INFORMATION*

Build Configuration:
BB_VERSION   = "1.37.0"
BUILD_SYS= "x86_64-linux"
NATIVELSBSTRING  = "universal-4.8"
TARGET_SYS   = "arm-poky-linux-gnueabi"
MACHINE  = "arm-cortex-a8"
DISTRO   = "poky"
DISTRO_VERSION   = "2.5"
TUNE_FEATURES= "arm armv7a vfp neon callconvention-hard cortexa8"
TARGET_FPU   = "hard"
meta-custombsp-ti
meta
meta-poky
meta-yocto-bsp
meta-custom-common  = ":"
meta-oe  = "master:45ee3c0e98bd3ed81419aaeae1e7324e486161a2"


WARNING: custom-image-1.0-r0 do_rootfs: Intentionally failing
postinstall scriptlets of ['vsftpd', 'dropbear', 'chrony'] to defer
them to first boot is deprecated. Please place them into
pkg_postinst_ontarget_${PN} ().

If deferring to first boot wasn't the intent, then scriptlet failure
may mean an issue in the recipe, or a regression elsewhere.

Details of the failure are in
/home/build_arm-cortex-a8/tmp/work/arm_cortex_a8-poky-linux-gnueabi/custom-image/1.0-r0/temp/log.do_rootfs.

WARNING: custom-image-1.0-r0 do_rootfs: [log_check] abkdkj-image:
found 4 warning messages in the logfile:

[log_check] warning: %post(vsftpd-3.0.3-r0.cortexa8hf_neon) scriptlet
failed, exit status 1

[log_check] warning: %post(dropbear-2017.75-r0.cortexa8hf_neon)
scriptlet failed, exit status 1

[log_check] warning: %post(chrony-3.1-r0.cortexa8hf_neon) scriptlet
failed, exit status 1

[log_check] WARNING: Intentionally failing postinstall scriptlets of
['vsftpd', 'dropbear', 'chrony'] to defer them to first boot is
deprecated. Please place them into pkg_postinst_ontarget_${PN} ().



Thanks,

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

[yocto] DEVTOOL doesn't upgrade glibc as expected

[Dhanush K.S]

Hi,

I'm currently using Yocto Sumo 2.5 release with the glibc version 2.27 and
would like to upgrade it to v2.28.
Using the devtool upgrade glibc -V 2.28
-S 044c96f0d5595aeb0bb4e79355081c5a7f4faca5 doesn't work as expected.
In turn it creates the workspace/recipes/glibc_2.28.bb recipe with the
contents and SRC_URI of v2.27.

devtool upgrade glibc -S 044c96f0d5595aeb0bb4e79355081c5a7f4faca5
NOTE: Starting bitbake server...
NOTE: Creating workspace layer in
/source/yocto/build_arm-cortex-a8/workspace

NOTE: Extracting current version source...
NOTE: Resolving any missing task queue dependencies

Build Configuration:
BB_VERSION   = "1.37.0"
BUILD_SYS= "x86_64-linux"
NATIVELSBSTRING  = "universal-4.8"
TARGET_SYS   = "arm-poky-linux-gnueabi"
MACHINE  = "arm-cortex-a8"
DISTRO   = "poky"
DISTRO_VERSION   = "2.5"
TUNE_FEATURES= "arm armv7a vfp neon callconvention-hard cortexa8"
TARGET_FPU   = "hard"
meta
meta-poky
meta-yocto-bsp
meta-oe  = "master:45ee3c0e98bd3ed81419aaeae1e7324e486161a2"
workspace= ":"

NOTE: Executing RunQueue Tasks
NOTE: Tasks Summary: Attempted 3 tasks of which 0 didn't need to be rerun
and all succeeded.
NOTE: Writing buildhistory
NOTE: Adding local source files to srctree...
NOTE: Extracting upgraded version source...
WARNING: Command 'git rebase 044c96f0d5595aeb0bb4e79355081c5a7f4faca5'
failed:
First, rewinding head to replay your work on top of it...
Applying: sparc: Check PIC instead of SHARED in start.S [BZ #22638]
error: Failed to merge in the changes.
Using index info to reconstruct a base tree...
M ChangeLog
M sysdeps/sparc/sparc32/start.S
M sysdeps/sparc/sparc64/start.S
Falling back to patching base and 3-way merge...
Auto-merging ChangeLog
CONFLICT (content): Merge conflict in ChangeLog
Patch failed at 0001 sparc: Check PIC instead of SHARED in start.S [BZ
#22638]
The copy of the patch that failed is found in: .git/rebase-apply/patch

Resolve all conflicts manually, mark them as resolved with
"git add/rm ", then run "git rebase --continue".
You can instead skip this commit: run "git rebase --skip".
To abort and get back to the state before "git rebase", run "git rebase
--abort".

You will need to resolve conflicts in order to complete the upgrade.
Traceback (most recent call last):
  File "/source/yocto/poky-sumo-19.0.0/scripts/devtool", line 344, in

ret = main()
  File "/source/yocto/poky-sumo-19.0.0/scripts/devtool", line 331, in main
ret = args.func(args, config, basepath, workspace)
  File "/source/yocto/poky-sumo-19.0.0/scripts/lib/devtool/upgrade.py",
line 559, in upgrade
rf, copied = _create_new_recipe(args.version, md5, sha256, args.srcrev,
srcbranch, srcsubdir1, srcsubdir2, config.workspace_path, tinfoil, rd,
license_diff, new_licenses)
  File "/source/yocto/poky-sumo-19.0.0/scripts/lib/devtool/upgrade.py",
line 344, in _create_new_recipe
scheme, network, path, user, passwd, params = bb.fetch2.decodeurl(entry)
  File "/source/yocto/poky-sumo-19.0.0/bitbake/lib/bb/fetch2/__init__.py",
line 368, in decodeurl
raise MalformedUrl(url)
bb.fetch2.MalformedUrl: The URL:
'${GLIBC_GIT_URI};branch=${SRCBRANCH};name=glibc' is invalid and cannot be
interpreted.

Need help with this one.

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

[yocto] Expansion Error during parsing of glibc_2.28 recipe

[Dhanush K.S]

Hello,

I'm trying to upgrade the glibc recipe from version 2.27 to 2.28 in Yocto
Sumo 2.5. Building the recipe for both qemux86 and for arm-cortex-a8
machines throws an Expansion error as below.

WARNING: /source/meta-openembedded/meta-oe/recipes-extended/liblockfile/
liblockfile_1.14.bb: Unable to get checksum for liblockfile SRC_URI entry
0001-Makefile.in-install-nfslock.so-and-nfslock.so.0.patch: file could not
be found   | ETA:  0:00:58
WARNING: /source/poky-sumo-19.0.0/meta/recipes-core/glibc/glibc_2.28.bb:
Exception during build_dependencies for
do_fix_readlib_c##
   | ETA:  0:00:04
WARNING: /source/poky-sumo-19.0.0/meta/recipes-core/glibc/glibc_2.28.bb:
Error during finalise of /source/poky-sumo-19.0.0/meta/recipes-core/glibc/
glibc_2.28.bb
ERROR: ExpansionError during parsing
/source/poky-sumo-19.0.0/meta/recipes-core/glibc/glibc_2.28.bb
Traceback (most recent call last):
  File "/source/poky-sumo-19.0.0/meta/classes/utils.bbclass", line 331, in
all_multilib_tune_values(d=, var='GLIBC_GETLOADER', unique=True, need_split=True,
delim=' '):
 values = []
>value = d.getVar(var) or ""
 if value != "":
  File "/source/poky-sumo-19.0.0/bitbake/lib/bb/data_smart.py", line 608,
in DataSmart.getVar(var='GLIBC_GETLOADER', expand=True,
noweakdefault=False, parsing=False):
 def getVar(self, var, expand=True, noweakdefault=False,
parsing=False):
>return self.getVarFlag(var, "_content", expand, noweakdefault,
parsing)

  File "/source/poky-sumo-19.0.0/bitbake/lib/bb/data_smart.py", line 794,
in DataSmart.getVarFlag(var='GLIBC_GETLOADER', flag='_content',
expand=True, noweakdefault=False, parsing=False):
 cachename = var + "[" + flag + "]"
>value = self.expand(value, cachename)

  File "/source/poky-sumo-19.0.0/bitbake/lib/bb/data_smart.py", line 436,
in DataSmart.expand(s='${@get_linuxloader(d)}', varname='GLIBC_GETLOADER'):
 def expand(self, s, varname = None):
>return self.expandWithRefs(s, varname).value

  File "/source/poky-sumo-19.0.0/bitbake/lib/bb/data_smart.py", line 426,
in DataSmart.expandWithRefs(s='${@get_linuxloader(d)}',
varname='GLIBC_GETLOADER'):
 except Exception as exc:
>raise ExpansionError(varname, s, exc) from exc

bb.data_smart.ExpansionError: Failure expanding variable GLIBC_GETLOADER,
expression was ${@get_linuxloader(d)} which triggered exception NameError:
name 'get_linuxloader' is not defined

WARNING: /source/poky-sumo-19.0.0/meta/recipes-core/glibc/
glibc-initial_2.28.bb: Exception during build_dependencies for
do_fix_readlib_c
WARNING: /source/poky-sumo-19.0.0/meta/recipes-core/glibc/
glibc-initial_2.28.bb: Error during finalise of
/source/poky-sumo-19.0.0/meta/recipes-core/glibc/glibc-initial_2.28.bb

Using devtool to upgrade the recipe doesn't work as well. Just changes the
recipe name but the SRC_URI remains the same as that of v2.27.

What am I missing here?

Here is my build config.

*Build Configuration:
*>* BB_VERSION   = "1.37.0"
*>* BUILD_SYS= "x86_64-linux"
*>* NATIVELSBSTRING  = "universal-4.8"
*>* TARGET_SYS   = "arm-poky-linux-gnueabi"
*>* MACHINE  = "arm-cortex-a8"
*>* DISTRO   = "poky"
*>* DISTRO_VERSION   = "2.5"
*>* TUNE_FEATURES= "arm armv7a vfp neon callconvention-hard cortexa8"
*>* TARGET_FPU   = "hard"*>* meta-poky
*>* meta-yocto-bsp*>* meta-oe  =
"master:45ee3c0e98bd3ed81419aaeae1e7324e486161a2*

*Thanks!*

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

[yocto] ARM Cross Compiler SDK Toolchain

[Dhanush K.S]

Hi Yocto,

I am running Yocto 2.5 (Poky Sumo) on the host system CentOS 7.1 to build
images for the target system ARM cortexa8 with a Target_FPU configured to
hard.

I would like to use a Cross Compiler SDK Toolchain in order to build the
images, as the current toolchain fails with a few recipes during
compilation due to missing include files.

I tried building the toolchain using "bitbake meta-toolchain", but
unfortunately that failed as well at do_generate_content_debug. But also,
as far as I understand this command builds the SDK with compilers for the
host system and not for the target system.

I would like to use a pre-built SDK, if one is available for ARM cortex A8
architecture. I have looked all around and haven't found one.

Could some Yocto Experts point me in the right direction? How can go about
finding a Cross Compiler Toolchain in order to overcome the compilation
errors.

Thanks in advance for your help.
Regards,

Mit freundlichen Grüßen / Best Regards,
Dhanush
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] Busybox_1.23.2 fails at do_compile on Poky-Sumo

[Dhanush K.S]

Hello Yocto,

I'm currently building an image with the busybox_1.23.2.bb recipe included,
using Yocto Sumo 2.5 with the Bitbake version 1.37.0. It is running on a
CentOS host building images for the target ARM cortexa8. This busybox
recipe is placed in another custom layer. Though this recipe compiles
without errors in Poky-Fido, in Poky-Sumo I get compilation errors due to
missing header files. Please take a look at the link below for the
log.do_compile output.

https://pastebin.com/yYXJnC2e

Both limits.h and byteswap.h don't exist in Poky-Fido as well, but compiles
without problems, unlike on Sumo. Does this have to do with the wrong
Toolchains used or due to glibc (FYI: glibc_2.27 is been used)? If it has
to do with the Toolchains, which one should I be using and how do I go
about it? Could someone please point me in the right direction?

Here is the Build Config:

Build Configuration:
BB_VERSION   = "1.37.0"
BUILD_SYS= "x86_64-linux"
NATIVELSBSTRING  = "universal-4.8"
TARGET_SYS   = "arm-poky-linux-gnueabi"
MACHINE  = "arm-cortex-a8"
DISTRO   = "poky"
DISTRO_VERSION   = "2.5"
TUNE_FEATURES= "arm armv7a vfp neon callconvention-hard cortexa8"
TARGET_FPU   = "hard"
meta-networking
meta-python  = "master:45ee3c0e98bd3ed81419aaeae1e7324e486161a2"
meta-userbsp-ti
meta
meta-poky
meta-yocto-bsp
meta-user-common  = ":"
meta-oe  = "master:45ee3c0e98bd3ed81419aaeae1e7324e486161a2"
workspace= ":"

Thanks in advance!
Regards,
Mit freundlichen Grüßen / Best Regards,
Dhanush
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] Busybox_1.23.2 fails at do_compile on Poky-Sumo

[Dhanush K.S]

Hello Yocto,

I'm currently building an image with the busybox_1.23.2.bb recipe included,
using Yocto Sumo 2.5 with the Bitbake version 1.37.0. It is running on a
CentOS host building images for the target ARM cortexa8. This busybox
recipe is placed in another custom layer. Though this recipe compiles
without errors in Poky-Fido, in Poky-Sumo I get compilation errors due to
missing header files. I have pasted a part of the log.do.compile file with
the error.

*# merged configuration written to .config (needs make)*
*#*
*NOTE: make -j 2 LD=arm-poky-linux-gnueabi-gcc  -march=armv7-a -mfpu=neon
-mfloat-abi=hard -mcpu=cortex-a8
--sysroot=/opt/ac500/yocto/branches/DEVEL_nextYocto/yocto/build_arm-cortex-a8/tmp/work/cortexa8hf-neon-poky-linux-gnueabi/busybox/1.23.2-r0/recipe-sysroot
V=1 ARCH=arm CROSS_COMPILE=arm-poky-linux-gnueabi- SKIP_STRIP=y
busybox_unstripped*
*rm -f .kernelrelease*
*echo 1.23.2 > .kernelrelease*
*/opt/ac500/yocto/branches/DEVEL_nextYocto/yocto/build_arm-cortex-a8/tmp/work/cortexa8hf-neon-poky-linux-gnueabi/busybox/1.23.2-r0/busybox-1.23.2/scripts/gen_build_files.sh
/opt/ac500/yocto/branches/DEVEL_nextYocto/yocto/build_arm-cortex-a8/tmp/work/cortexa8hf-neon-poky-linux-gnueabi/busybox/1.23.2-r0/busybox-1.23.2
/opt/ac500/yocto/branches/DEVEL_nextYocto/yocto/build_arm-cortex-a8/tmp/work/cortexa8hf-neon-poky-linux-gnueabi/busybox/1.23.2-r0/busybox-1.23.2*
*make -f
/opt/ac500/yocto/branches/DEVEL_nextYocto/yocto/build_arm-cortex-a8/tmp/work/cortexa8hf-neon-poky-linux-gnueabi/busybox/1.23.2-r0/busybox-1.23.2/Makefile
silentoldconfig*
*make -f scripts/Makefile.build obj=scripts/basic*
*/opt/ac500/yocto/branches/DEVEL_nextYocto/yocto/build_arm-cortex-a8/tmp/work/cortexa8hf-neon-poky-linux-gnueabi/busybox/1.23.2-r0/busybox-1.23.2/scripts/gen_build_files.sh
/opt/ac500/yocto/branches/DEVEL_nextYocto/yocto/build_arm-cortex-a8/tmp/work/cortexa8hf-neon-poky-linux-gnueabi/busybox/1.23.2-r0/busybox-1.23.2
/opt/ac500/yocto/branches/DEVEL_nextYocto/yocto/build_arm-cortex-a8/tmp/work/cortexa8hf-neon-poky-linux-gnueabi/busybox/1.23.2-r0/busybox-1.23.2*
*mkdir -p include*
*make -f scripts/Makefile.build obj=scripts/kconfig silentoldconfig*
*scripts/kconfig/conf -s Config.in*
*#*
*# using defaults found in .config*
*#*
*make -C
/opt/ac500/yocto/branches/DEVEL_nextYocto/yocto/build_arm-cortex-a8/tmp/work/cortexa8hf-neon-poky-linux-gnueabi/busybox/1.23.2-r0/busybox-1.23.2
KBUILD_SRC= .kernelrelease*
*rm -f .kernelrelease*
*echo 1.23.2 > .kernelrelease*
*make -f scripts/Makefile.build obj=scripts/basic*
*make -f scripts/Makefile.build obj=applets*
*  scripts/basic/split-include include/autoconf.h include/config*
*  gcc -Wp,-MD,applets/.usage.d  -Wall -Wstrict-prototypes -O2
-fomit-frame-pointer  -Iinclude -Iinclude -o applets/usage
applets/usage.c  *
*  gcc -Wp,-MD,applets/.applet_tables.d  -Wall -Wstrict-prototypes -O2
-fomit-frame-pointer   -o applets/applet_tables
applets/applet_tables.c  *
*
/opt/ac500/yocto/branches/DEVEL_nextYocto/yocto/build_arm-cortex-a8/tmp/work/cortexa8hf-neon-poky-linux-gnueabi/busybox/1.23.2-r0/busybox-1.23.2/scripts/mkconfigs
include/bbconfigopts.h include/bbconfigopts_bz2.h*
*make -f scripts/Makefile.build obj=scripts*
*  applets/usage_compressed include/usage_compressed.h applets*
*  applets/applet_tables include/applet_tables.h include/NUM_APPLETS.h*
*  gcc -Wp,-MD,applets/.usage_pod.d  -Wall -Wstrict-prototypes -O2
-fomit-frame-pointer  -Iinclude -Iinclude -o applets/usage_pod
applets/usage_pod.c  *
*  arm-poky-linux-gnueabi-gcc -Wp,-MD,applets/.applets.o.d   -std=gnu99
-Iinclude -Ilibbb  -include include/autoconf.h -D_GNU_SOURCE -DNDEBUG
-D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64
-D"BB_VER=KBUILD_STR(1.23.2)" -DBB_BT=AUTOCONF_TIMESTAMP  -Wall -Wshadow
-Wwrite-strings -Wundef -Wstrict-prototypes -Wunused -Wunused-parameter
-Wunused-function -Wunused-value -Wmissing-prototypes
-Wmissing-declarations -Wno-format-security -Wdeclaration-after-statement
-Wold-style-definition -fno-builtin-strlen -finline-limit=0
-fomit-frame-pointer -ffunction-sections -fdata-sections
-fno-guess-branch-probability -funsigned-char -static-libgcc
-falign-functions=1 -falign-jumps=1 -falign-labels=1 -falign-loops=1
-fno-unwind-tables -fno-asynchronous-unwind-tables -Os -O2 -pipe -g
-feliminate-unused-debug-types
-fdebug-prefix-map=/opt/ac500/yocto/branches/DEVEL_nextYocto/yocto/build_arm-cortex-a8/tmp/work/cortexa8hf-neon-poky-linux-gnueabi/busybox/1.23.2-r0=/usr/src/debug/busybox/1.23.2-r0
-fdebug-prefix-map=/opt/ac500/yocto/branches/DEVEL_nextYocto/yocto/build_arm-cortex-a8/tmp/work/cortexa8hf-neon-poky-linux-gnueabi/busybox/1.23.2-r0/recipe-sysroot=
-fdebug-prefix-map=/opt/ac500/yocto/branches/DEVEL_nextYocto/yocto/build_arm-cortex-a8/tmp/work/cortexa8hf-neon-poky-linux-gnueabi/busybox/1.23.2-r0/recipe-sysroot-native=
-mtune=cortex-a8  -O2 -pipe -g -feliminate-unused-debug-types

Re: [yocto] Busybox_1.23.2 fails at do_compile on Poky-Sumo

[Dhanush K.S]

Thanks for the the tip Raj. Here is the Build Config.

Build Configuration:
BB_VERSION   = "1.37.0"
BUILD_SYS= "x86_64-linux"
NATIVELSBSTRING  = "universal-4.8"
TARGET_SYS   = "arm-poky-linux-gnueabi"
MACHINE  = "arm-cortex-a8"
DISTRO   = "poky"
DISTRO_VERSION   = "2.5"
TUNE_FEATURES= "arm armv7a vfp neon callconvention-hard cortexa8"
TARGET_FPU   = "hard"
meta-networking
meta-python  = "master:45ee3c0e98bd3ed81419aaeae1e7324e486161a2"
meta-userbsp-ti
meta
meta-poky
meta-yocto-bsp
meta-user-common  = ":"
meta-oe  = "master:45ee3c0e98bd3ed81419aaeae1e7324e486161a2"
workspace= ":"

Thanks!

Mit freundlichen Grüßen / Best Regards,
Dhanush


On Thu, 18 Oct 2018 at 17:49, Khem Raj  wrote:

> Always send the Build Configuration that bitbake prints on top of
> build. So someone can get some additional information about your build
> to help you better.
> On Thu, Oct 18, 2018 at 1:03 AM Dhanush K.S  wrote:
> >
> > Hello Yocto,
> >
> > I'm currently building an image with the busybox_1.23.2.bb recipe
> included, using Yocto Sumo 2.5 with the Bitbake version 1.37.0. It is
> running on a CentOS host building images for the target ARM cortexa8. This
> busybox recipe is placed in another custom layer. Though this recipe
> compiles without errors in Poky-Fido, in Poky-Sumo I get compilation errors
> due to missing header files. I have pasted a part of the log.do.compile
> file with the error.
> >
> > # merged configuration written to .config (needs make)
> > #
> > NOTE: make -j 2 LD=arm-poky-linux-gnueabi-gcc  -march=armv7-a -mfpu=neon
> -mfloat-abi=hard -mcpu=cortex-a8
> --sysroot=/opt/ac500/yocto/branches/DEVEL_nextYocto/yocto/build_arm-cortex-a8/tmp/work/cortexa8hf-neon-poky-linux-gnueabi/busybox/1.23.2-r0/recipe-sysroot
> V=1 ARCH=arm CROSS_COMPILE=arm-poky-linux-gnueabi- SKIP_STRIP=y
> busybox_unstripped
> > rm -f .kernelrelease
> > echo 1.23.2 > .kernelrelease
> >
> /opt/ac500/yocto/branches/DEVEL_nextYocto/yocto/build_arm-cortex-a8/tmp/work/cortexa8hf-neon-poky-linux-gnueabi/busybox/1.23.2-r0/busybox-1.23.2/scripts/gen_build_files.sh
> /opt/ac500/yocto/branches/DEVEL_nextYocto/yocto/build_arm-cortex-a8/tmp/work/cortexa8hf-neon-poky-linux-gnueabi/busybox/1.23.2-r0/busybox-1.23.2
> /opt/ac500/yocto/branches/DEVEL_nextYocto/yocto/build_arm-cortex-a8/tmp/work/cortexa8hf-neon-poky-linux-gnueabi/busybox/1.23.2-r0/busybox-1.23.2
> > make -f
> /opt/ac500/yocto/branches/DEVEL_nextYocto/yocto/build_arm-cortex-a8/tmp/work/cortexa8hf-neon-poky-linux-gnueabi/busybox/1.23.2-r0/busybox-1.23.2/Makefile
> silentoldconfig
> > make -f scripts/Makefile.build obj=scripts/basic
> >
> /opt/ac500/yocto/branches/DEVEL_nextYocto/yocto/build_arm-cortex-a8/tmp/work/cortexa8hf-neon-poky-linux-gnueabi/busybox/1.23.2-r0/busybox-1.23.2/scripts/gen_build_files.sh
> /opt/ac500/yocto/branches/DEVEL_nextYocto/yocto/build_arm-cortex-a8/tmp/work/cortexa8hf-neon-poky-linux-gnueabi/busybox/1.23.2-r0/busybox-1.23.2
> /opt/ac500/yocto/branches/DEVEL_nextYocto/yocto/build_arm-cortex-a8/tmp/work/cortexa8hf-neon-poky-linux-gnueabi/busybox/1.23.2-r0/busybox-1.23.2
> > mkdir -p include
> > make -f scripts/Makefile.build obj=scripts/kconfig silentoldconfig
> > scripts/kconfig/conf -s Config.in
> > #
> > # using defaults found in .config
> > #
> > make -C
> /opt/ac500/yocto/branches/DEVEL_nextYocto/yocto/build_arm-cortex-a8/tmp/work/cortexa8hf-neon-poky-linux-gnueabi/busybox/1.23.2-r0/busybox-1.23.2
> KBUILD_SRC= .kernelrelease
> > rm -f .kernelrelease
> > echo 1.23.2 > .kernelrelease
> > make -f scripts/Makefile.build obj=scripts/basic
> > make -f scripts/Makefile.build obj=applets
> >   scripts/basic/split-include include/autoconf.h include/config
> >   gcc -Wp,-MD,applets/.usage.d  -Wall -Wstrict-prototypes -O2
> -fomit-frame-pointer  -Iinclude -Iinclude -o applets/usage
> applets/usage.c
> >   gcc -Wp,-MD,applets/.applet_tables.d  -Wall -Wstrict-prototypes -O2
> -fomit-frame-pointer   -o applets/applet_tables applets/applet_tables.c
> >
>  
> /opt/ac500/yocto/branches/DEVEL_nextYocto/yocto/build_arm-cortex-a8/tmp/work/cortexa8hf-neon-poky-linux-gnueabi/busybox/1.23.2-r0/busybox-1.23.2/scripts/mkconfigs
> include/bbconfigopts.h include/bbconfigopts_bz2.h
> > make -f scripts/Makefile.build obj=scripts
> >   applets/usage_compressed include/usage_compressed.h applets
> >   applets/applet_tables include/applet_tables.h include/NUM_APPLETS.h
> >   gcc -Wp,-MD,applets/.usage_pod.d  -Wall -Wstrict-prototypes -O2
> -fomi

[yocto] Busybox_1.23.2 fails at do_compile on Poky-Sumo

[Dhanush K.S]

Hello Yocto,

I'm currently building an image with the busybox_1.23.2.bb recipe included,
using Yocto Sumo 2.5 with the Bitbake version 1.37.0. It is running on a
CentOS host building images for the target ARM cortexa8. This busybox
recipe is placed in another custom layer. Though this recipe compiles
without errors in Poky-Fido, in Poky-Sumo I get compilation errors due to
missing header files. I have pasted a part of the log.do.compile file with
the error.

*# merged configuration written to .config (needs make)*
*#*
*NOTE: make -j 2 LD=arm-poky-linux-gnueabi-gcc  -march=armv7-a -mfpu=neon
-mfloat-abi=hard -mcpu=cortex-a8
--sysroot=/opt/ac500/yocto/branches/DEVEL_nextYocto/yocto/build_arm-cortex-a8/tmp/work/cortexa8hf-neon-poky-linux-gnueabi/busybox/1.23.2-r0/recipe-sysroot
V=1 ARCH=arm CROSS_COMPILE=arm-poky-linux-gnueabi- SKIP_STRIP=y
busybox_unstripped*
*rm -f .kernelrelease*
*echo 1.23.2 > .kernelrelease*
*/opt/ac500/yocto/branches/DEVEL_nextYocto/yocto/build_arm-cortex-a8/tmp/work/cortexa8hf-neon-poky-linux-gnueabi/busybox/1.23.2-r0/busybox-1.23.2/scripts/gen_build_files.sh
/opt/ac500/yocto/branches/DEVEL_nextYocto/yocto/build_arm-cortex-a8/tmp/work/cortexa8hf-neon-poky-linux-gnueabi/busybox/1.23.2-r0/busybox-1.23.2
/opt/ac500/yocto/branches/DEVEL_nextYocto/yocto/build_arm-cortex-a8/tmp/work/cortexa8hf-neon-poky-linux-gnueabi/busybox/1.23.2-r0/busybox-1.23.2*
*make -f
/opt/ac500/yocto/branches/DEVEL_nextYocto/yocto/build_arm-cortex-a8/tmp/work/cortexa8hf-neon-poky-linux-gnueabi/busybox/1.23.2-r0/busybox-1.23.2/Makefile
silentoldconfig*
*make -f scripts/Makefile.build obj=scripts/basic*
*/opt/ac500/yocto/branches/DEVEL_nextYocto/yocto/build_arm-cortex-a8/tmp/work/cortexa8hf-neon-poky-linux-gnueabi/busybox/1.23.2-r0/busybox-1.23.2/scripts/gen_build_files.sh
/opt/ac500/yocto/branches/DEVEL_nextYocto/yocto/build_arm-cortex-a8/tmp/work/cortexa8hf-neon-poky-linux-gnueabi/busybox/1.23.2-r0/busybox-1.23.2
/opt/ac500/yocto/branches/DEVEL_nextYocto/yocto/build_arm-cortex-a8/tmp/work/cortexa8hf-neon-poky-linux-gnueabi/busybox/1.23.2-r0/busybox-1.23.2*
*mkdir -p include*
*make -f scripts/Makefile.build obj=scripts/kconfig silentoldconfig*
*scripts/kconfig/conf -s Config.in*
*#*
*# using defaults found in .config*
*#*
*make -C
/opt/ac500/yocto/branches/DEVEL_nextYocto/yocto/build_arm-cortex-a8/tmp/work/cortexa8hf-neon-poky-linux-gnueabi/busybox/1.23.2-r0/busybox-1.23.2
KBUILD_SRC= .kernelrelease*
*rm -f .kernelrelease*
*echo 1.23.2 > .kernelrelease*
*make -f scripts/Makefile.build obj=scripts/basic*
*make -f scripts/Makefile.build obj=applets*
*  scripts/basic/split-include include/autoconf.h include/config*
*  gcc -Wp,-MD,applets/.usage.d  -Wall -Wstrict-prototypes -O2
-fomit-frame-pointer  -Iinclude -Iinclude -o applets/usage
applets/usage.c  *
*  gcc -Wp,-MD,applets/.applet_tables.d  -Wall -Wstrict-prototypes -O2
-fomit-frame-pointer   -o applets/applet_tables
applets/applet_tables.c  *
*
/opt/ac500/yocto/branches/DEVEL_nextYocto/yocto/build_arm-cortex-a8/tmp/work/cortexa8hf-neon-poky-linux-gnueabi/busybox/1.23.2-r0/busybox-1.23.2/scripts/mkconfigs
include/bbconfigopts.h include/bbconfigopts_bz2.h*
*make -f scripts/Makefile.build obj=scripts*
*  applets/usage_compressed include/usage_compressed.h applets*
*  applets/applet_tables include/applet_tables.h include/NUM_APPLETS.h*
*  gcc -Wp,-MD,applets/.usage_pod.d  -Wall -Wstrict-prototypes -O2
-fomit-frame-pointer  -Iinclude -Iinclude -o applets/usage_pod
applets/usage_pod.c  *
*  arm-poky-linux-gnueabi-gcc -Wp,-MD,applets/.applets.o.d   -std=gnu99
-Iinclude -Ilibbb  -include include/autoconf.h -D_GNU_SOURCE -DNDEBUG
-D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64
-D"BB_VER=KBUILD_STR(1.23.2)" -DBB_BT=AUTOCONF_TIMESTAMP  -Wall -Wshadow
-Wwrite-strings -Wundef -Wstrict-prototypes -Wunused -Wunused-parameter
-Wunused-function -Wunused-value -Wmissing-prototypes
-Wmissing-declarations -Wno-format-security -Wdeclaration-after-statement
-Wold-style-definition -fno-builtin-strlen -finline-limit=0
-fomit-frame-pointer -ffunction-sections -fdata-sections
-fno-guess-branch-probability -funsigned-char -static-libgcc
-falign-functions=1 -falign-jumps=1 -falign-labels=1 -falign-loops=1
-fno-unwind-tables -fno-asynchronous-unwind-tables -Os -O2 -pipe -g
-feliminate-unused-debug-types
-fdebug-prefix-map=/opt/ac500/yocto/branches/DEVEL_nextYocto/yocto/build_arm-cortex-a8/tmp/work/cortexa8hf-neon-poky-linux-gnueabi/busybox/1.23.2-r0=/usr/src/debug/busybox/1.23.2-r0
-fdebug-prefix-map=/opt/ac500/yocto/branches/DEVEL_nextYocto/yocto/build_arm-cortex-a8/tmp/work/cortexa8hf-neon-poky-linux-gnueabi/busybox/1.23.2-r0/recipe-sysroot=
-fdebug-prefix-map=/opt/ac500/yocto/branches/DEVEL_nextYocto/yocto/build_arm-cortex-a8/tmp/work/cortexa8hf-neon-poky-linux-gnueabi/busybox/1.23.2-r0/recipe-sysroot-native=
-mtune=cortex-a8  -O2 -pipe -g -feliminate-unused-debug-types

[yocto] Bitbake Build Configurations

[Dhanush K.S]

Hi Yocto,

I have my bitbake environment set up on the host system CentOS 7 and
building images for the target ARM cortex A8 with the following BUILD
CONFIGURATION,

Build Configuration:
BB_VERSION   = "1.37.0"
BUILD_SYS= "x86_64-linux"
NATIVELSBSTRING  = "universal-4.8"
TARGET_SYS   = "arm-poky-linux-gnueabi"
MACHINE  = "arm-cortex-a8"
DISTRO   = "poky"
DISTRO_VERSION   = "2.5"
TUNE_FEATURES= "arm armv7a vfp neon callconvention-hard cortexa8"
TARGET_FPU   = "hard"
meta-networking
meta-python  = "master:45ee3c0e98bd3ed81419aaeae1e7324e486161a2"
meta-userbsp-ti
meta
meta-poky
meta-yocto-bsp
meta-user-common  = ":"
meta-oe  = "master:45ee3c0e98bd3ed81419aaeae1e7324e486161a2"


   1. What I don't understand is how exactly are these Variables set?
   2. For the NATIVELSBSTRING which should actually be displaying the HOST
   OS according to the Yocto Manual, isn't doing that. What could be the
   reason for that? (Earlier, with Poky Fido, this wasn't the case. It
   displays "CentOS-Linux-7.1.1503".)
   3. From where does Bitbake pull this information?
   4. Also how is the TARGET_FPU variable set?

Could someone please shed some light on this.

Thanks!

Mit freundlichen Grüßen / Best Regards,
Dhanush Keshava Reddy Soppahalli
Mob: +4915216144064
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] Problem using SVN in SUMO

[Dhanush K.S]

I run into the following error with SVN when i bitbake a custom recipe /
building an image with the custom recipe.

ERROR: ExpansionError during parsing
/opt/xxx/yocto/branches/DEVEL_nextYocto/yocto/meta-xxx/meta-xxxbsp-ti/recipes-kernel/xxx-kmods/
xxx-kmods.bb
Traceback (most recent call last):
bb.data_smart.ExpansionError: Failure expanding variable SRCPV, expression
was ${@bb.fetch2.get_srcrev(d)} which triggered exception FetchError:
Fetcher failure: Fetch command export PSEUDO_DISABLED=1; export
DBUS_SESSION_BUS_ADDRESS="unix:abstract=/tmp/dbus-YvJ9dQ1Lq4,guid=c98f6cc12c31b7698bb5b2705b98dd53";
export SSH_AGENT_PID="2819"; export
SSH_AUTH_SOCK="/tmp/ssh-j5FBuyUi8utw/agent.2741"; export
GIT_SSL_CAINFO="/opt/xxx/yocto/branches/DEVEL_nextYocto/yocto/poky-tools-2.5/2.5/sysroots/x86_64-pokysdk-linux/etc/ssl/certs/ca-certificates.crt";
export GIT_PROXY_COMMAND="oe-git-proxy"; export ftp_proxy="
http://proxy.xxx.com:8080;; export https_proxy="https://proxy.xxx.com:8080;;
export http_proxy="http://proxy.xxx.com:8080;; export
PATH="/opt/xxx/yocto/branches/DEVEL_nextYocto/yocto/build_arm-cortex-a8/tmp/sysroots-uninative/x86_64-linux/usr/bin:/opt/xxx/yocto/branches/DEVEL_nextYocto/yocto/poky-sumo-19.0.0/scripts:/opt/xxx/yocto/branches/DEVEL_nextYocto/yocto/build_arm-cortex-a8/tmp/work/arm_cortex_a8-poky-linux-gnueabi/xxx-kmods/fetcheravoidrecurse-r0/recipe-sysroot-native/usr/bin/arm-poky-linux-gnueabi:/opt/xxx/yocto/branches/DEVEL_nextYocto/yocto/build_arm-cortex-a8/tmp/work/arm_cortex_a8-poky-linux-gnueabi/xxx-kmods/fetcheravoidrecurse-r0/recipe-sysroot/usr/bin/crossscripts:/opt/xxx/yocto/branches/DEVEL_nextYocto/yocto/build_arm-cortex-a8/tmp/work/arm_cortex_a8-poky-linux-gnueabi/xxx-kmods/fetcheravoidrecurse-r0/recipe-sysroot-native/usr/sbin:/opt/xxx/yocto/branches/DEVEL_nextYocto/yocto/build_arm-cortex-a8/tmp/work/arm_cortex_a8-poky-linux-gnueabi/xxx-kmods/fetcheravoidrecurse-r0/recipe-sysroot-native/usr/bin:/opt/xxx/yocto/branches/DEVEL_nextYocto/yocto/build_arm-cortex-a8/tmp/work/arm_cortex_a8-poky-linux-gnueabi/xxx-kmods/fetcheravoidrecurse-r0/recipe-sysroot-native/sbin:/opt/xxx/yocto/branches/DEVEL_nextYocto/yocto/build_arm-cortex-a8/tmp/work/arm_cortex_a8-poky-linux-gnueabi/xxx-kmods/fetcheravoidrecurse-r0/recipe-sysroot-native/bin:/opt/xxx/yocto/branches/DEVEL_nextYocto/yocto/poky-sumo-19.0.0/bitbake/bin:/opt/xxx/yocto/branches/DEVEL_nextYocto/yocto/build_arm-cortex-a8/tmp/hosttools";
export HOME="/home/xxx"; LANG=C LC_ALL=C /usr/bin/env svn --non-interactive
--trust-server-cert log --limit 1 --no-auth-cache --username
XD-XDj65-PMFW_UILDB --password *!
https://LINK_TO_OUR_SVN/REPO_Linux/trunk/modules/ failed with exit code
127, output:
/usr/bin/env: svn: No such file or directory

Also when the image recipe is bitbaked, the following error is thrown

Failed to spawn fakeroot worker to run
/opt/xxx/yocto/branches/DEVEL_nextYocto/yocto/meta-xxx/meta-xxx-common/recipes-xxx/images/xxx-image.bb:do_rootfs:
[Errno 2] No such file or directory:
'/opt/xxx/yocto/branches/DEVEL_nextYocto/yocto/build_arm-cortex-a8/tmp/sysroots-components/x86_64/pseudo-native/usr/bin/pseudo'

Mit freundlichen Grüßen / Best Regards,
Dhanush Keshava Reddy Soppahalli
Mob: +4915216144064
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] BITBAKE ADD-LAYER | HELP!!

[Dhanush K.S]

No. That doesn't help as well. Rather I get an error with
meta-openembedded/meta-oe.

Mit freundlichen Grüßen / Best Regards,
Dhanush Keshava Reddy Soppahalli
+4915216144064

On Thu, Aug 16, 2018, 21:42 Andre McCurdy  wrote:

> On Thu, Aug 16, 2018 at 12:52 AM, Dhanush K.S 
> wrote:
> > Hello MailingList,
> >
> > I just upgraded yocto to the latest release (Sumo 19.0 /Yocto 2.5.1).
> > Currently i am trying to add the meta-openembedded layer to my
> > conf/bblayers.conf using the command "bitbake-layers add-layer
> > DIRECTORY_PATH/LAYER".
> >
> > But I am getting parseError at times.
> >
> > Is it absolutely necessary to checkout the meta-openembedded layer to the
> > same Branch as that of the Yocto Version?
>
> Yes, it is. Do your errors go away if you do that?
>
> > or is it alright to stay in the
> > master Branch?
> > I can add the meta-oe sub-layer while on master but i get parseError
> when on
> > the Sumo branch.
> > I am not able to add the meta-python and meta-networking sub-layers of
> > meta-openembedded to the conf/bblayers.conf file without getting parse
> > errors. (meta-networking sub-layer depends on meta-python, so until I
> > resolve that I cannot add this)
> >
> >  [ac500v3@localhost build-2.5]$ bitbake-layers add-layer
> > /opt/ac500/yocto/trunk/yocto/next/meta-openembedded/meta-python/
> > NOTE: Starting bitbake server...
> > Loading cache: 100%
> >
> ||
> > Time: 0:00:00
> > Loaded 499 entries from dependency cache.
> > ERROR: ParseError at
> >
> /opt/ac500/yocto/trunk/yocto/next/meta-openembedded/meta-python/recipes-devtools/python/
> python-pbr_4.2.0.bb:3:
> > Could not include required file recipes-devtools/python/python-pbr.inc
> > | ETA:  --:--:--
> >
> > Summary: There was 1 ERROR message shown, returning a non-zero exit code.
> > ERROR: Parse failure with the specified layer added
> >
> > What and where am I going wrong?
> >
> >
> > Mit freundlichen Grüßen / Best Regards,
> > Dhanush Keshava Reddy Soppahalli
> > Mob: +4915216144064
> >
> > --
> > ___
> > 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] BITBAKE ADD-LAYER | HELP!!

[Dhanush K.S]

Hello MailingList,

I just upgraded yocto to the latest release (Sumo 19.0 /Yocto 2.5.1).
Currently i am trying to add the meta-openembedded layer to my
conf/bblayers.conf using the command "bitbake-layers add-layer
DIRECTORY_PATH/LAYER".

But I am getting parseError at times.


   - Is it absolutely necessary to checkout the meta-openembedded layer to
   the same Branch as that of the Yocto Version? or is it alright to stay in
   the master Branch?
   - I can add the meta-oe sub-layer while on master but i get parseError
   when on the Sumo branch.
   - I am not able to add the meta-python and meta-networking sub-layers of
   meta-openembedded to the conf/bblayers.conf file without getting parse
   errors. (meta-networking sub-layer depends on meta-python, so until I
   resolve that I cannot add this)


*[ac500v3@localhost build-2.5]$ bitbake-layers add-layer
/opt/ac500/yocto/trunk/yocto/next/meta-openembedded/meta-python/*
*NOTE: Starting bitbake server...*
*Loading cache: 100%
||
Time: 0:00:00*
*Loaded 499 entries from dependency cache.*
*ERROR: ParseError at
/opt/ac500/yocto/trunk/yocto/next/meta-openembedded/meta-python/recipes-devtools/python/python-pbr_4.2.0.bb:3
: Could not include required file
recipes-devtools/python/python-pbr.inc
| ETA:  --:--:--*

*Summary: There was 1 ERROR message shown, returning a non-zero exit code.*
*ERROR: Parse failure with the specified layer added*

What and where am I going wrong?


Mit freundlichen Grüßen / Best Regards,
Dhanush Keshava Reddy Soppahalli
Mob: +4915216144064
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] HELP!

[Dhanush K.S]

Hello,

I am currently trying to migrate from Yocto 1.8 Poky Fido 13.0.0 to Yocto
2.5.

After cloning the Poky repository, I was confused with which tag to
checkout with.

Could you please help me understand the difference between the tags
*"sumo-19.0.0"
*and *"yocto-2.5"*

As far as I understand, both mean the same since "2.5" is the
DISTRO_VERSION and "sumo" is the DISTRO_CODENAME.

But is still the same with the checkout tags as well?

Many thanks in advance!

Mit freundlichen Grüßen / Best Regards,
Dhanush Keshava Reddy Soppahalli
Mob: +4915216144064
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto