[Chicken-users] 4.8.0.5 compiled ... on message not quite correct

2013-10-30 Thread Matt Welland
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

Re: [Chicken-users] 4.8.0.5 compiled ... on message not quite correct

2013-10-30 Thread Mario Domenech Goulart
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)

Re: [Chicken-users] 4.8.0.5 compiled ... on message not quite correct

2013-10-30 Thread Jim Ursetto
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

Re: [Chicken-users] 4.8.0.5 compiled ... on message not quite correct

2013-10-30 Thread Jim Ursetto
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

Re: [Chicken-users] 4.8.0.5 compiled ... on message not quite correct

2013-10-30 Thread Jim Ursetto
I've changed the build process for stability so that release tarballs have their build tag made more generic and more accurate. This was the easiest workaround, I hope the wording is ok. There's no provision in the build for recording C compilation, just Scheme-C compilation. However, you