diff options
| author | Winter <winter@winter.cafe> | 2023-01-30 21:07:07 -0500 |
|---|---|---|
| committer | Winter <winter@winter.cafe> | 2023-01-30 21:13:05 -0500 |
| commit | ede7b1d98a01cd25c05f30c215afc063bd62706b (patch) | |
| tree | 15b3af946edb0859f7dbec8455b19b641658409c /pkgs/development/python-modules/rangehttpserver | |
| parent | 63f869f5ff10b570fcf3a0d002a7aa25938f6f9f (diff) | |
Revert "rustc: add note about libiconv dependency"
This reverts commit edfbbaf28258d968de64b364d4a0868a80cdf1c2.
I mistakingly believed that once 1.66.0 was used to bootstrap, we'd be
able to remove libiconv from rustc's build-time dependency tree on Darwin.
Sadly, this isn't the case, because src/tools/bootstrap depends on libc.
Additionally, it seems that my assessment in b1834a461edf7abf4a6fb89db0ed65904a48a01c
was wrong -- *any* dependency on `libc` will cause a requirement on
libiconv, due to rustc unconditionally linking every library specified
in `link` directives, no matter if the function is actually used.
This was worked around somewhat in https://github.com/rust-lang/libc/pull/2944
by not linking libiconv if libc is only a dependency of std, but this
doesn't apply when `libc` is a dependency of anything else.
Maybe one day we'll just rip out libiconv from `libc` entirely (or hide it
behind a feature flag), but for now, we can just keep it in `buildRustPackage`'s
`buildInputs` by default.
Diffstat (limited to 'pkgs/development/python-modules/rangehttpserver')
0 files changed, 0 insertions, 0 deletions
