Re: parse-datetime.c generated in the source (instead of build) directory

2018-03-19 Thread Bruno Haible
> Other source files are captured just fine. The only problem is that it > expects parse-datetime.{c,y} to be in build directories, instead of the > source directory. It could be confused by the #line directives that bison > produces. Indeed, that could be. OTOH, tools like bison and gperf shoul

Re: parse-datetime.c generated in the source (instead of build) directory

2018-03-19 Thread Kamil Dudka
On Saturday, March 17, 2018 1:37:24 AM CET Bruno Haible wrote: > Kamil Dudka wrote: > > parse-datetime.c generated out of parse-datetime.y ends up in the source > > directory, instead of the build directory as one would expect. This was > > introduced by the following commit: > > > > http://git.s

Re: parse-datetime.c generated in the source (instead of build) directory

2018-03-16 Thread Bruno Haible
Kamil Dudka wrote: > parse-datetime.c generated out of parse-datetime.y ends up in the source > directory, instead of the build directory as one would expect. This was > introduced by the following commit: > > http://git.savannah.gnu.org/gitweb/?p=gnulib.git;a=commitdiff;h=6c680191 > > Neither

Re: parse-datetime.c generated in the source (instead of build) directory

2018-03-16 Thread Paul Eggert
Kamil Dudka wrote: the build should work even if the source directory is on a read-only file system. That's the first I've heard of that constraint, at least for the case where one is building from the Git repository. (The problem you describe should not occur when building from a distributio

Re: parse-datetime.c generated in the source (instead of build) directory

2018-03-16 Thread Vivien Kraus
Sorry, I have just checked and automake does not distribute the generated source by default, thus the modified .y.c rule is required. Le vendredi 16 mars 2018 à 19:09 +0100, Vivien Kraus a écrit : > Hello, > > Distributing the generated sources is the default behaviour to expect > from automake;

Re: parse-datetime.c generated in the source (instead of build) directory

2018-03-16 Thread Vivien Kraus
Hello, Distributing the generated sources is the default behaviour to expect from automake; I don't really understand why it is needed to override the .y.c rule... This behaviour permits you to configure, build, install, check... the package without having bison installed. Since the generated .c

parse-datetime.c generated in the source (instead of build) directory

2018-03-16 Thread Kamil Dudka
parse-datetime.c generated out of parse-datetime.y ends up in the source directory, instead of the build directory as one would expect. This was introduced by the following commit: http://git.savannah.gnu.org/gitweb/?p=gnulib.git;a=commitdiff;h=6c680191 Neither the comment, nor the change log