This is the mail archive of the
binutils@sources.redhat.com
mailing list for the binutils project.
Re: Makefile.in, Makefile.am problem
- From: Alan Modra <amodra at bigpond dot net dot au>
- To: Ivan Guzvinec <ivang at opencores dot org>
- Cc: binutils at sources dot redhat dot com
- Date: Mon, 21 Jan 2002 16:55:28 +1030
- Subject: Re: Makefile.in, Makefile.am problem
- References: <001d01c1a107$20b0df70$0501010a@loki>
On Sat, Jan 19, 2002 at 05:34:11PM +0100, Ivan Guzvinec wrote:
> Hi,
>
> I'm trying to merge our OR32 binutils with main distribution but I have
> a problem with MKDEP generated sections of Makefile.am/.in.
>
> (part of Makefile.in/.am that starts with)
> AMKDEP = #DO NOT PUT ANYTHING BETWEEN THIS LINE AND THE MATCHING WARNING
> BELOW.
> DEPTC_a29k_aout = $(INCDIR)/symcat.h $(srcdir)/config/obj-aout.h \
> $(srcdir)/config/tc-a29k.h $(BFDDIR)/libaout.h $(INCDIR)/bfdlink.h \
> $(INCDIR)/safe-ctype.h $(INCDIR)/opcode/a29k.h
> ...
> ...
> BMKDEP = #DO NOT PUT ANYTHING BETWEEN THIS LINE AND THE MATCHING WARNING
> ABOVE.
> (and ends here)
>
> Entries for the files that I have added are not generated. If I add them
> manualy they (as expected) are deleted when I try to build the sources.
>
> I am new to these tools (Automake, etc...) so I would ask if someone can
> please tell me how and when these sections of Makefile.am/.in are
> generated?
configure using --enable-64-bit-bfd --enable-targets=all, go to each of
bfd/, opcodes/, binutils/, gas/, gprof/ and ld/ in your build directory,
and run
make dep-am
After that, run automake in each of the corresponding source dirs.
--
Alan Modra
IBM OzLabs - Linux Technology Centre