|
|
|
|
|
|
|
|
|
|
|
|
| home | help | back | first | fref | pref | prev | next | nref | lref | last | post |
Message-ID: <202011181853.0AIIr4Ww018647@hedwig.cmf.nrl.navy.mil> From: Ken Hornstein <kenh@cmf.nrl.navy.mil> To: krbdev@mit.edu In-Reply-To: <8736164ija.fsf@hope.eyrie.org> MIME-Version: 1.0 Date: Wed, 18 Nov 2020 13:53:04 -0500 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: krbdev-bounces@mit.edu >For the record, Debian (and thus Ubuntu, etc.) does not set the executable >bit on any shared libraries except for some weird special cases where the >library can also be invoked as an executable. Oh, interesting. So ... is this just a _packaging_ thing? It seems like the default toolchain on the systems I looked at end up setting the the execute bit during the link step, but I admit I don't know who's responsible for that, and if that wasn't the case on Debian then I'm mildly curious exactly who is deciding on the mode of that output file. I personally have no opinion on whether or not the execute bit SHOULD be set in general on shared libraries; it seems like there's valid arguments for both sides. My only point was that it seems like at least Linux systems that use RPM expect it to be there, but clearly that's not even a universal requirement across all Linux distributions. --Ken _______________________________________________ krbdev mailing list krbdev@mit.edu https://mailman.mit.edu/mailman/listinfo/krbdev
|
|
|
|
|
|
|
|
|
|
|
|
| home | help | back | first | fref | pref | prev | next | nref | lref | last | post |