From: Chris Conroy <Chris.Conroy@hillcrestlabs.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: question meta-toolchain on x86_64 for armv5te
Date: Tue, 10 Nov 2009 11:16:41 -0500 [thread overview]
Message-ID: <1257869801.1942.25.camel@conroy-linux> (raw)
In-Reply-To: <DIIE.000005E3001861E8@192.168.11.6>
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
next prev parent reply other threads:[~2009-11-10 16:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-10 16:03 question meta-toolchain on x86_64 for armv5te Johannes Maier
2009-11-10 16:16 ` Chris Conroy [this message]
2009-11-11 1:52 ` Holger Hans Peter Freyther
2009-11-11 8:13 ` Khem Raj
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=1257869801.1942.25.camel@conroy-linux \
--to=chris.conroy@hillcrestlabs.com \
--cc=openembedded-devel@lists.openembedded.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.