From: Alan Modra <amodra@bigpond.net.au>
To: Ivan Guzvinec <ivang@opencores.org>
Cc: binutils@sources.redhat.com
Subject: Re: Makefile.in, Makefile.am problem
Date: Mon, 21 Jan 2002 02:49:00 -0000 [thread overview]
Message-ID: <20020121062528.GJ21859@bubble.sa.bigpond.net.au> (raw)
In-Reply-To: <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
next prev parent reply other threads:[~2002-01-21 6:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-19 11:18 Ivan Guzvinec
2002-01-21 2:49 ` Alan Modra [this message]
2002-01-22 11:06 ` Ivan Guzvinec
-- strict thread matches above, loose matches on Subject: below --
2002-01-23 9:10 Ivan Guzvinec
2002-01-23 16:46 ` Alan Modra
2002-01-18 8:47 Ivan Guzvinec
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=20020121062528.GJ21859@bubble.sa.bigpond.net.au \
--to=amodra@bigpond.net.au \
--cc=binutils@sources.redhat.com \
--cc=ivang@opencores.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).