Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Doug Evans <dje@google.com>
To: Jan Kratochvil <jan.kratochvil@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [patch] Fix build if using --with-system-readline
Date: Mon, 30 Nov 2009 17:44:00 -0000	[thread overview]
Message-ID: <e394668d0911300944j31eebccfsf425fb6797503d0f@mail.gmail.com> (raw)
In-Reply-To: <20091129205707.GA9408@host0.dyn.jankratochvil.net>

On Sun, Nov 29, 2009 at 12:57 PM, Jan Kratochvil
<jan.kratochvil@redhat.com> wrote:
> 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.
>


That is the easiest patch, and it doesn't actually change anything
since we're already building with (effectively) -I$(srcdir).
So it's ok with me.
I'd wait a bit to see if anyone else wants to speak up.

Having said that, -I$(srcdir) "feels" less clean than
-I$(OPCODES_DIR).  We have -$(BFD_SRC) already, it seems like opcodes
should be treated no different.
I realize going this route involves more work, fixing all the files
that do #include "opcodes/mumble.h", there's only a handful of them
though.
I'd skip putting in the effort to go this route until someone else agrees.


      reply	other threads:[~2009-11-30 17:44 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-29 20:57 Jan Kratochvil
2009-11-30 17:44 ` Doug Evans [this message]

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=e394668d0911300944j31eebccfsf425fb6797503d0f@mail.gmail.com \
    --to=dje@google.com \
    --cc=gdb-patches@sourceware.org \
    --cc=jan.kratochvil@redhat.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