This is the mail archive of the
binutils@sources.redhat.com
mailing list for the binutils project.
Re: Makefile.in, Makefile.am problem
- From: "Ivan Guzvinec" <ivang at opencores dot org>
- To: <binutils at sources dot redhat dot com>
- Date: Wed, 23 Jan 2002 16:04:40 +0100
- Subject: Re: Makefile.in, Makefile.am problem
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