I suggest that we end the discussion here. It's much easier to simply try cross building grdesktop than it is to argue what is going on.
Turns out, grdesktop does find the right pkg-config despite shipping the outdated macro in aclocal.m4. Yavor's closure is correct. On Sat, Nov 17, 2018 at 12:57:25AM +0200, Yavor Doganov wrote: > No, in this particular case he is not right; you are both confusing > two different use cases that have different (documented) behavior. > The --force option causes the output file (aclocal.m4) to be generated > always. If the package is not shipping the third-party macro (as is > the case with grdesktop -- it is not shipping pkg.m4), --force will > always recreate aclocal.m4 using the macro definition as found in > aclocal's search path (or autoreconf will fail if it cannot find it). > > IOW, it is not necessary to patch aclocal.m4 as it is always going to > be regenerated by dh_autoreconf. Thank you for the detailed explanation. Today I learned something. In particular, it'll result in me differentiating where macros are stored and trying to send autoreconf patches for similar issues. Old ones include #894039 #912837 #900433 and #900864. I wonder how many of them get solved by autoreconfing with --force. Helmut
