From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: gdb-patches@sourceware.org
Cc: Doug Evans <dje@google.com>
Subject: [patch] Fix build if using --with-system-readline
Date: Sun, 29 Nov 2009 20:57:00 -0000 [thread overview]
Message-ID: <20091129205707.GA9408@host0.dyn.jankratochvil.net> (raw)
Hi,
./configure --enable-targets=all --with-system-readline; make
->
gcc -g -O2 -I. -I. -I./common -I./config -DLOCALEDIR="\"/usr/local/share/locale\"" -DHAVE_CONFIG_H -I./../include/opcode -I../bfd -I./../bfd -I./../include -I../libdecnumber -I./../libdecnumber -I./gnulib -Ignulib -DMI_OUT=1 -DTUI=1 -Wall -Wdeclaration-after-statement -Wpointer-arith -Wformat-nonliteral -Wno-pointer-sign -Wno-unused -Wunused-value -Wno-switch -Wno-char-subscripts -Werror -c -o frv-tdep.o -MT frv-tdep.o -MMD -MP -MF .deps/frv-tdep.Tpo frv-tdep.c
frv-tdep.c:35:60: error: opcodes/frv-desc.h: No such file or directory
(it is not `make -j' race)
because with --with-system-readline there is no:
-I./../readline/..
OK to check-in?
Thanks,
Jan
gdb/
2009-11-29 Jan Kratochvil <jan.kratochvil@redhat.com>
Fix build if using --with-system-readline.
* Makefile.in (OPCODES_CFLAGS): Add `-I$(OPCODES_DIR)/..'.
--- a/gdb/Makefile.in
+++ b/gdb/Makefile.in
@@ -301,7 +301,7 @@ OPCODES = $(OPCODES_DIR)/libopcodes.a
# Where are the other opcode tables which only have header file
# versions?
OP_INCLUDE = $(INCLUDE_DIR)/opcode
-OPCODES_CFLAGS = -I$(OP_INCLUDE)
+OPCODES_CFLAGS = -I$(OP_INCLUDE) -I$(OPCODES_DIR)/..
# The simulator is usually nonexistent; targets that include one
# should set this to list all the .o or .a files to be linked in.
next reply other threads:[~2009-11-29 20:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-29 20:57 Jan Kratochvil [this message]
2009-11-30 17:44 ` Doug Evans
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=20091129205707.GA9408@host0.dyn.jankratochvil.net \
--to=jan.kratochvil@redhat.com \
--cc=dje@google.com \
--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