From: Manoj Iyer <manjo@austin.ibm.com>
To: gdb-patches@sources.redhat.com
Subject: [RFC] Rearranging the build order fix link problem in tmp-ld-insn
Date: Thu, 21 Apr 2005 19:20:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.58.0504211414560.942@lazy> (raw)
When compiling/linking tmp-ld-insn, the linker exits with the error
message, cc -g -O -I. -I. -I./../../include -I../../bfd -I./../../bfd
-I../../gdb -I./../../gdb -I./../../gdb/config -o tmp-ld-insn -DMAIN
./ld-insn.c ld-cache.o misc.o lf.o table.o ld-decode.o filter_host.o
filter.o
cc: 1501-228 input file ld-cache.o not found
cc: 1501-228 input file ld-decode.o not found
Rearranging the build order fixes this build break. Here is the patch.
Please review and ok to commit.
=========================================================================
2005-04-21 Manoj Iyer <manjo@austin.ibm.com>
* Rearranging the build order in sim/ppc/Makefile.in to fix build
break reported by AIX linker.
--- ./src/sim/ppc/Makefile.in 2005-01-03 09:34:19.000000000 -0600
+++ ./new/src/sim/ppc/Makefile.in 2005-04-21 14:12:56.000000000 -0500
@@ -683,7 +683,7 @@ tmp-dgen: dgen ppc-spr-table $(srcdir)/.
$(SHELL) $(srcdir)/../../move-if-change tmp-spreg.c spreg.c
touch tmp-dgen
-tmp-igen: igen $(srcdir)/ppc-instructions $(srcdir)/altivec.igen $(srcdir)/e500.igen $(IGEN_OPCODE_RULES) $(srcdir)/../../move-if-change tmp-ld-decode tmp-ld-cache tmp-ld-insn tmp-filter
+tmp-igen: igen $(srcdir)/ppc-instructions $(srcdir)/altivec.igen $(srcdir)/e500.igen $(IGEN_OPCODE_RULES) $(srcdir)/../../move-if-change tmp-ld-insn tmp-ld-decode tmp-ld-cache tmp-filter
./igen $(IGEN_FLAGS) \
-o $(srcdir)/$(IGEN_OPCODE_RULES) \
-I $(srcdir) -i $(srcdir)/ppc-instructions \
Thanks
-----
manjo
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
+ Cogito ergo sum +
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
next reply other threads:[~2005-04-21 19:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-21 19:20 Manoj Iyer [this message]
2005-04-21 19:22 ` Daniel Jacobowitz
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.58.0504211414560.942@lazy \
--to=manjo@austin.ibm.com \
--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