From: Joel Sherrill <joel.sherrill@oarcorp.com>
To: "gdb@sourceware.org" <gdb@sourceware.org>,
Anthony Green <green@moxielogic.com>
Subject: gdb moxie build failure
Date: Mon, 18 Aug 2014 22:14:00 -0000 [thread overview]
Message-ID: <53F27ADC.4070609@oarcorp.com> (raw)
Hi
gdb on the head has moxie-rtems fail like this:
echo "/* generated by Makefile */" > tmp-hw.h
/bin/sh ../../../binutils-gdb/sim/moxie/../common/create-version.sh
../../../binutils-gdb/sim/moxie/.. x86_64-unknown-linux-gnu
moxie-rtems4.11 version.c
sim_hw=""; \
for hw in $sim_hw ; do \
echo "extern const struct hw_descriptor dv_${hw}_descriptor[];" ; \
done >> tmp-hw.h
dtc -O dtb -o moxie-gdb.dtb ../../../binutils-gdb/sim/moxie/moxie-gdb.dts
make[3]: dtc: Command not found
echo "const struct hw_descriptor *hw_descriptors[] = {" >> tmp-hw.h
make[3]: *** [moxie-gdb.dtb] Error 127
make[3]: *** Waiting for unfinished jobs....
sim_hw=""; \
for hw in $sim_hw ; do \
Is dtc a required tool that is not checked for? Is the output in the tree
but not timestamped? maintainer only tool?
Thanks.
--
Joel Sherrill, Ph.D. Director of Research & Development
joel.sherrill@OARcorp.com On-Line Applications Research
Ask me about RTEMS: a free RTOS Huntsville AL 35805
Support Available (256) 722-9985
next reply other threads:[~2014-08-18 22:14 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-18 22:14 Joel Sherrill [this message]
2014-08-19 5:38 ` integrating dtc into the sim/ tree Mike Frysinger
2014-08-19 6:26 ` Joel Brobecker
2014-08-20 9:33 ` Mike Frysinger
2014-08-20 9:53 ` Joel Brobecker
2014-08-20 15:30 ` Mike Frysinger
2014-08-20 16:06 ` Joel Brobecker
2014-08-20 16:11 ` Joel Sherrill
2014-08-20 16:19 ` Joel Brobecker
2014-08-20 16:37 ` Joel Sherrill
2014-08-21 1:31 ` Mike Frysinger
2014-08-21 1:25 ` Mike Frysinger
2014-08-21 7:32 ` Joel Brobecker
2014-08-21 9:05 ` Pedro Alves
2014-08-21 13:58 ` Joel Sherrill
2014-08-21 16:25 ` Richard Henderson
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=53F27ADC.4070609@oarcorp.com \
--to=joel.sherrill@oarcorp.com \
--cc=gdb@sourceware.org \
--cc=green@moxielogic.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox