From: "Joseph S. Myers" <joseph@codesourcery.com>
To: binutils@gcc.gnu.org
Subject: Patch to add objdump to TOOL_PROGS
Date: Fri, 18 Feb 2005 00:02:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.61.0502172049260.29995@digraph.polyomino.org.uk> (raw)
This patch adds objdump to TOOL_PROGS so a link to it gets installed
in tooldir.
A case where this is of use is building and testing GCC on
hppa64-hpux, where tooldir followed by bindir are at the start of the
PATH with both 32-bit and 64-bit binutils installed under the same
prefix; objdump in bindir is 32-bit HPPA (SOM) objdump and the 64-bit
objdump is bindir/hppa64-hp-hpux11.xx-objdump. The GCC testsuite
expects to find objdump (not target-objdump) in the PATH, if not
building binutils in a unified tree, in order to identify the object
file format, so it finds the SOM objdump which fails to identify the
64-bit file format as ELF. Having a link to objdump in tooldir solves
this problem.
Tested on i686-pc-linux-gnu. OK to commit?
--
Joseph S. Myers
joseph@codesourcery.com
2005-02-17 Joseph S. Myers <joseph@codesourcery.com>
* Makefile.am (TOOL_PROGS): Add objdump.
* Makefile.in: Regenerate.
diff -rupN binutils.orig/Makefile.am binutils/Makefile.am
--- binutils.orig/Makefile.am 2004-12-01 10:54:51.000000000 +0000
+++ binutils/Makefile.am 2005-02-17 20:35:23.000000000 +0000
@@ -63,7 +63,7 @@ noinst_PROGRAMS = $(NM_PROG) $(STRIP_PRO
EXTRA_PROGRAMS = $(NLMCONV_PROG) srconv sysdump coffdump $(DLLTOOL_PROG) $(WINDRES_PROG) $(DLLWRAP_PROG)
# Stuff that goes in tooldir/ if appropriate.
-TOOL_PROGS = nm-new strip-new ar ranlib dlltool
+TOOL_PROGS = nm-new strip-new ar ranlib dlltool objdump
BASEDIR = $(srcdir)/..
BFDDIR = $(BASEDIR)/bfd
diff -rupN binutils.orig/Makefile.in binutils/Makefile.in
--- binutils.orig/Makefile.in 2004-12-01 10:54:51.000000000 +0000
+++ binutils/Makefile.in 2005-02-17 20:35:39.000000000 +0000
@@ -184,7 +184,7 @@ noinst_PROGRAMS = $(NM_PROG) $(STRIP_PRO
EXTRA_PROGRAMS = $(NLMCONV_PROG) srconv sysdump coffdump $(DLLTOOL_PROG) $(WINDRES_PROG) $(DLLWRAP_PROG)
# Stuff that goes in tooldir/ if appropriate.
-TOOL_PROGS = nm-new strip-new ar ranlib dlltool
+TOOL_PROGS = nm-new strip-new ar ranlib dlltool objdump
BASEDIR = $(srcdir)/..
BFDDIR = $(BASEDIR)/bfd
next reply other threads:[~2005-02-17 20:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-18 0:02 Joseph S. Myers [this message]
2005-02-18 3:15 ` Alan Modra
2005-02-18 10:57 ` Joseph S. Myers
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=Pine.LNX.4.61.0502172049260.29995@digraph.polyomino.org.uk \
--to=joseph@codesourcery.com \
--cc=binutils@gcc.gnu.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).