Hi Sven, On Sun, Apr 11, 2021 at 08:51:24PM +0200, Sven Joachim wrote: > That is a result of me complaining about these flags when they were > introduced, see > https://lists.gnu.org/archive/html/bug-ncurses/2019-10/msg00037.html.
That seems quite wise in retrospect. :) > > So actually fixing this would be possible by fixing the generated > > /usr/bin/ncurses6-config to not contain them. The filtering can either > > happen inside the configure script or applied post build in a > > Debian-specific fixup. > > Another option might be to patch misc/ncurses-config.in and remove > @LDFLAGS@ there. That depends on the purpose of @LDFLAGS@ there. It would very likely work on Debian, but I am unsure whether it would break elsewhere. So maybe doing so is not acceptable upstream. I suppose that you do want to minimize the difference to upstream. On the Debian side, I do agree here as @LDFLAGS@ only contain the dpkg-buildflags, which we do not want to forward. So patching it locally sounds like a sane plan B to me. If @LDFLAGS@ has a purpose for other distributions, I guess the best trade-off is filtering it during configure. Helmut
