| Summary: | lttng-ust do_compile failed on autobuilder for beagleboard with 20110817 build | ||
|---|---|---|---|
| Product: | [Build System, Metadata & Runtime] OE-Core | Reporter: | Yi Zhao <yi.zhao> |
| Component: | devtools / tool chain | Assignee: | Nitin Kamble <nitin.a.kamble> |
| Status: | VERIFIED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | Medium | CC: | dvhart, jiajun.xu, liang.li2, liangliang.wang, meta.mr.watcher, meta.watcher, poky.bs.watcher, poky.watcher, sgw, wenhuax.fan, yi.zhao |
| Version: | unspecified | ||
| Target Milestone: | 1.1 | ||
| Hardware: | x86 | ||
| OS: | Multiple | ||
| Whiteboard: | There is a pending patch for the mips issue (18-Aug-2011) | ||
| OS type for building Yocto: | --- | Type of Regression: | --- |
| Verified: | Documentation change: | --- | |
|
Description
Yi Zhao
2011-08-17 23:56:02 UTC
The qemumips and routerstatinpro sato-sdk image also can not build due to missing dependency with lttng-ust. http://autobuilder.pokylinux.org:8010/builders/nightly-external/builds/71/steps/shell_27/logs/stdio ########### Parsing recipes...done. Parsing of 793 .bb files complete (0 cached, 793 parsed). 1029 targets, 44 skipped, 0 masked, 0 errors. NOTE: Resolving any missing task queue dependencies ERROR: Nothing PROVIDES 'lttng-ust' (but /srv/home/pokybuild/poky-slave/nightly-external/build/meta/recipes-devtools/gdb/gdb_7.3.bb DEPENDS on or otherwise requires it) ERROR: lttng-ust was skipped: incompatible with host mips-poky-linux NOTE: Runtime target 'gdb' is unbuildable, removing... Missing or unbuildable dependency chain was: ['gdb', 'lttng-ust'] NOTE: Runtime target 'task-core-tools-testapps' is unbuildable, removing... Missing or unbuildable dependency chain was: ['task-core-tools-testapps', 'gdb', 'lttng-ust'] NOTE: Runtime target 'task-core-tools-profile' is unbuildable, removing... Missing or unbuildable dependency chain was: ['task-core-tools-profile', 'gdb', 'lttng-ust'] NOTE: Runtime target 'task-core-tools-debug' is unbuildable, removing... Missing or unbuildable dependency chain was: ['task-core-tools-debug', 'gdb', 'lttng-ust'] NOTE: Runtime target 'gdbserver' is unbuildable, removing... Missing or unbuildable dependency chain was: ['gdbserver', 'lttng-ust'] ERROR: Nothing RPROVIDES 'gdb-dev' (but /srv/home/pokybuild/poky-slave/nightly-external/build/meta/recipes-devtools/gdb/gdb_7.3.bb RDEPENDS on or otherwise requires it) ERROR: No eligible RPROVIDERs exist for 'gdb-dev' NOTE: Runtime target 'gdb-dev' is unbuildable, removing... Missing or unbuildable dependency chain was: ['gdb-dev'] NOTE: Preparing runqueue NOTE: Executing SetScene Tasks NOTE: Running setscene task 348 of 1437 (/srv/home/pokybuild/poky-slave/nightly-external/build/meta/recipes-core/eglibc/eglibc-locale_2.13.bb:do_package_setscene) ######################## qemumips sato-sdk image has been built out in nightly build 20110821-1: http://autobuilder.pokylinux.org/nightly/20110821-1/machines/qemu/qemumips/ also routerstatinpro sato-sdk image has been build out in this nightly build. Tried to change the -march from armv7 -> armv5, but that caused this problem, I am thinking there is a mismatch of options.
| arm-poky-linux-gnueabi-libtool: compile: ccache arm-poky-linux-gnueabi-gcc -march=armv5 -fno-tree-vectorize -mthumb-interwork -mfloat-abi=softfp -mfpu=neon -mtune=cortex-a8 --sysroot=/vol/1/sgw/autobuilder/yab/yocto-slave/external/build/build/tmp/sysroots/beagleboard -DHAVE_CONFIG_H -I. -I.. -I../include/ust -I../include -I../libustcomm -DUST_COMPONENT=libust -fno-strict-aliasing -Wall -pipe -g -feliminate-unused-debug-types -MT libust_la-marker-control.lo -MD -MP -MF .deps/libust_la-marker-control.Tpo -c marker-control.c -o libust_la-marker-control.o >/dev/null 2>&1
| mv -f .deps/libust_la-tracercore.Tpo .deps/libust_la-tracercore.Plo
| {standard input}: Assembler messages:
| {standard input}:190: Error: selected processor does not support ARM mode `dmb'
| {standard input}:242: Error: selected processor does not support ARM mode `dmb'
| {standard input}:1531: Error: selected processor does not support ARM mode `dmb'
| make[2]: *** [libust_la-type-serializer.lo] Error 1
| make[2]: *** Waiting for unfinished jobs....
| {standard input}: Assembler messages:
| {standard input}:2466: Error: selected processor does not support ARM mode `dmb'
| make[2]: *** [libust_la-tracepoint.lo] Error 1
| mv -f .deps/libust_la-trace_event.Tpo .deps/libust_la-trace_event.Plo
| {standard input}: Assembler messages:
| {standard input}:91: Error: selected processor does not support ARM mode `dmb'
| {standard input}:143: Error: selected processor does not support ARM mode `dmb'
| {standard input}:5107: Error: selected processor does not support ARM mode `dmb'
| make[2]: *** [libust_la-serialize.lo] Error 1
| {standard input}: Assembler messages:
| {standard input}:203: Error: selected processor does not support ARM mode `dmb'
| make[2]: *** [libust_la-tracer.lo] Error 1
| mv -f .deps/libust_la-channels.Tpo .deps/libust_la-channels.Plo
| mv -f .deps/libust_la-marker-control.Tpo .deps/libust_la-marker-control.Plo
| {standard input}: Assembler messages:
| {standard input}:2822: Error: selected processor does not support ARM mode `dmb'
| {standard input}:4030: Error: selected processor does not support ARM mode `dmb'
| {standard input}:4515: Error: selected processor does not support ARM mode `dmb'
| {standard input}:5032: Error: selected processor does not support ARM mode `dmb'
| make[2]: *** [libust_la-buffers.lo] Error 1
| {standard input}: Assembler messages:
| {standard input}:202: Error: selected processor does not support ARM mode `dmb'
| {standard input}:254: Error: selected processor does not support ARM mode `dmb'
| {standard input}:686: Error: selected processor does not support ARM mode `dmb'
| {standard input}:695: Error: selected processor does not support ARM mode `dmb'
| {standard input}:721: Error: selected processor does not support ARM mode `dmb'
| {standard input}:823: Error: selected processor does not support ARM mode `dmb'
| {standard input}:832: Error: selected processor does not support ARM mode `dmb'
| {standard input}:855: Error: selected processor does not support ARM mode `dmb'
| {standard input}:6193: Error: selected processor does not support ARM mode `dmb'
| {standard input}:6207: Error: selected processor does not support ARM mode `dmb'
| {standard input}:6220: Error: selected processor does not support ARM mode `dmb'
| {standard input}:6711: Error: selected processor does not support ARM mode `dmb'
| make[2]: *** [libust_la-marker.lo] Error 1
| arm-poky-linux-gnueabi-libtool: compile: ccache arm-poky-linux-gnueabi-gcc -march=armv5 -fno-tree-vectorize -mthumb-interwork -mfloat-abi=softfp -mfpu=neon -mtune=cortex-a8 --sysroot=/vol/1/sgw/autobuilder/yab/yocto-slave/external/build/build/tmp/sysroots/beagleboard -DHAVE_CONFIG_H -I. -I.. -I../include/ust -I../include -I../libustcomm -DUST_COMPONENT=libust -fno-strict-aliasing -Wall -pipe -g -feliminate-unused-debug-types -MT libust_la-tracectl.lo -MD -MP -MF .deps/libust_la-tracectl.Tpo -c tracectl.c -o libust_la-tracectl.o >/dev/null 2>&1
| mv -f .deps/libust_la-tracectl.Tpo .deps/libust_la-tracectl.Plo
| make[2]: Leaving directory `/vol/1/sgw/autobuilder/yab/yocto-slave/external/build/build/tmp/work/armv7a-vfp-neon-poky-linux-gnueabi/lttng-ust-0.15-r2/ust-0.15/libust'
| make[1]: *** [all-recursive] Error 1
| make[1]: Leaving directory `/vol/1/sgw/autobuilder/yab/yocto-slave/external/build/build/tmp/work/armv7a-vfp-neon-poky-linux-gnueabi/lttng-ust-0.15-r2/ust-0.15'
| make: *** [all] Error 2
| ERROR: oe_runmake failed
| ERROR: Function 'do_compile' failed (see /vol/1/sgw/autobuilder/yab/yocto-slave/external/build/build/tmp/work/armv7a-vfp-neon-poky-linux-gnueabi/lttng-ust-0.15-r2/temp/log.do_compile.27601 for further information)
I'm not surprised change the march didn't work, the tune files are setup for arm7. Consider changing the DEFAULT_TUNE in the beagleboard to build without neon: DEFAULT_TUNE = "cortexa8" do this before the include of the tune-cortexa8.inc file. Could be related to compiler bug: http://gcc.gnu.org/bugzilla/show_bug.cgi?id=43137 Which was just resolved with the following patch. http://gcc.gnu.org/viewcvs?view=revision&revision=163935 T(In reply to comment #5) > Could be related to compiler bug: > > http://gcc.gnu.org/bugzilla/show_bug.cgi?id=43137 > It would be more compelling if that were a floating point issue. The failing line in lttng contained a double. I didn't examine it closely, but at a glance I thought it might make sense to try without the -neon vector floating point stuff. But, worth a shot. Ignore the last comment, this is more appropriate. http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50099 The previously mentioned bugfix is not correct for this situation. (In reply to comment #7) > Ignore the last comment, this is more appropriate. > This reference my last comment, not Darren's I got a mid-air collision! > http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50099 > > The previously mentioned bugfix is not correct for this situation. I am able to reproduce the issue now. | vfprintf.c:956:1: error: unrecognizable insn: | (insn 3968 3967 3969 145 (set (subreg:SI (reg/v:DI 160 [ _umax ]) 0) | (sign_extend:SI (mem:QI (plus:SI (mult:SI (reg/v:SI 166 [ nextarg ]) | (const_int 8 [0x8])) | (reg/f:SI 370 [ argtable.7 ])) [0 *D.6937_569+0 S1 A32]))) vfprintf.c:555 -1 | (nil)) | vfprintf.c:956:1: internal compiler error: in extract_insn, at recog.c:2109 | Please submit a full bug report, | with preprocessed source if appropriate. | See <http://gcc.gnu.org/bugs.html> for instructions. | make[2]: *** [libustsnprintf_la-vfprintf.lo] Error 1 | make[2]: Leaving directory `/disk0/pokybuild/build0/tmp/work/armv7a-vfp-neon-poky-linux-gnueabi/lttng-ust-0.15-r2/ust-0.15/snprintf' removing neon Floating parameter: "-mfpu=neon" does not help. I am seeing same error with it.
$ /bin/sh ../arm-poky-linux-gnueabi-libtool --tag=CC --mode=compile ccache arm-poky-linux-gnueabi-gcc -march=armv7-a -fno-tree-vectorize -mthumb-interwork -mfloat-abi=softfp -mtune=cortex-a8 --sysroot=/disk0/pokybuild/build0/tmp/sysroots/beagleboard -DHAVE_CONFIG_H -I. -I.. -I../include/ust -I../include -I../libustcomm -DUST_COMPONENT="ust_snprintf" -fPIC -fno-strict-aliasing -Wall -O2 -pipe -g -feliminate-unused-debug-types -MT libustsnprintf_la-vfprintf.lo -MD -MP -MF .deps/libustsnprintf_la-vfprintf.Tpo -c -o libustsnprintf_la-vfprintf.lo `test -f 'vfprintf.c' || echo './'`vfprintf.c
arm-poky-linux-gnueabi-libtool: compile: ccache arm-poky-linux-gnueabi-gcc -march=armv7-a -fno-tree-vectorize -mthumb-interwork -mfloat-abi=softfp -mtune=cortex-a8 --sysroot=/disk0/pokybuild/build0/tmp/sysroots/beagleboard -DHAVE_CONFIG_H -I. -I.. -I../include/ust -I../include -I../libustcomm -DUST_COMPONENT=ust_snprintf -fPIC -fno-strict-aliasing -Wall -O2 -pipe -g -feliminate-unused-debug-types -MT libustsnprintf_la-vfprintf.lo -MD -MP -MF .deps/libustsnprintf_la-vfprintf.Tpo -c vfprintf.c -fPIC -DPIC -o .libs/libustsnprintf_la-vfprintf.o
vfprintf.c: In function 'ust_safe_vfprintf':
vfprintf.c:956:1: error: unrecognizable insn:
(insn 3968 3967 3969 145 (set (subreg:SI (reg/v:DI 160 [ _umax ]) 0)
(sign_extend:SI (mem:QI (plus:SI (mult:SI (reg/v:SI 166 [ nextarg ])
(const_int 8 [0x8]))
(reg/f:SI 370 [ argtable.7 ])) [0 *D.5277_569+0 S1 A32]))) vfprintf.c:555 -1
(nil))
vfprintf.c:956:1: internal compiler error: in extract_insn, at recog.c:2109
Please submit a full bug report,
with preprocessed source if appropriate.
See <http://gcc.gnu.org/bugs.html> for instructions.
This file has the use of dmb instruction enabled. /disk0/pokybuild/build0/tmp/sysroots/beagleboard/usr/include/urcu/config.h /* Use the dmb instruction is available for use on ARM. */ #define CONFIG_RCU_ARM_HAVE_DMB 1 Which is making armv5 arch not work for the recipe. Nitin That's a secondary issue that arose from changing the tune file for the entire build. Beagleboard builds as armv7a. Thanks to Khem Raj for the patch http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=0efd5b3d114a23c6821183e0f6c0538bf25e97b7 Verified with 20110908 build. Tree/Branch: poky-contrib/master_under_test Poky Commit:5fa508a717da07ef7352e4ac385ac276156aedec Beagleboard image can be built now. |