Re: [yocto] Error Building Valgrind_3.15 for yocto

2019-11-12 Thread Randy MacLeod

On 11/11/19 9:33 PM, Sheraz Ali wrote:


Hi Sir,

        I want to add valgrind to my yocto i am using valgrind version 
(3.15.0-r0 ) i have attached the valgrind source and error log for 
your reference.


This is the Build Configuration for which i am trying to build valgrind

Build Configuration:
BB_VERSION    = "1.22.0"
BUILD_SYS = "x86_64-linux"
NATIVELSBSTRING   = "Ubuntu-14.04"
TARGET_SYS    = "arm-poky-linux-gnueabi"
MACHINE   = "iwg22m"
DISTRO    = "poky"
DISTRO_VERSION    = "1.6.1"

That's a very old  release and is not supported officially by Yocto or 
even by the community:

   https://wiki.yoctoproject.org/wiki/Releases

Do you have a vendor who supports this collection of layers?
If not, there are many companies who are likley able to do so.


TUNE_FEATURES = "armv7a vfp neon callconvention-hard cortexa7"
TARGET_FPU    = "vfp-neon"
meta
meta-yocto
meta-yocto-bsp    = "tmp:c4f1f0f491f988901bfd6965f7d10f60cb94a76f"
meta-renesas
meta-rzg1 = "tmp:19bf1ed97d04009722bb88a780268822ee60ff83"
meta-oe
meta-multimedia   = "tmp:dca466c074c9a35bc0133e7e0d65cca0731e2acf"
meta-linaro-toolchain = "tmp:8a0601723c06fdb75e62aa0f0cf15fc9d7d90167"
meta-networking   = "tmp:dca466c074c9a35bc0133e7e0d65cca0731e2acf"

I am getting the following error can you suggest me what to do

/*arm-poky-linux-gnueabi-gcc: error: unrecognized argument in option 
'-march=armv7ve'*/
/*arm-poky-linux-gnueabi-gcc: note: valid arguments to '-march=' are: 
armv2 armv2a armv3 armv3m armv4 armv4t armv5 armv5e armv5t armv5te 
armv6 armv6-m armv6j armv6k armv6s-m armv6t2 armv6z armv6zk armv7 
armv7-a armv7-m armv7-r armv7e-m armv8-a armv8-a+crc iwmmxt iwmmxt2 
native*/




It looks like your BSP layer/vendor (meta-rzg1 perhaps), or perhaps the
toolchain supplier hasn't added support for this arch.

I can understand that you might not be able to upgrade to a
supported Yocto release but if not, it's unlikely that anyone can help.

If you can reproduce the problem on a supported branch with just poky or
with just fewer layers, then you could open a defect against valgrind or 
the toolchain:

   https://bugzilla.yoctoproject.org/

Sorry that I can't be of more assistance.,

../Randy



make[5]: *** [intdiv-intdiv.o] Error 1
make[5]: Leaving directory 
`/home/sarjoodeen/Project/2018/Nippon/YOCTO/iwG22M-release-bsp/build/tmp/work/cortexa7hf-vfp-neon-poky-linux-gnueabi/valgrind/3.15.0-r0/build/none/tests/arm'

make[4]: *** [check-am] Error 2
make[4]: Leaving directory 
`/home/sarjoodeen/Project/2018/Nippon/YOCTO/iwG22M-release-bsp/build/tmp/work/cortexa7hf-vfp-neon-poky-linux-gnueabi/valgrind/3.15.0-r0/build/none/tests/arm'

make[3]: *** [check-recursive] Error 1
make[3]: Leaving directory 
`/home/sarjoodeen/Project/2018/Nippon/YOCTO/iwG22M-release-bsp/build/tmp/work/cortexa7hf-vfp-neon-poky-linux-gnueabi/valgrind/3.15.0-r0/build/none/tests'

make[2]: *** [check-recursive] Error 1
make[2]: Leaving directory 
`/home/sarjoodeen/Project/2018/Nippon/YOCTO/iwG22M-release-bsp/build/tmp/work/cortexa7hf-vfp-neon-poky-linux-gnueabi/valgrind/3.15.0-r0/build/none'

make[1]: *** [check-recursive] Error 1
make[1]: Leaving directory 
`/home/sarjoodeen/Project/2018/Nippon/YOCTO/iwG22M-release-bsp/build/tmp/work/cortexa7hf-vfp-neon-poky-linux-gnueabi/valgrind/3.15.0-r0/build'

make: *** [check] Error 2
make: Leaving directory 
`/home/sarjoodeen/Project/2018/Nippon/YOCTO/iwG22M-release-bsp/build/tmp/work/cortexa7hf-vfp-neon-poky-linux-gnueabi/valgrind/3.15.0-r0/build'

ERROR: oe_runmake failed
WARNING: exit code 1 from a shell command.
ERROR: Function failed: do_compile_ptest_base (log file is located at 
/home/sarjoodeen/Project/2018/Nippon/YOCTO/iwG22M-release-bsp/build/tmp/work/cortexa7hf-vfp-neon-poky-linux-gnueabi/valgrind/3.15.0-r0/temp/log.do_compile_ptest_base.29480)


Thanks and Regards
Sheraz Ali Shah
--
Thanks and Regards
Sheraz Ali Shah



--
# Randy MacLeod
# Wind River Linux

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


Re: [yocto] Error Building Valgrind_3.15 for yocto

2019-11-12 Thread Khem Raj
On Tue, Nov 12, 2019 at 5:26 AM Sheraz Ali  wrote:
>
> Hi Sir,
>
> I want to add valgrind to my yocto i am using valgrind version 
> (3.15.0-r0 ) i have attached the valgrind source and error log for your 
> reference.
>
> This is the Build Configuration for which i am trying to build valgrind
>
> Build Configuration:
> BB_VERSION= "1.22.0"
> BUILD_SYS = "x86_64-linux"
> NATIVELSBSTRING   = "Ubuntu-14.04"
> TARGET_SYS= "arm-poky-linux-gnueabi"
> MACHINE   = "iwg22m"
> DISTRO= "poky"
> DISTRO_VERSION= "1.6.1"
> TUNE_FEATURES = "armv7a vfp neon callconvention-hard cortexa7"
> TARGET_FPU= "vfp-neon"
> meta
> meta-yocto
> meta-yocto-bsp= "tmp:c4f1f0f491f988901bfd6965f7d10f60cb94a76f"
> meta-renesas
> meta-rzg1 = "tmp:19bf1ed97d04009722bb88a780268822ee60ff83"
> meta-oe
> meta-multimedia   = "tmp:dca466c074c9a35bc0133e7e0d65cca0731e2acf"
> meta-linaro-toolchain = "tmp:8a0601723c06fdb75e62aa0f0cf15fc9d7d90167"
> meta-networking   = "tmp:dca466c074c9a35bc0133e7e0d65cca0731e2acf"
>
> I am getting the following error can you suggest me what to do
>
> arm-poky-linux-gnueabi-gcc: error: unrecognized argument in option 
> '-march=armv7ve'
> arm-poky-linux-gnueabi-gcc: note: valid arguments to '-march=' are: armv2 
> armv2a armv3 armv3m armv4 armv4t armv5 armv5e armv5t armv5te armv6 armv6-m 
> armv6j armv6k armv6s-m armv6t2 armv6z armv6zk armv7 armv7-a armv7-m armv7-r 
> armv7e-m armv8-a armv8-a+crc iwmmxt iwmmxt2 native
> make[5]: *** [intdiv-intdiv.o] Error 1
> make[5]: Leaving directory 
> `/home/sarjoodeen/Project/2018/Nippon/YOCTO/iwG22M-release-bsp/build/tmp/work/cortexa7hf-vfp-neon-poky-linux-gnueabi/valgrind/3.15.0-r0/build/none/tests/arm'
> make[4]: *** [check-am] Error 2
> make[4]: Leaving directory 
> `/home/sarjoodeen/Project/2018/Nippon/YOCTO/iwG22M-release-bsp/build/tmp/work/cortexa7hf-vfp-neon-poky-linux-gnueabi/valgrind/3.15.0-r0/build/none/tests/arm'
> make[3]: *** [check-recursive] Error 1
> make[3]: Leaving directory 
> `/home/sarjoodeen/Project/2018/Nippon/YOCTO/iwG22M-release-bsp/build/tmp/work/cortexa7hf-vfp-neon-poky-linux-gnueabi/valgrind/3.15.0-r0/build/none/tests'
> make[2]: *** [check-recursive] Error 1
> make[2]: Leaving directory 
> `/home/sarjoodeen/Project/2018/Nippon/YOCTO/iwG22M-release-bsp/build/tmp/work/cortexa7hf-vfp-neon-poky-linux-gnueabi/valgrind/3.15.0-r0/build/none'
> make[1]: *** [check-recursive] Error 1
> make[1]: Leaving directory 
> `/home/sarjoodeen/Project/2018/Nippon/YOCTO/iwG22M-release-bsp/build/tmp/work/cortexa7hf-vfp-neon-poky-linux-gnueabi/valgrind/3.15.0-r0/build'
> make: *** [check] Error 2
> make: Leaving directory 
> `/home/sarjoodeen/Project/2018/Nippon/YOCTO/iwG22M-release-bsp/build/tmp/work/cortexa7hf-vfp-neon-poky-linux-gnueabi/valgrind/3.15.0-r0/build'
> ERROR: oe_runmake failed
> WARNING: exit code 1 from a shell command.
> ERROR: Function failed: do_compile_ptest_base (log file is located at 
> /home/sarjoodeen/Project/2018/Nippon/YOCTO/iwG22M-release-bsp/build/tmp/work/cortexa7hf-vfp-neon-poky-linux-gnueabi/valgrind/3.15.0-r0/temp/log.do_compile_ptest_base.29480)
>

somewhere, its messing up compiler flags -march=armv7ve
-mcpu=cortex-a15 -mthumb is being added can you check if you have
bbapends or other places modifying it

> Thanks and Regards
> Sheraz Ali Shah
> --
> ___
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto