Matt, Easiest way to fix this in the tarball is, prior to `make`:
echo "#define C_BUILD_TAG \"compiled $(date +%Y-%m-%d) on $(hostname)\"" > buildtag.h or echo '#define C_BUILD_TAG ""' > buildtag.h or whatever you want in that line. You can't currently remove or truncate that file to get an empty buildtag; you have to define C_BUILD_TAG to "". The code could be updated to accept a missing build tag (and/or to remove the resulting blank line); I can provide a patch if you like. Jim On Oct 30, 2013, at 3:11 PM, Jim Ursetto <zbignie...@gmail.com> wrote: > There was some noise on the list a few months ago in re changing the > compilation message to reflect where the .c to .o compile occurred. Not sure > if it went anywhere. > > I don't really care either way, it is basically cosmetic IMO. > >> On Oct 30, 2013, at 11:02, Mario Domenech Goulart <mario.goul...@gmail.com> >> wrote: >> >> Hi Matt, >> >>> On Wed, 30 Oct 2013 08:57:26 -0700 Matt Welland <estifo...@gmail.com> wrote: >>> >>> When I compiled 4.8.0.5 from the tar this morning I get a curious >>> message on starting csi: >>> >>>> csi >>> >>> CHICKEN >>> (c) 2008-2013, The Chicken Team >>> (c) 2000-2007, Felix L. Winkelmann >>> Version 4.8.0.5 (stability/4.8.0) (rev 5bd53ac) >>> linux-unix-gnu-x86-64 [ 64bit manyargs dload ptables ] >>> compiled 2013-10-03 on aeryn.xorinia.dim (Darwin) <==== Not true :) >> >> That's where the Scheme->C compilation took place. When you built the >> code from the release tarball, you actually only compiled the C code. >> >> Yes, the banner is a bit misleading. >> >> Best wishes. >> Mario >> -- >> http://parenteses.org/mario >> >> _______________________________________________ >> Chicken-users mailing list >> Chicken-users@nongnu.org >> https://lists.nongnu.org/mailman/listinfo/chicken-users _______________________________________________ Chicken-users mailing list Chicken-users@nongnu.org https://lists.nongnu.org/mailman/listinfo/chicken-users