id,summary,reporter,owner,description,type,status,priority,milestone,component,version,resolution,keywords,cc,blockedby,blocking,branch_state,votes 2692,Date not set properly in manpage,egmont,slavazanko,"After installing mc-4.8.1 the footer of the manpage says: MC Version 4.8.1 @DATE_OF_MAN_PAGE@ MC(1) Running just the configure script (and no make) already generates mc.1 from mc.1.in (and similarly for all other manpages) and substitutes all the varibables (like version number, path prefixes) except for the date. Running make in that directory would substitute the version number too, but the target file is already more recent than the source, so this step is not executed. If you remove mc.1 or touch it back in time, then a make generates mc.1 with a proper date. I don't know what the desired solution would be, but it seems currently that configure and make are working against each other, they both try to do the same thing (and do it differently). It should be the responsibility of one of them to generate the manpages from the corresponding *.in files. Also note (moving here from ticket #2689) that the code that updates the date in the manpage uses ""stat -c"" and ""date -d"", both are apparently GNU/Linux stuff, not supported on Mac or probably on *BSD. As a partial solution, maybe the best solution would be to substitute the version number and date when the dist tarball is created (as part of running autoconf/automake), so the user gets these ready. This way creating a tarball or compiling from git probably still wouldn't work on Mac, but at least compiling a tarball would go fine. (I'm wondering, I don't know: is there a best practice for this in other free software?) I'll try to find the proper cross-OS command to print the timestamp of a file.",defect,closed,major,4.8.3,mc-core,4.8.1,fixed,,,,,merged,committed-master committed-stable