From: Martin Jansa <martin.jansa@gmail.com>
To: praveen vattipalli <praveen.vatt@gmail.com>
Cc: yocto@yoctoproject.org
Subject: Re: do_compile_ptest_base error (valgrind) in dizzy
Date: Wed, 8 Apr 2015 13:47:46 +0200 [thread overview]
Message-ID: <20150408114746.GE2337@jama> (raw)
In-Reply-To: <CA+pXca1siHggYUW5OMO0GM4KNSJ+qEV3-_A=VgkZNTk3H4Db-g@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 4385 bytes --]
On Wed, Apr 08, 2015 at 12:39:56PM +0530, praveen vattipalli wrote:
> hi
> I am using 64 bit ubuntu12.04 and compiling coertexa9 arch arm board. I
> could able to build core-image-minimal successfully. But when I am trying
> to build valgrind. I am getting do_compile_ptest_base error. If i remove
> ptest in valgrind_3.9.0.bb it is building without errors.
There are multiple issues in valgrind's ptest, in the end I've also
disabled ptest for valgrind:
Here is snippet of my distro config (with link to the same report 7 months ago):
# Work around FTBFS when building valgrind with ptest and thumb enabled
# valgrind/3.9.0-r8/valgrind-3.9.0/none/tests/arm/ldrt_arm.c
# {standard input}: Assembler messages:
# {standard input}:42: Error: cannot use post-indexing with this instruction -- `ldrt r6,[r5],#+132'
# {standard input}:42: Error: cannot use post-indexing with this instruction -- `ldrt r6,[r5],#132'
# ...
# ARM_INSTRUCTION_SET_pn-valgrind = "arm"
# and remove -O2 as work around for ICE:
# 3.9.0-r8/valgrind-3.9.0/none/tests/arm/vcvt_fixed_float_VFP.c:12:1: internal compiler error:
# Max. number of generated reload insns per insn is achieved (90)
# http://lists.openembedded.org/pipermail/openembedded-core/2014-September/097330.html
# both issues are still reproducible with 3.10.0 version imported from
# http://patchwork.openembedded.org/patch/83009/
# TARGET_CFLAGS_remove_pn-valgrind = "-O2"
PTEST_ENABLED_pn-valgrind = "0"
>
> I am using poky-dizzy.
>
> ERROR LOG:
>
> /home/praveenk/work/platform/build/tmp/work/cortexa9hf-vfp-neon-poky-linux-gnueabi/valgrind/3.9.0-r8/valgrind-3.9.0/none/tests/arm/vcvt_fixed_float_VFP.c:
> In function 's32_to_f32_imm1':
> |
> /home/praveenk/work/platform/build/tmp/work/cortexa9hf-vfp-neon-poky-linux-gnueabi/valgrind/3.9.0-r8/valgrind-3.9.0/none/tests/arm/vcvt_fixed_float_VFP.c:12:1:
> internal compiler error: Max. number of generated reload insns per insn is
> achieved (90)
> |
> | }
> | ^
> | Please submit a full bug report,
> | with preprocessed source if appropriate.
> | See <http://gcc.gnu.org/bugs.html> for instructions.
> | make[5]: *** [vcvt_fixed_float_VFP.o] Error 1
> | make[5]: Leaving directory
> `/home/praveenk/work/platform/build/tmp/work/cortexa9hf-vfp-neon-poky-linux-gnueabi/valgrind/3.9.0-r8/build/none/tests/arm'
> | make[4]: *** [check-am] Error 2
> | make[4]: Leaving directory
> `/home/praveenk/work/platform/build/tmp/work/cortexa9hf-vfp-neon-poky-linux-gnueabi/valgrind/3.9.0-r8/build/none/tests/arm'
> | make[3]: *** [check-recursive] Error 1
> | make[3]: Leaving directory
> `/home/praveenk/work/platform/build/tmp/work/cortexa9hf-vfp-neon-poky-linux-gnueabi/valgrind/3.9.0-r8/build/none/tests'
> | make[2]: *** [check-recursive] Error 1
> | make[2]: Leaving directory
> `/home/praveenk/work/platform/build/tmp/work/cortexa9hf-vfp-neon-poky-linux-gnueabi/valgrind/3.9.0-r8/build/none'
> | make[1]: *** [check-recursive] Error 1
> | make[1]: Leaving directory
> `/home/praveenk/work/platform/build/tmp/work/cortexa9hf-vfp-neon-poky-linux-gnueabi/valgrind/3.9.0-r8/build'
> | make: *** [check] Error 2
> | make: Leaving directory
> `/home/praveenk/work/platform/build/tmp/work/cortexa9hf-vfp-neon-poky-linux-gnueabi/valgrind/3.9.0-r8/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/praveenk/work/platform/build/tmp/work/cortexa9hf-vfp-neon-poky-linux-gnueabi/valgrind/3.9.0-r8/temp/log.do_compile_ptest_base.11152)
> ERROR: Task 9 (/home/praveenk/work/platform/meta/recipes-devtools/valgrind/
> valgrind_3.9.0.bb, do_compile_ptest_base) failed with exit code '1'
> NOTE: Tasks Summary: Attempted 776 tasks of which 769 didn't need to be
> rerun and 1 failed.
> No currently running tasks (776 of 784)
>
> Summary: 1 task failed:
> /home/praveenk/work/platform/meta/recipes-devtools/valgrind/
> valgrind_3.9.0.bb, do_compile_ptest_base
> Summary: There was 1 ERROR message shown, returning a non-zero exit code.
>
> how can i solve this.
>
> Thanks
> Praveen
> --
> _______________________________________________
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
--
Martin 'JaMa' Jansa jabber: Martin.Jansa@gmail.com
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 188 bytes --]
next prev parent reply other threads:[~2015-04-08 11:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-08 7:09 do_compile_ptest_base error (valgrind) in dizzy praveen vattipalli
2015-04-08 11:47 ` Martin Jansa [this message]
2015-04-09 7:18 ` Khem Raj
2015-04-10 9:30 ` praveen vattipalli
-- strict thread matches above, loose matches on Subject: below --
2015-04-07 6:43 praveen vattipalli
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20150408114746.GE2337@jama \
--to=martin.jansa@gmail.com \
--cc=praveen.vatt@gmail.com \
--cc=yocto@yoctoproject.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.