[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [avr-gcc-list] no avr/lib/avr25/attiny13a/Makefile.in

From: Ruud Vlaming
Subject: Re: [avr-gcc-list] no avr/lib/avr25/attiny13a/Makefile.in
Date: Sun, 1 Feb 2009 22:35:31 +0100
User-agent: KMail/1.9.1

On Sunday 01 February 2009 18:53, Weddington, Eric wrote:
> > -----Original Message-----
> > From: Ruud Vlaming [mailto:address@hidden 
> > Sent: Sunday, February 01, 2009 9:47 AM
> > To: Weddington, Eric; Joerg Wunsch; Anatoly Sokolov
> > Cc: address@hidden
> > Subject: Re: [avr-gcc-list] no avr/lib/avr25/attiny13a/Makefile.in
> > 
> > (To go one step further, would it not be possible to 
> > intergrate the steps the
> > bootstrap performs into configure?  We are back to the 
> > standard configure/make
> > procedure which everybody knows. I, for example, never 
> > bootstrapped before.)
> > 
> If you look at the top of the bootstrap script, you'll see a comment as to 
> why the bootstrap script is needed: # bootstrap script to build all the 
> *.in files and configure script. 
> When avr-libc is released, the configure script is pre-built and distributed 
> in the release. The bootstrap script is required for avr-libc *developers*, 
> who may change the *.in, or *.ac files and then rebuild the configure script. 

Yes, i read why it is needed, and for lib-c developers that is not a problem.
For users however, that just want to build the libc and move on it would be
better if it wouldn't (or was integrated in one script somehow)

So now we are again at the reason why i placed the first post of this
discussion. If you do not bootstrap, you miss one file. This issue was not
pressent on earlier versions, i never needed to bootstrap just to build.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]