* question meta-toolchain on x86_64 for armv5te
@ 2009-11-10 16:03 Johannes Maier
2009-11-10 16:16 ` Chris Conroy
` (2 more replies)
0 siblings, 3 replies; 4+ messages in thread
From: Johannes Maier @ 2009-11-10 16:03 UTC (permalink / raw)
To: openembedded-devel
Hi@all,
I'm new to openembedded and I didn't find any answers to my questions so I hope to find here some help.
I get an error while building the meta-toolchain on x86_64 for armv5te.
So I wanted to ask if it is in general better to use a 32bit system for such tasks since I don't get any error there?
The error is as follows:
angstrom-linux-gnueabi/gdb-cross-sdk-6.8-r2/gdb-6.8/gdb -I/home/test/oe/stuff/openembedded/tmp/work/x86_64-armv5te-sdk-angstrom-linux-gnueabi/gdb-cross-sdk-6.8-r2/gdb-6.8/gdb/config -DLOCALEDIR="\"/usr/local/angstrom/arm/share/locale\"" -DHAVE_CONFIG_H -I/home/test/oe/stuff/openembedded/tmp/work/x86_64-armv5te-sdk-angstrom-linux-gnueabi/gdb-cross-sdk-6.8-r2/gdb-6.8/gdb/../include/opcode -I/home/test/oe/stuff/openembedded/tmp/work/x86_64-armv5te-sdk-angstrom-linux-gnueabi/gdb-cross-sdk-6.8-r2/gdb-6.8/gdb/../readline/.. -I../bfd -I/home/test/oe/stuff/openembedded/tmp/work/x86_64-armv5te-sdk-angstrom-linux-gnueabi/gdb-cross-sdk-6.8-r2/gdb-6.8/gdb/../bfd -I/home/test/oe/stuff/openembedded/tmp/work/x86_64-armv5te-sdk-angstrom-linux-gnueabi/gdb-cross-sdk-6.8-r2/gdb-6.8/gdb/../include -I../libdecnumber -I/home/test/oe/stuff/openembedded/tmp/work/x86_64-armv5te-sdk-angstrom-linux-gnueabi/gdb-cross-sdk-6.8-r2/gdb-6.8/gdb/../libdecnumber -DMI_OUT=1 -DTUI=1
-isystem/home/test/oe/stuff/opene
mbedded/tmp/staging/x86_64-linux/usr/include -Wall -Wdeclaration-after-statement -Wpointer-arith -Wformat-nonliteral -Wno-pointer-sign -Wno-unused -Wno-switch -Wno-char-subscripts -Werror /home/test/oe/stuff/openembedded/tmp/work/x86_64-armv5te-sdk-angstrom-linux-gnueabi/gdb-cross-sdk-6.8-r2/gdb-6.8/gdb/value.c
| ccache gcc -c -isystem/home/test/oe/stuff/openembedded/tmp/staging/x86_64-linux/usr/include -O2 -I. -I/home/test/oe/stuff/openembedded/tmp/work/x86_64-armv5te-sdk-angstrom-linux-gnueabi/gdb-cross-sdk-6.8-r2/gdb-6.8/gdb -I/home/test/oe/stuff/openembedded/tmp/work/x86_64-armv5te-sdk-angstrom-linux-gnueabi/gdb-cross-sdk-6.8-r2/gdb-6.8/gdb/config -DLOCALEDIR="\"/usr/local/angstrom/arm/share/locale\"" -DHAVE_CONFIG_H -I/home/test/oe/stuff/openembedded/tmp/work/x86_64-armv5te-sdk-angstrom-linux-gnueabi/gdb-cross-sdk-6.8-r2/gdb-6.8/gdb/../include/opcode -I/home/test/oe/stuff/openembedded/tmp/work/x86_64-armv5te-sdk-angstrom-linux-gnueabi/gdb-cross-sdk-6.8-r2/gdb-6.8/gdb/../readline/.. -I../bfd -I/home/test/oe/stuff/openembedded/tmp/work/x86_64-armv5te-sdk-angstrom-linux-gnueabi/gdb-cross-sdk-6.8-r2/gdb-6.8/gdb/../bfd -I/home/test/oe/stuff/openembedded/tmp/work/x86_64-armv5te-sdk-angstrom-linux-gnueabi/gdb-cross-sdk-6.8-r2/gdb-6.8/gdb/../include -I../libdecnumber
-I/home/test/oe/stuff/
openembedded/tmp/work/x86_64-armv5te-sdk-angstrom-linux-gnueabi/gdb-cross-sdk-6.8-r2/gdb-6.8/gdb/../libdecnumber -DMI_OUT=1 -DTUI=1 -isystem/home/test/oe/stuff/openembedded/tmp/staging/x86_64-linux/usr/include -Wall -Wdeclaration-after-statement -Wpointer-arith -Wformat-nonliteral -Wno-pointer-sign -Wno-unused -Wno-switch -Wno-char-subscripts -Werror /home/test/oe/stuff/openembedded/tmp/work/x86_64-armv5te-sdk-angstrom-linux-gnueabi/gdb-cross-sdk-6.8-r2/gdb-6.8/gdb/eval.c
| cc1: warnings being treated as errors
| /home/test/oe/stuff/openembedded/tmp/work/x86_64-armv5te-sdk-angstrom-linux-gnueabi/gdb-cross-sdk-6.8-r2/gdb-6.8/gdb/eval.c: In function 'evaluate_subexp_standard':
| /home/test/oe/stuff/openembedded/tmp/work/x86_64-armv5te-sdk-angstrom-linux-gnueabi/gdb-cross-sdk-6.8-r2/gdb-6.8/gdb/eval.c:1705: error: 'subscript_array' may be used uninitialized in this function
| /home/test/oe/stuff/openembedded/tmp/work/x86_64-armv5te-sdk-angstrom-linux-gnueabi/gdb-cross-sdk-6.8-r2/gdb-6.8/gdb/eval.c:1644: note: 'subscript_array' was declared here
| make[2]: *** [eval.o] Error 1
| make[2]: Leaving directory `/home/test/oe/stuff/openembedded/tmp/work/x86_64-armv5te-sdk-angstrom-linux-gnueabi/gdb-cross-sdk-6.8-r2/build-arm-angstrom-linux-gnueabi/gdb'
| make[1]: *** [all-gdb] Error 2
| make[1]: Leaving directory `/home/test/oe/stuff/openembedded/tmp/work/x86_64-armv5te-sdk-angstrom-linux-gnueabi/gdb-cross-sdk-6.8-r2/build-arm-angstrom-linux-gnueabi'
| make: *** [all] Error 2
| FATAL: oe_runmake failed
NOTE: Task failed: /home/test/oe/stuff/openembedded/tmp/work/x86_64-armv5te-sdk-angstrom-linux-gnueabi/gdb-cross-sdk-6.8-r2/temp/log.do_compile.19984
ERROR: TaskFailed event exception, aborting
ERROR: Build of /home/test/oe/stuff/openembedded/recipes/gdb/gdb-cross-sdk_6.8.bb do_compile failed
ERROR: Task 434 (/home/test/oe/stuff/openembedded/recipes/gdb/gdb-cross-sdk_6.8.bb, do_compile) failed
NOTE: Tasks Summary: Attempted 610 tasks of which 0 didn't need to be rerun and 1 failed.
ERROR: '/home/test/oe/stuff/openembedded/recipes/gdb/gdb-cross-sdk_6.8.bb' failed
test@test-desktop:~/oe/stuff/openembedded$
Thanks in advance,
majo
^ permalink raw reply [flat|nested] 4+ messages in thread* Re: question meta-toolchain on x86_64 for armv5te
2009-11-10 16:03 question meta-toolchain on x86_64 for armv5te Johannes Maier
@ 2009-11-10 16:16 ` Chris Conroy
2009-11-11 1:52 ` Holger Hans Peter Freyther
2009-11-11 8:13 ` Khem Raj
2 siblings, 0 replies; 4+ messages in thread
From: Chris Conroy @ 2009-11-10 16:16 UTC (permalink / raw)
To: openembedded-devel
On Tue, 2009-11-10 at 16:03 +0000, Johannes Maier wrote:
> Hi@all,
>
> I'm new to openembedded and I didn't find any answers to my questions so I hope to find here some help.
>
> I get an error while building the meta-toolchain on x86_64 for armv5te.
>
> So I wanted to ask if it is in general better to use a 32bit system for such tasks since I don't get any error there?
For what it's worth, I've got meta-toolchain working on x86_64 here,
though I'm not in sync with trunk and do have some mods pulled from
poky--I don't believe any of those changes were x86_64 host specific.
I would guess that you are leaking your host system headers into your
build and they end up not showing up as errors on a 32 bit host since
that presumably matches your target.
>
> The error is as follows:
>
> angstrom-linux-gnueabi/gdb-cross-sdk-6.8-r2/gdb-6.8/gdb -I/home/test/oe/stuff/openembedded/tmp/work/x86_64-armv5te-sdk-angstrom-linux-gnueabi/gdb-cross-sdk-6.8-r2/gdb-6.8/gdb/config -DLOCALEDIR="\"/usr/local/angstrom/arm/share/locale\"" -DHAVE_CONFIG_H -I/home/test/oe/stuff/openembedded/tmp/work/x86_64-armv5te-sdk-angstrom-linux-gnueabi/gdb-cross-sdk-6.8-r2/gdb-6.8/gdb/../include/opcode -I/home/test/oe/stuff/openembedded/tmp/work/x86_64-armv5te-sdk-angstrom-linux-gnueabi/gdb-cross-sdk-6.8-r2/gdb-6.8/gdb/../readline/.. -I../bfd -I/home/test/oe/stuff/openembedded/tmp/work/x86_64-armv5te-sdk-angstrom-linux-gnueabi/gdb-cross-sdk-6.8-r2/gdb-6.8/gdb/../bfd -I/home/test/oe/stuff/openembedded/tmp/work/x86_64-armv5te-sdk-angstrom-linux-gnueabi/gdb-cross-sdk-6.8-r2/gdb-6.8/gdb/../include -I../libdecnumber -I/home/test/oe/stuff/openembedded/tmp/work/x86_64-armv5te-sdk-angstrom-linux-gnueabi/gdb-cross-sdk-6.8-r2/gdb-6.8/gdb/../libdecnumber -DMI_OUT=1 -DTUI=1
> -isystem/home/test/oe/stuff/opene
> mbedded/tmp/staging/x86_64-linux/usr/include -Wall -Wdeclaration-after-statement -Wpointer-arith -Wformat-nonliteral -Wno-pointer-sign -Wno-unused -Wno-switch -Wno-char-subscripts -Werror /home/test/oe/stuff/openembedded/tmp/work/x86_64-armv5te-sdk-angstrom-linux-gnueabi/gdb-cross-sdk-6.8-r2/gdb-6.8/gdb/value.c
> | ccache gcc -c -isystem/home/test/oe/stuff/openembedded/tmp/staging/x86_64-linux/usr/include -O2 -I. -I/home/test/oe/stuff/openembedded/tmp/work/x86_64-armv5te-sdk-angstrom-linux-gnueabi/gdb-cross-sdk-6.8-r2/gdb-6.8/gdb -I/home/test/oe/stuff/openembedded/tmp/work/x86_64-armv5te-sdk-angstrom-linux-gnueabi/gdb-cross-sdk-6.8-r2/gdb-6.8/gdb/config -DLOCALEDIR="\"/usr/local/angstrom/arm/share/locale\"" -DHAVE_CONFIG_H -I/home/test/oe/stuff/openembedded/tmp/work/x86_64-armv5te-sdk-angstrom-linux-gnueabi/gdb-cross-sdk-6.8-r2/gdb-6.8/gdb/../include/opcode -I/home/test/oe/stuff/openembedded/tmp/work/x86_64-armv5te-sdk-angstrom-linux-gnueabi/gdb-cross-sdk-6.8-r2/gdb-6.8/gdb/../readline/.. -I../bfd -I/home/test/oe/stuff/openembedded/tmp/work/x86_64-armv5te-sdk-angstrom-linux-gnueabi/gdb-cross-sdk-6.8-r2/gdb-6.8/gdb/../bfd -I/home/test/oe/stuff/openembedded/tmp/work/x86_64-armv5te-sdk-angstrom-linux-gnueabi/gdb-cross-sdk-6.8-r2/gdb-6.8/gdb/../include -I../libdecnumber
> -I/home/test/oe/stuff/
> openembedded/tmp/work/x86_64-armv5te-sdk-angstrom-linux-gnueabi/gdb-cross-sdk-6.8-r2/gdb-6.8/gdb/../libdecnumber -DMI_OUT=1 -DTUI=1 -isystem/home/test/oe/stuff/openembedded/tmp/staging/x86_64-linux/usr/include -Wall -Wdeclaration-after-statement -Wpointer-arith -Wformat-nonliteral -Wno-pointer-sign -Wno-unused -Wno-switch -Wno-char-subscripts -Werror /home/test/oe/stuff/openembedded/tmp/work/x86_64-armv5te-sdk-angstrom-linux-gnueabi/gdb-cross-sdk-6.8-r2/gdb-6.8/gdb/eval.c
> | cc1: warnings being treated as errors
> | /home/test/oe/stuff/openembedded/tmp/work/x86_64-armv5te-sdk-angstrom-linux-gnueabi/gdb-cross-sdk-6.8-r2/gdb-6.8/gdb/eval.c: In function 'evaluate_subexp_standard':
> | /home/test/oe/stuff/openembedded/tmp/work/x86_64-armv5te-sdk-angstrom-linux-gnueabi/gdb-cross-sdk-6.8-r2/gdb-6.8/gdb/eval.c:1705: error: 'subscript_array' may be used uninitialized in this function
> | /home/test/oe/stuff/openembedded/tmp/work/x86_64-armv5te-sdk-angstrom-linux-gnueabi/gdb-cross-sdk-6.8-r2/gdb-6.8/gdb/eval.c:1644: note: 'subscript_array' was declared here
> | make[2]: *** [eval.o] Error 1
> | make[2]: Leaving directory `/home/test/oe/stuff/openembedded/tmp/work/x86_64-armv5te-sdk-angstrom-linux-gnueabi/gdb-cross-sdk-6.8-r2/build-arm-angstrom-linux-gnueabi/gdb'
> | make[1]: *** [all-gdb] Error 2
> | make[1]: Leaving directory `/home/test/oe/stuff/openembedded/tmp/work/x86_64-armv5te-sdk-angstrom-linux-gnueabi/gdb-cross-sdk-6.8-r2/build-arm-angstrom-linux-gnueabi'
> | make: *** [all] Error 2
> | FATAL: oe_runmake failed
> NOTE: Task failed: /home/test/oe/stuff/openembedded/tmp/work/x86_64-armv5te-sdk-angstrom-linux-gnueabi/gdb-cross-sdk-6.8-r2/temp/log.do_compile.19984
> ERROR: TaskFailed event exception, aborting
> ERROR: Build of /home/test/oe/stuff/openembedded/recipes/gdb/gdb-cross-sdk_6.8.bb do_compile failed
> ERROR: Task 434 (/home/test/oe/stuff/openembedded/recipes/gdb/gdb-cross-sdk_6.8.bb, do_compile) failed
> NOTE: Tasks Summary: Attempted 610 tasks of which 0 didn't need to be rerun and 1 failed.
> ERROR: '/home/test/oe/stuff/openembedded/recipes/gdb/gdb-cross-sdk_6.8.bb' failed
> test@test-desktop:~/oe/stuff/openembedded$
>
> Thanks in advance,
> majo
>
>
>
>
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: question meta-toolchain on x86_64 for armv5te
2009-11-10 16:03 question meta-toolchain on x86_64 for armv5te Johannes Maier
2009-11-10 16:16 ` Chris Conroy
@ 2009-11-11 1:52 ` Holger Hans Peter Freyther
2009-11-11 8:13 ` Khem Raj
2 siblings, 0 replies; 4+ messages in thread
From: Holger Hans Peter Freyther @ 2009-11-11 1:52 UTC (permalink / raw)
To: openembedded-devel
On Tuesday 10 November 2009 17:03:06 Johannes Maier wrote:
> Hi@all,
>
> I'm new to openembedded and I didn't find any answers to my questions so I
> hope to find here some help.
>
> I get an error while building the meta-toolchain on x86_64 for armv5te.
>
> So I wanted to ask if it is in general better to use a 32bit system for
> such tasks since I don't get any error there?
This is not 32 vs 64 bits... more likely if fortify is enabled during
compile.. The error looks like something I had fixed... so what are you
building, using which OE revision?
z.
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: question meta-toolchain on x86_64 for armv5te
2009-11-10 16:03 question meta-toolchain on x86_64 for armv5te Johannes Maier
2009-11-10 16:16 ` Chris Conroy
2009-11-11 1:52 ` Holger Hans Peter Freyther
@ 2009-11-11 8:13 ` Khem Raj
2 siblings, 0 replies; 4+ messages in thread
From: Khem Raj @ 2009-11-11 8:13 UTC (permalink / raw)
To: openembedded-devel
On Tue, Nov 10, 2009 at 8:03 AM, Johannes Maier <jm@huber-online.com> wrote:
> Hi@all,
>
> I'm new to openembedded and I didn't find any answers to my questions so I hope to find here some help.
>
> I get an error while building the meta-toolchain on x86_64 for armv5te.
>
> So I wanted to ask if it is in general better to use a 32bit system for such tasks since I don't get any error there?
>
> The error is as follows:
>
> angstrom-linux-gnueabi/gdb-cross-sdk-6.8-r2/gdb-6.8/gdb -I/home/test/oe/stuff/openembedded/tmp/work/x86_64-armv5te-sdk-angstrom-linux-gnueabi/gdb-cross-sdk-6.8-r2/gdb-6.8/gdb/config -DLOCALEDIR="\"/usr/local/angstrom/arm/share/locale\"" -DHAVE_CONFIG_H -I/home/test/oe/stuff/openembedded/tmp/work/x86_64-armv5te-sdk-angstrom-linux-gnueabi/gdb-cross-sdk-6.8-r2/gdb-6.8/gdb/../include/opcode -I/home/test/oe/stuff/openembedded/tmp/work/x86_64-armv5te-sdk-angstrom-linux-gnueabi/gdb-cross-sdk-6.8-r2/gdb-6.8/gdb/../readline/.. -I../bfd -I/home/test/oe/stuff/openembedded/tmp/work/x86_64-armv5te-sdk-angstrom-linux-gnueabi/gdb-cross-sdk-6.8-r2/gdb-6.8/gdb/../bfd -I/home/test/oe/stuff/openembedded/tmp/work/x86_64-armv5te-sdk-angstrom-linux-gnueabi/gdb-cross-sdk-6.8-r2/gdb-6.8/gdb/../include -I../libdecnumber -I/home/test/oe/stuff/openembedded/tmp/work/x86_64-armv5te-sdk-angstrom-linux-gnueabi/gdb-cross-sdk-6.8-r2/gdb-6.8/gdb/../libdecnumber -DMI_OUT=1 -DTUI=1
> -isystem/home/test/oe/stuff/opene
> mbedded/tmp/staging/x86_64-linux/usr/include -Wall -Wdeclaration-after-statement -Wpointer-arith -Wformat-nonliteral -Wno-pointer-sign -Wno-unused -Wno-switch -Wno-char-subscripts -Werror /home/test/oe/stuff/openembedded/tmp/work/x86_64-armv5te-sdk-angstrom-linux-gnueabi/gdb-cross-sdk-6.8-r2/gdb-6.8/gdb/value.c
> | ccache gcc -c -isystem/home/test/oe/stuff/openembedded/tmp/staging/x86_64-linux/usr/include -O2 -I. -I/home/test/oe/stuff/openembedded/tmp/work/x86_64-armv5te-sdk-angstrom-linux-gnueabi/gdb-cross-sdk-6.8-r2/gdb-6.8/gdb -I/home/test/oe/stuff/openembedded/tmp/work/x86_64-armv5te-sdk-angstrom-linux-gnueabi/gdb-cross-sdk-6.8-r2/gdb-6.8/gdb/config -DLOCALEDIR="\"/usr/local/angstrom/arm/share/locale\"" -DHAVE_CONFIG_H -I/home/test/oe/stuff/openembedded/tmp/work/x86_64-armv5te-sdk-angstrom-linux-gnueabi/gdb-cross-sdk-6.8-r2/gdb-6.8/gdb/../include/opcode -I/home/test/oe/stuff/openembedded/tmp/work/x86_64-armv5te-sdk-angstrom-linux-gnueabi/gdb-cross-sdk-6.8-r2/gdb-6.8/gdb/../readline/.. -I../bfd -I/home/test/oe/stuff/openembedded/tmp/work/x86_64-armv5te-sdk-angstrom-linux-gnueabi/gdb-cross-sdk-6.8-r2/gdb-6.8/gdb/../bfd -I/home/test/oe/stuff/openembedded/tmp/work/x86_64-armv5te-sdk-angstrom-linux-gnueabi/gdb-cross-sdk-6.8-r2/gdb-6.8/gdb/../include -I../libdecnumber
> -I/home/test/oe/stuff/
> openembedded/tmp/work/x86_64-armv5te-sdk-angstrom-linux-gnueabi/gdb-cross-sdk-6.8-r2/gdb-6.8/gdb/../libdecnumber -DMI_OUT=1 -DTUI=1 -isystem/home/test/oe/stuff/openembedded/tmp/staging/x86_64-linux/usr/include -Wall -Wdeclaration-after-statement -Wpointer-arith -Wformat-nonliteral -Wno-pointer-sign -Wno-unused -Wno-switch -Wno-char-subscripts -Werror /home/test/oe/stuff/openembedded/tmp/work/x86_64-armv5te-sdk-angstrom-linux-gnueabi/gdb-cross-sdk-6.8-r2/gdb-6.8/gdb/eval.c
> | cc1: warnings being treated as errors
> | /home/test/oe/stuff/openembedded/tmp/work/x86_64-armv5te-sdk-angstrom-linux-gnueabi/gdb-cross-sdk-6.8-r2/gdb-6.8/gdb/eval.c: In function 'evaluate_subexp_standard':
> | /home/test/oe/stuff/openembedded/tmp/work/x86_64-armv5te-sdk-angstrom-linux-gnueabi/gdb-cross-sdk-6.8-r2/gdb-6.8/gdb/eval.c:1705: error: 'subscript_array' may be used uninitialized in this function
> | /home/test/oe/stuff/openembedded/tmp/work/x86_64-armv5te-sdk-angstrom-linux-gnueabi/gdb-cross-sdk-6.8-r2/gdb-6.8/gdb/eval.c:1644: note: 'subscript_array' was declared here
you might be using gcc 4.4 on your build box.
gcc 4.4 spits more warnings like what you see. You can do couple of
things. add --disable-werror to gdb recipes but
I would not recommend that. Secondly you can create a patch to gdb/eval.c
Modify line 1644 of gdb/eval.c to
int subscript_array[MAX_FORTRAN_DIMS] = {0};
and this should make gcc 4.4 happy.
-Khem
Thanks
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2009-11-11 8:20 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2009-11-10 16:03 question meta-toolchain on x86_64 for armv5te Johannes Maier
2009-11-10 16:16 ` Chris Conroy
2009-11-11 1:52 ` Holger Hans Peter Freyther
2009-11-11 8:13 ` Khem Raj
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.