On 14.04.2017 18:33, Uli Schlachter wrote:

> configure already generates this. No idea what "complaining", "extra
> preparations", nor "special commands" you mean. (Well, ok, perhaps the
> empty files: This just

Yeah, that was the missing point. turned out that just creating them
in the corresponding hook rule was trivial. Not nice, but i can
live with that.

> So it seems that this needs configure to run. As a side effect this
> generates the proper files. Then you need to run automake again so that
> the proper Makefile.in is created. Which means you need to run configure
> again...

Uuuh, i didn't expect that.

Could it be that it's magically doing that on its own ?
I wonder, because I successfully built it via pbuilder/debuild (but not
tested) yet - with my drm queue applied - and the new symbols appeared.
If it wouldn't work in one pass, then at least the backends should be
missing (if it compiles at all).

>> Therefore, these files *really* should always be autogenerated and
>> strictly kept out of the src tree / tarball.
>
> They are autogenerated. "make dist" adds it to tarballs since the file
> is included by something.

I dont think the tarball should contain any autogenerated stuff.
That brings the risk that not everything's regenerated, if some patches
applied (especially ugly for distros/packaging). Fortunately it's not
in the git repo (otherwise git-buildpackage would break).


--mtx