From: "Ivan Guzvinec" <ivang@opencores.org>
To: <binutils@sources.redhat.com>
Subject: Re: Makefile.in, Makefile.am problem
Date: Wed, 23 Jan 2002 09:10:00 -0000 [thread overview]
Message-ID: <001501c1a41f$4a9191c0$0501010a@loki> (raw)
Alan Modra wrote:
> > 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.
I tried this procedure, but it does not solve my problem.
Can someone please explain ALL the steps needed to add new target to
binutils (or point me to a document that explains it). I would like to add
OR32 (OpenRisc1200) architecture support (aout, coff and elf32).
Maybe I'm doing something wrong in the above procedure. I want to point out
again that I'm new to these tools (make, automake, etc...) and more detailed
explanation is needed. I would like to hear from someone that has added an
architecture/target recently. It would save me a lot of time if I don't need
to chew through make,automake,... documentation first.
regards,
Ivan
next reply other threads:[~2002-01-23 15:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-23 9:10 Ivan Guzvinec [this message]
2002-01-23 16:46 ` Alan Modra
-- strict thread matches above, loose matches on Subject: below --
2002-01-19 11:18 Ivan Guzvinec
2002-01-21 2:49 ` Alan Modra
2002-01-22 11:06 ` Ivan Guzvinec
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='001501c1a41f$4a9191c0$0501010a@loki' \
--to=ivang@opencores.org \
--cc=binutils@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).