Rtems Rebuild Remake Question

[Bill Butler(test)]

I am not saying that there was a Makefile.in in the build tree. I
explained more in detail  what I was doing the first time I wrote about
this so I skipped some steps this time.. sorry for the confusion.

(In the Src tree )

1)touch Makefile.am 
2) ../../../../../../bootstrap (tried running in BSP SRC directory and
m68k SRC dir)
3) This does create an updated Makefile.in in the SRC directory.

(Build tree side)
4) configure --target=m68k-rtems --enable-rtemsbsp="<BSP>"
--prefix=/opt/m68k-rtems
5) make all
6) makefile.in (from the SRC tree) is then used to create a Makefile in
the build tree. Right? When I said "copied over", this is what I was
trying to state. Sorry for the attempted shortcut.

Problem:
Steps 1-5 are working fine.
Step 6 is not happening

If I run bootstrap (../../../../../bootstrap ) in the BSP directory on
the SCR tree side, and then steps 4 and steps 5 ,the results is that
step 6 does not happen !

Update: I did get it to work (step 6) when I do a bootstrap in the root
SRC directory (/tools/rtems-ss-2002.../) shouldn't it work if you run
bootstrap in the BSP directory only?

About --enable-maintainer-mode. I was under the impression that this
would
Automatically run bootstrap on a configure. But if you did boot strap
manually you did not need it..  I am not using --enable-maintainer-mode
currently because someone stated it was not working for all BSP. I'm I
incorrect?

Ah well I will test the local bootstrap method with
-enable-maintainer-mode on and see if that changes anything.

Sorry for all the confusion.



Bill Butler
AIPCom Inc
972-644-2328 x16
bbill at tnex.com
 

-----Original Message-----
From: Ralf Corsepius [mailto:corsepiu at faw.uni-ulm.de] 
Sent: Friday, March 08, 2002 9:17 AM
To: Joel Sherrill
Cc: Bill Butler(test); 'Ian Caddy'; 'RTEMS Users'
Subject: Re: Rtems Rebuild Remake Question

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