>>>>> "Helmut" == Helmut Grohne <hel...@subdivi.de> writes:
Helmut> What is being disabled here is the generation of
Helmut> /usr/share/doc/libpam-doc/txt/draft-morgan-pam-current.txt.gz. This
Helmut> file is missing from the current libpam-doc package. Is that
Helmut> intentional?
No.
I had entirely missed this particular bit of pam trivia.
Helmut> adding Build-Conflicts: bison. If you'd rather have the
Helmut> file, I suggest adding Build-Depends-Indep: bison.
Is that sufficient?
You also talked about adding native:true for bison. But Is that sufficient?
Then don't I need to use a native flex and a native C compiler?
I don't really understand how all that works in meson, but it seems like
I'd need all native tools to build the spec.
I guess we only will consume the spec on the arch all build, and
there's no reason for arch all to ever cross build I can think of.
But it seems like we also need to make sure the arch cross builds
succeed.
I don't understand how adding build-indep on bison actually fixes the
problem. I agree it makes it less likely because it means I now need a
native bison in my build environment rather than a cross bison to
trigger things.
But if I just make bison (or byacc which is also supported) native,
won't I try to build using a cross flex, cross compiler and native
bison?
I don't understand how much of the compiler discovery and argument
detection I would need to replicate to build both cross and native tools.
I wonder if a simpler solution would be to only build the spec if we're
building docs.
So:
* add bison as build-indep
* Only build the spec if the docs feature is enabled.
