From: Robert Cragie <rcc@jennic.com>
To: sid@sources.redhat.com
Subject: Patch to fix init_disassemble_info linking
Date: Sat, 08 May 2004 15:24:00 -0000 [thread overview]
Message-ID: <200405081156.25435.rcc@jennic.com> (raw)
This patch, along the lines of what Frank was suggesting, seems to fix the
build - not tried running it though. Note it looks like I am using a
newer version of automake.
? cvs.diff
Index: sid/component/cgen-cpu/Makefile.am
===================================================================
RCS file: /cvs/src/src/sid/component/cgen-cpu/Makefile.am,v
retrieving revision 1.8
diff -r1.8 Makefile.am
25,26c25,26
< libcgencpu_la_LIBADD = @cpu_libs@ $(INTLLIBS) $(LIBIBERTY) cgen-asm.lo
cgen-dis.lo cgen-opc.lo dis-buf.lo
< libcgencpu_la_DEPENDENCIES = @cpu_libs@ cgen-asm.lo cgen-dis.lo cgen-opc.lo
dis-buf.lo
---
> libcgencpu_la_LIBADD = @cpu_libs@ $(INTLLIBS) $(LIBIBERTY) cgen-asm.lo
cgen-dis.lo cgen-opc.lo dis-buf.lo dis-init.lo
> libcgencpu_la_DEPENDENCIES = @cpu_libs@ cgen-asm.lo cgen-dis.lo cgen-opc.lo
dis-buf.lo dis-init.lo
47a48,50
> /bin/sh ./libtool --mode=compile $(CC) $(OPCODES_COMPILE_FLAGS)
$(CFLAGS)
-c $<
>
> dis-init.lo: ../../../opcodes/dis-init.c
Index: sid/component/cgen-cpu/Makefile.in
===================================================================
RCS file: /cvs/src/src/sid/component/cgen-cpu/Makefile.in,v
retrieving revision 1.9
diff -r1.9 Makefile.in
1c1
< # Makefile.in generated automatically by automake 1.4-p5 from Makefile.am
---
> # Makefile.in generated automatically by automake 1.4-p6 from Makefile.am
115,116c115,116
< libcgencpu_la_LIBADD = @cpu_libs@ $(INTLLIBS) $(LIBIBERTY) cgen-asm.lo
cgen-dis.lo cgen-opc.lo dis-buf.lo
< libcgencpu_la_DEPENDENCIES = @cpu_libs@ cgen-asm.lo cgen-dis.lo cgen-opc.lo
dis-buf.lo
---
> libcgencpu_la_LIBADD = @cpu_libs@ $(INTLLIBS) $(LIBIBERTY) cgen-asm.lo
cgen-dis.lo cgen-opc.lo dis-buf.lo dis-init.lo
> libcgencpu_la_DEPENDENCIES = @cpu_libs@ cgen-asm.lo cgen-dis.lo cgen-opc.lo
dis-buf.lo dis-init.lo
118,126c118
< OPCODES_COMPILE_FLAGS = -DHAVE_CONFIG_H \
< -I../../../opcodes \
< -I../../../bfd \
< -I../../../intl \
< -I$(srcdir)/../../../opcodes \
< -I$(srcdir)/../../../include \
< -I$(srcdir)/../../../bfd \
< -I$(srcdir)/../../../intl \
< -D_GNU_SOURCE
---
> OPCODES_COMPILE_FLAGS =
-DHAVE_CONFIG_H -I../../../opcodes -I../../../bfd
-I../../../intl -I$(srcdir)/../../../opcodes -I$(srcdir)/../../../include
-I$(srcdir)/../../../bfd -I$(srcdir)/../../../intl -D_GNU_SOURCE
152c144
< aclocal.m4 config.in configure configure.in
---
> acinclude.m4 aclocal.m4 config.in configure configure.in
173c165
< $(ACLOCAL_M4): @MAINTAINER_MODE_TRUE@ configure.in
---
> $(ACLOCAL_M4): @MAINTAINER_MODE_TRUE@ configure.in acinclude.m4
580a573,575
> /bin/sh ./libtool --mode=compile $(CC) $(OPCODES_COMPILE_FLAGS)
$(CFLAGS)
-c $<
>
> dis-init.lo: ../../../opcodes/dis-init.c
next reply other threads:[~2004-05-08 15:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-08 15:24 Robert Cragie [this message]
2004-05-08 20:06 ` Frank Ch. Eigler
[not found] <000201c4366a$adbaa4a0$5514010a@telxsi.com>
2004-05-10 13:33 ` Robert Cragie
2004-05-10 17:14 ` Frank Ch. Eigler
2004-05-11 13:54 ` Robert Cragie
2004-05-14 7:45 ` Ashutosh
2004-05-14 8:37 ` Robert Cragie
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=200405081156.25435.rcc@jennic.com \
--to=rcc@jennic.com \
--cc=sid@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).