Fair enough. That's totally fine for self-contained packages in which
you control the build parameters from end-to-end. This may become an
issue with skarnet libraries, such as utmps, that are used with other,
non-skarnet packages. Libutmps pulls in libskarnet and libskarnet
'pollutes' the other packages by making their stack executable.

 To make things perfectly clear: the modification I pushed to git also
applies to the ld invocations creating shared libraries, including
libskarnet.so. So with that change, skalibs or libutmps will not
pollute anything else. ;)


Reply via email to