From: Eli Zaretskii <eliz@gnu.org>
To: gdb-patches@sourceware.org
Subject: NAT_FILE set incorrectly in gdb/Makefile
Date: Sun, 19 Apr 2009 19:00:00 -0000 [thread overview]
Message-ID: <838wlwii4o.fsf@gnu.org> (raw)
"make TAGS" curses thusly:
Making TAGS
.././gdb/config/i386/config/i386/nm-linux64.h: No such file or directory
This is on GNU/Linux, obviously, but I see the equivalent error
message in the DJGPP build.
The problem is this line from gdb/Makefile:
NAT_FILE= config/i386/config/i386/nm-linux64.h
which is obviously incorrect. It looks like the culprit is this line
from configure.ac:
sed -e '/^NAT_FILE[ ]*=/s,^NAT_FILE[ ]*=[ ]*,&config/'"${gdb_host_cpu}"'/,' <Makefile >Makefile.tmp
which seems to run twice, perhaps once by configure, the other time by
config.status. But that's a guess; the truth is I have no idea why
config/i386 gets prepended twice. Does anyone see the villain?
next reply other threads:[~2009-04-19 19:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-19 19:00 Eli Zaretskii [this message]
2009-04-19 21:35 ` Andreas Schwab
2009-04-20 17:09 ` Tom Tromey
2009-04-20 21:29 ` Andreas Schwab
2009-04-21 18:25 ` Tom Tromey
2009-04-20 18:58 ` Eli Zaretskii
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=838wlwii4o.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb-patches@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