Re: [Chicken-users] unified bootstrap

[Brandon J. Van Every]

felix winkelmann wrote:
> On 9/4/06, Brandon J. Van Every <address@hidden> wrote:
> > >
> > > - Dependency on automake 1.9.6 isn't so good. I removed the check
> > >  for 1.9.6 and everything seems to work so far (using automake 1.8.3).
> >
> > Why not good?  You prefer bugs in old build systems?  We don't have to
> > follow the bleeding edge, but 1.8.x is rather old.  We should be using
> > whatever is most recent and readily packaged.  That should be 1.9.x if
> > not 1.9.6.  Realize, automake is only for people creating distros, i.e.
> > you, me.  It has no effect on the end user, other than possibly
> > producing a more reliable ./configure script.
>
> I don't care. That software-update race is annoying enough as it is.
> 1.8.3 works for me.

I went to do some research on how silly you are about not downloading a 
package.  :-)
I was surprised to find out that Automake 1.9 has some problems 
according to http://packages.debian.org/stable/devel/automake1.9
I have instated a requirement for Automake 1.8.3 in configure.in.  There 
should be a lower bound on what is expected.


> > > - csi.c should be distributed as well.
> >
> > Have you ever had a case of csi building but chicken not building?  If
> > that has happened, ok, I see your point.  If it has never happened, then
> > I don't see the point, as csi.c is readily built once chicken is built.
> > There isn't any silex in the build anymore, that's what csi used to be
> > needed for.  We could even distribute chicken-profile.c,
> > chicken-setup.c, etc. if you're really worried about it.  I mean, what's
> > special about csi.c compared to the others?
>
> csi.c, chicken-profile.c, chicken-setup.c and csc.c will have to be
> included in the distribution, since it simplifies cross-compilation.
> Please be so kind to change the make/build files accordingly.
Ok, distributing all of 'em makes more sense than distributing few of 
'em.  This is actually a substantial change to the build.  Previously, 
the system was designed to build the minimum requirements for Chicken, 
then use the built Chicken to do the rest.  So for tarballs, I'll need 
to put conditionals around the post-Chicken build rules, so that copies 
are used instead.  These changes are easy enough for me to do.  I'm just 
noting that it's a significant redesign, which is why it wasn't easy for 
you to do them yourself.  I'll have them done shortly.


Cheers,
Brandon Van Every