Rtems Rebuild Remake Question

[Ralf Corsepius]

Am Fre, 2002-03-08 um 15.25 schrieb Joel Sherrill:
> 
> 
> "Bill Butler(test)" wrote:
> > 
> > No I don't believe that the 5307 was ported over with 4.5.0, at least it
> > was not in the main distrubtion.. I had to modify it.. But I was having
> > trouble with the mcf5307elite, which was included.
> > 
> > But... I got it to work now.
> > 
> > I believe this is what I had to do to make it work. You know how things
> > go.. you try several things, and retry and finally it works.. Now what
> > was it that fixed it?
> > 
> > 1st. the Makefile.in is copied over on "make all" in the build directory
> > not on configure. I was unsure about this.
> 
> Maybe this is an English thing but I think Makefile.in's are strictly
> generated into the source tree by automake as part of bootstrap.
Exactly. Any Makefile.in inside of the build-directory is wrong.
  
> > 2nd. I had to touch the main Makefile.am in the root directory of the
> > BSP. 
This would indicate not to be using --enable-maintainer-mode.

> > I believe this is because the build looked at the bsp directory and
> > thought it was up to date (dependence problem?). By changing the Main
> > makefile, it re-ran it which in turn copied the lower
> > "start/Makefile.in" over from the src directory.
Another indication of not using --enable-maintainer-mode.

> I am wondering what really happened.  There is no dependey between the
> top level Makefile.am and any subdirectory's Makefile.am.
Right. There shouldn't be any.

The dependencies span between the config.status to generate a
Makefile.in and between the a Makefile.in and it's corresponding
Makefile.am.

>  It is
> possible
> that you tried to run bootstrap while in a directory without a
> configure.in
> script.  I don't recall what bootstrap does/says in that case but it
> won't
> generate any files.
I don't understand what you are trying to say.

Ralf