[gambit-list] Automatic build system for Gambit

Marc Feeley feeley at iro.umontreal.ca
Tue Mar 29 17:47:46 EDT 2011

The sources in the git repo are sufficient to build Gambit from scratch.  I think the problem you are experiencing is that when you do a "git pull" the modification date of the .scm files is more recent than the corresponding .c file.  So "make" thinks the .scm files have been modified since the last compilation by gsc-comp (to compile .scm -> .c).

Could you check if a

   touch */*.c


By the way, it would be really nice to have an automatic build of Gambit on different systems (RPM, MacPorts, CYGWIN, etc).  Is that something you want to do, or just for your own purposes?


On 2011-03-29, at 3:30 PM, Paul Wolneykien wrote:

>  Hi,
>  I'm thinking of a semi-automatic system for building new releases of
> Gambit tracking the main Git repository at
> http://www.iro.umontreal.ca/~gambit/repo/gambit.git . I suppose the
> process as follows: when a new release tag is published, the procedure
> updates the local branch and build a new version of the Gambit, possibly
> with the help of a previously built one.
>  The main problem with that is that I can't see a way to provide a
> consequently updated build environment as stated in
> http://dynamo.iro.umontreal.ca/~gambit/wiki/index.php/Contributing_Patches_to_Gambit_Source_Code.
> The only thing that can be consequently updated is the clean local
> source tree (with no generated files) as it published at the main Git
> repository. That's because each build is handled in a separate
> environment constructing from scratch. However, the result of a previous
> build is available in the form of RPM package. So I've tried to use a
> previous version of Gambit (4.5.3) to build the fresh release (4.6.0)
> linking /usr/bin/gsc to gsc-comp in the source tree root: both `make
> bootstrap' and `make' finished with an error message about gsc version
> incompatibility.
>  Dear community, is it generally possible to build Gambit:
>  a) having only the sources published at the main Git repository?
>  b) having only a) and a previous version of Gambit installed?
>  If not, is the *-devel tarball is absolutely necessary to build
> Gambit? And if so, can it be prepared from the main Git repository?
>  Best regards,
>  Paul.
> _______________________________________________
> Gambit-list mailing list
> Gambit-list at iro.umontreal.ca
> https://webmail.iro.umontreal.ca/mailman/listinfo/gambit-list

More information about the Gambit-list mailing list