[Chicken-janitors] #1444: Chicken will not build from tarball if contents are placed in version control and then retrieved

[Chicken Trac]

#1444: Chicken will not build from tarball if contents are placed in version
control and then retrieved
--------------------------+--------------------------------
 Reporter:  jrobbins      |                 Owner:
     Type:  defect        |                Status:  new
 Priority:  major         |             Milestone:  someday
Component:  build system  |               Version:  4.13.0
 Keywords:                |  Estimated difficulty:
--------------------------+--------------------------------
 In short, if you extract the contents of your most recent release tarball,
 place it in some sort of version control (SVN or Git will do), and pull
 down the contents of the version control, that pulled-down version of
 Chicken will fail to build, even if the non-version-controlled build will
 succeed.

 Attached is a script that can replicate the issue. I've tested it on
 several Ubuntu and Windows machines, and it happens on all of them
 (however, it did fail to cause an error on one Arch Linux machine I
 tested). The environment variable CHICKEN_PLATFORM controls what platform
 the script runs for (default is linux), and specifying the environment
 variable GIT will make it run with Git instead of SVN.

 There are no differences between a normal and version controlled chicken
 folder (at least diff reports nothing), but building causes utils.c to
 state that, in the buggy case, it is bootstrapping when it should in fact
 not be. The permissions do not change when taken from version control, and
 while modification/access times do change when taken from version control,
 setting the atime/mtime back to what they should be does nothing.

--
Ticket URL: <https://bugs.call-cc.org/ticket/1444>
CHICKEN Scheme <https://www.call-cc.org/>
CHICKEN Scheme is a compiler for the Scheme programming language.