This is the mail archive of the
gdb-prs@sourceware.org
mailing list for the GDB project.
tdep/2443: FRV/MEP code fails to build due to -I path mess
- From: vapier at gentoo dot org
- To: gdb-gnats at sources dot redhat dot com
- Date: 7 Apr 2008 00:12:03 -0000
- Subject: tdep/2443: FRV/MEP code fails to build due to -I path mess
- Reply-to: vapier at gentoo dot org
>Number: 2443
>Category: tdep
>Synopsis: FRV/MEP code fails to build due to -I path mess
>Confidential: no
>Severity: non-critical
>Priority: medium
>Responsible: unassigned
>State: open
>Class: change-request
>Submitter-Id: net
>Arrival-Date: Mon Apr 07 00:18:01 UTC 2008
>Closed-Date:
>Last-Modified:
>Originator: vapier@gentoo.org
>Release: gdb-6.8
>Organization:
>Environment:
>Description:
the bundled readline cflags causes bad include paths in gdb from going ignored
if we look at gdb/Makefile when configured with --without-system-readline:
READLINE_DIR = ../readline
READLINE_SRC = $(srcdir)/$(READLINE_DIR)
READLINE_CFLAGS = -I$(READLINE_SRC)/..
this means the -I path now points to the top level:
-I./../readline/..
and if we configure with --without-system-readline, the READLINE_CFLAGS is no longer set which means we have no implicit -I path to the top level
the trouble comes in with frv-tdep.c and mep-tdep.c:
gdb/frv-tdep.c:#include "opcodes/frv-desc.h"
gdb/mep-tdep.c:#include "opcodes/mep-desc.h"
gdb/mep-tdep.c:#include "opcodes/mep-opc.h"
these require an explicit -I path to the toplevel in gdb/Makefile, and since there is no explicit path, this only works when there are implicit readline paths
>How-To-Repeat:
tar xf gdb-6.8.tar.bz2
cd gdb-6.8
./configure --enable-targets=all --with-system-readline
make all-gdb
<frv and mep code fail to build in gdb/>
>Fix:
>Release-Note:
>Audit-Trail:
>Unformatted: