Re: more timestamp problems

[Dima K. <gn...@di...>]

sfeam via gnuplot-beta <gnu...@li...> writes:

> Shige Takeno points out (Bug #2016) that ./prepare; ./configure; make
> is currently not working if you start with a git snapshot downloaded
> from SourceForge.   That's because the snapshot is a *.zip file that
> doesn't include the git metadata, so the attempt to create
> timestamp.h by querying git cannot work.
>
> I wonder if we have control over the script on sf.net that creates
> a snapshot?   Maybe that script could generate timestamp.h on the fly?
>
> Another possibility is to assume that anyone downloading a snapshot
> will unpack it immediately, in which case the timestamp can be the
> creation date of the top level source directory.

I want to say we're doing something we shouldn't be doing, but I can't
quite figure out what's happening. The bug report is here:
https://sourceforge.net/p/gnuplot/bugs/2016/

The reporter says he sees this barf:

  cut: ../.git/HEAD: No such file or directory
  make: *** No rule to make target ../.git/', needed bytimestamp.h'. Stop.

The timestamp.h rule I see is this:

  timestamp.h: $(top_srcdir)/ChangeLog Makefile
          @echo Making $@
          @echo "#ifndef GNUPLOT_TIMEBASE_H_INCLUDED" >$@t
          @echo "#define GNUPLOT_TIMEBASE_H_INCLUDED" >>$@t
          @head -1 $< | sed -e 's,\(^[0-9-]* \).*$$,const char gnuplot_date[] = "\1";,' >>$@t
          @echo "#endif /* GNUPLOT_TIMEBASE_H_INCLUDED */" >> $@t
          @if cmp -s $@ $@t; then rm -f $@t; else mv $@t $@; fi

What is invoking cut and touching git? I don't see it.