Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: "Richard Dawe" <rich@phekda.freeserve.co.uk>
To: gdb-patches@sources.redhat.com
Subject: gdb-5.3: dependency on bfd/bfd.h in gdb/Makefile [PATCH]
Date: Fri, 27 Dec 2002 11:56:00 -0000	[thread overview]
Message-ID: <E18S0BP-00010Q-00@phekda.freeserve.co.uk> (raw)

Hello.

There's a dependency in gdb/Makefile (generated by configure'ing
the gdb-5.3 sources) on bfd/bfd.h. But bfd/bfd.h does not exist.
It seems to be called bfd/libbfd.h now. ChangeLog entry and patch below.

2002-12-27  Richard Dawe  <rich@phekda.freeserve.co.uk>

	* gdb/Makefile.in: BFD header file is bfd/libbfd.h now,
	not bfd/bfd.h.

Please CC me on replies, since I'm not subscribed to gdb-patches.

Thanks, regards, Rich

--- /develop/ports/orig/gdb-5.3/gdb/Makefile.in	2002-11-25 22:05:38.000000000 +0000
+++ gdb/Makefile.in	2002-12-27 15:41:00.000000000 +0000
@@ -574,7 +574,7 @@ aout_aout64_h =	$(INCLUDE_DIR)/aout/aout
 aout_stabs_gnu_h =	$(INCLUDE_DIR)/aout/stabs_gnu.h
 getopt_h =	$(INCLUDE_DIR)/getopt.h
 floatformat_h =	$(INCLUDE_DIR)/floatformat.h
-bfd_h =		$(BFD_DIR)/bfd.h
+bfd_h =		$(BFD_DIR)/libbfd.h
 callback_h =	$(INCLUDE_DIR)/gdb/callback.h
 coff_sym_h =	$(INCLUDE_DIR)/coff/sym.h
 coff_symconst_h =	$(INCLUDE_DIR)/coff/symconst.h
@@ -796,7 +796,7 @@ HFILES_NO_SRCDIR = bcache.h buildsym.h c
 
 # Header files that already have srcdir in them, or which are in objdir.
 
-HFILES_WITH_SRCDIR = ../bfd/bfd.h
+HFILES_WITH_SRCDIR = ../bfd/libbfd.h
 
 
 # GDB "info" files, which should be included in their entirety


             reply	other threads:[~2002-12-27 19:31 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-27 11:56 Richard Dawe [this message]
2002-12-27 12:02 ` Daniel Jacobowitz
2002-12-27 16:17   ` Richard Dawe

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=E18S0BP-00010Q-00@phekda.freeserve.co.uk \
    --to=rich@phekda.freeserve.co.uk \
    --cc=gdb-patches@sources.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