From: "Keith Ross (E-Lands)" <kross@elands.co.nz>
To: insight@sourceware.org
Subject: Can't build missing ADA, Flex
Date: Fri, 18 Nov 2005 04:59:00 -0000 [thread overview]
Message-ID: <437D6022.9080808@elands.co.nz> (raw)
Hi,
I know that there are lots of ongoing build issues with insight-6.30.50
and have been following the patches, but I think my problem is operator
error.
I'm building insight-weekly-6.30.50.20051114 under gcc-4.0.2 (c, c++
only) and cygwin and get
the follow error. I install flex but where/what's ada. I assume that I
configured it wrong.
configure --target=arm-elf --prefix=/gnutools/insight-6.3
make[2]: Entering directory `/tmp/build/gdb/gdb'
if [ "/src/insight/gdb/missing flex" ] && /src/insight/gdb/missing flex
--version >/dev/null 2>&1; then \
/src/insight/gdb/missing flex -oada-lex.c
/src/insight/gdb/gdb/ada-lex.l && \
rm -f ada-lex.c.new && \
sed -e '/extern.*malloc/d' \
-e '/extern.*realloc/d' \
-e '/extern.*free/d' \
-e '/include.*malloc.h/d' \
-e 's/\([^x]\)malloc/\1xmalloc/g' \
-e 's/\([^x]\)realloc/\1xrealloc/g' \
-e 's/yy_flex_xrealloc/yyxrealloc/g' \
< ada-lex.c > ada-lex.c.new && \
rm -f ada-lex.c && \
mv ada-lex.c.new ada-lex.c; \
elif [ -f ada-lex.c ]; then \
echo "Warning: ada-lex.c older than ada-lex.l and flex not
available."; \
else \
echo "ada-lex.c missing and flex not available."; \
false; \
fi
ada-lex.c missing and flex not available.
make[2]: *** [ada-lex.c] Error 1
make[2]: Leaving directory `/tmp/build/gdb/gdb'
make[1]: *** [all-gdb] Error 2
make[1]: Leaving directory `/tmp/build/gdb'
make: *** [all] Error 2
make: Leaving directory `/tmp/build/gdb'
%\tmp\build\gdb>flex --version
flex version 2.5.4
Regards,
Keith Ross
next reply other threads:[~2005-11-18 4:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-18 4:59 Keith Ross (E-Lands) [this message]
2005-11-18 22:21 ` Keith Seitz
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=437D6022.9080808@elands.co.nz \
--to=kross@elands.co.nz \
--cc=insight@sourceware.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).