nixpkgs/pkgs/development/interpreters/python/cpython/2.7
Will Dietz b11f3bc8e3 cpython: don't use lchmod() on Linux, fix w/musl
upstream issue:
https://bugs.python.org/issue31940

There are two PR's proposed to fix this,
but both seem to be stalling waiting for review.

I previously used what appears to be the favored
of the two approaches[1] to fix this,
with plan of keeping it musl-only until PR was merged.

However, while writing up a commit message
explaining the problem and why it needed fixing...

I investigated a bit and found it increasingly
hard to justify anything other than ...
simply not using lchmod.

Here's what I found:
* lchmod is non-POSIX, seems BSD-only these days
* Functionality of lchmod isn't supported on Linux
  * best scenario on Linux would be an error
* POSIX does provide lchmod-esque functionality
  with fchmodat(), which AFAICT is generally preferred.
* Python intentionally overlooks fchmodat()[2]
  electing instead to use lchmod() behavior
  as a proxy for whether fchmodat() "works".
  I'm not sure I follow their reasoning...
* both glibc and musl provide lchmod impls:
  * glibc returns ENOSYS "not implemented"
  * musl implements lchmod with fchmodat(),
    and so returns EOPNOTSUPP "op not supported"
* Python doesn't expect EOPNOTSUPP from lchmod,
  since it's not valid on BSD's lchmod.
* "configure" doesn't actually check lchmod usefully,
  instead checks for glibc preprocessor defines
  to indicate if the function is just a stub[3];
  somewhat fittingly, if the magic macros are defined
  then the next line of the C source is "choke me",
  causing the compiler to trip, fall, and point
  a finger at whatever is near where it ends up.
  (somewhat amusing, but AFAIK effective way to get an error :P)

I'm leaving out links to threads on mailing lists and such,
but for now I hope I've convinced you
(or to those reading commit history: explained my reasons)
that this is a bit of a mess[4].

And so instead of making a big mess messier,
and with hopes of never thinking about this again,
I propose we simply tell Python "don't use lchmod" on Linux.

[1] https://github.com/python/cpython/pull/4783
[2] 28453feaa8/Lib/os.py (L144)
[3] 28453feaa8/configure (L2198)
[4] Messes happen, no good intention goes unpunished :).
2018-04-25 21:46:13 -05:00
..
2.5.2-ctypes-util-find_library.patch
2.5.2-tkinter-x11.patch
2.6.2-ssl-threads.patch
2.6.5-export-PySignal_SetWakeupFd.patch
2.6.5-FD_SETSIZE.patch
2.6.5-ncurses-abi6.patch
2.7.3-dbm.patch
2.7.3-dylib.patch
2.7.3-getpath-exe-extension.patch
2.7.3-no-libm.patch
boot.nix pkgs: refactor needless quoting of homepage meta attribute (#27809) 2017-08-01 22:03:30 +02:00
default.nix cpython: don't use lchmod() on Linux, fix w/musl 2018-04-25 21:46:13 -05:00
deterministic-build.patch
nix-store-mtime.patch
no-ldconfig.patch python27: 2.7.12 -> 2.7.13 2016-12-24 16:00:31 +01:00
properly-detect-curses.patch
python-2.7-distutils-C++.patch python: add C++ compiler support for distutils 2016-10-17 11:23:13 -04:00
search-path.patch
use-correct-tcl-tk-on-darwin.patch pythonPackages.tkinter: fix darwin build 2018-03-18 22:28:46 +01:00