From: David Carlton <carlton@math.stanford.edu>
To: gdb <gdb@sources.redhat.com>
Cc: Nathanael Nerode <neroden@twcny.rr.com>
Subject: top level configure isn't working
Date: Mon, 17 Feb 2003 17:07:00 -0000 [thread overview]
Message-ID: <ro1smum6dku.fsf@jackfruit.Stanford.EDU> (raw)
Right now I can't run configure in src/; I get the following message:
papaya$ ./configure --enable-gdb-build-warnings=,-Werror
loading cache ./config.cache
checking host system type... i686-pc-linux-gnu
checking target system type... i686-pc-linux-gnu
checking build system type... i686-pc-linux-gnu
*** removing intl/Makefile to force reconfigure
*** removing mmalloc/Makefile to force reconfigure
*** removing libiberty/Makefile to force reconfigure
*** removing opcodes/Makefile to force reconfigure
*** removing bfd/Makefile to force reconfigure
*** removing readline/Makefile to force reconfigure
*** removing tcl/Makefile to force reconfigure
*** removing sim/Makefile to force reconfigure
*** removing gdb/Makefile to force reconfigure
*** removing etc/Makefile to force reconfigure
*** removing expect/Makefile to force reconfigure
*** removing dejagnu/Makefile to force reconfigure
*** removing utils/Makefile to force reconfigure
./configure: line 2707: syntax error near unexpected token `NCN_STRICT_CHECK_TOOL(AR,'
./configure: line 2707: `NCN_STRICT_CHECK_TOOL(AR, ar)'
Any suggestions as to what could be going wrong? Is it my setup, or a
problem somewhere else? I last built GDB in that directory chain on
Friday, though I'm not sure if I CVS updated in the top level that
day.
David Carlton
carlton@math.stanford.edu
next reply other threads:[~2003-02-17 17:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-17 17:07 David Carlton [this message]
2003-02-17 17:18 ` Andrew Cagney
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=ro1smum6dku.fsf@jackfruit.Stanford.EDU \
--to=carlton@math.stanford.edu \
--cc=gdb@sources.redhat.com \
--cc=neroden@twcny.rr.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