treewide: Get rid of cc.gcc
#91293
Merged
treewide: Get rid of cc.gcc
#91293
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
10 tasks
Ericson2314
changed the title
cc.gcccc.gcc
Ericson2314
force-pushed
the
cxx-wrapper-debt-part-2
branch
2 times, most recently
from
ad418c0 to
4228bc9
Compare
ofborg
bot
requested review from
Lucus16,
Synthetica9,
davidtwco,
dtzWill,
peti and
veprbl
ofborg
bot
added
10.rebuild-darwin: 501+
Member
Author
|
Oh nice, the eval problems just went away! |
Ericson2314
force-pushed
the
cxx-wrapper-debt-part-2
branch
2 times, most recently
from
aabadf1 to
0b0dcd3
Compare
ofborg
bot
added
10.rebuild-darwin: 1-10
Instead, we have a new `gccForLibs`, which has the appropriate definition for e.g. avoiding `x86_32` linking problems.
Ericson2314
force-pushed
the
cxx-wrapper-debt-part-2
branch
from
0b0dcd3 to
92f96f4
Compare
Ericson2314
changed the title
cc.gcccc.gcc
Member
Author
|
OK ofborg passes, and manually tested some obscure things like wasi zlib. |
worldofpeace
added a commit
to worldofpeace/nixpkgs
that referenced
this pull request
Aug 30, 2020
Ughhhh this was terrible but it seems to now be fixed by [0]. Though it doesn't seem the issue is entirely resolved NixOS#36947. [0]: NixOS#91293
10 tasks
Contributor
|
@Ericson2314 Hey, I think this broke the "aarch64-android-prebuilt" pkgs. Just try with: |
Member
Author
|
@bkchr Can you reproduce this without |
Contributor
|
When I use without But you can also use |
Member
and should be equivalent. @bkchr Could you include the logs / derivation it fails at? I bet it's having trouble with the Android toolchain? |
Contributor
|
Member
Author
|
Oh this isn't an eval error, which I what I was seeing. |
Member
Author
|
Ah, it's because it's trying to use nix-built gcc via |
ggreif
added a commit
to ggreif/nixpkgs
that referenced
this pull request
Oct 15, 2020
primeos
pushed a commit
to primeos/nixpkgs
that referenced
this pull request
Nov 4, 2020
(cherry picked from commit 7a30df9)
10 tasks
rvem
pushed a commit
to serokell/nixpkgs
that referenced
this pull request
Nov 8, 2022
(cherry picked from commit 7a30df9)
PetarKirov
added a commit
to PetarKirov/dlang.nix
that referenced
this pull request
Apr 21, 2023
…so.1`
After upgrading to a recent version of Nixpkgs (2023-04-18), the build broke
with the following error:
...
auto-patchelf: 6 dependencies could not be satisfied
error: auto-patchelf could not satisfy dependency libgcc_s.so.1 wanted by
/nix/store/kl8bjrlmlzcjz47c0n6kjsj1yxi6zpqm-dmd-binary-2.098.0/lib/libphobos2.so.0.98.0
error: auto-patchelf could not satisfy dependency libgcc_s.so.1 wanted by
/nix/store/kl8bjrlmlzcjz47c0n6kjsj1yxi6zpqm-dmd-binary-2.098.0/bin/rdmd
error: auto-patchelf could not satisfy dependency libgcc_s.so.1 wanted by
/nix/store/kl8bjrlmlzcjz47c0n6kjsj1yxi6zpqm-dmd-binary-2.098.0/bin/dub
error: auto-patchelf could not satisfy dependency libgcc_s.so.1 wanted by
/nix/store/kl8bjrlmlzcjz47c0n6kjsj1yxi6zpqm-dmd-binary-2.098.0/bin/dustmite
error: auto-patchelf could not satisfy dependency libgcc_s.so.1 wanted by
/nix/store/kl8bjrlmlzcjz47c0n6kjsj1yxi6zpqm-dmd-binary-2.098.0/bin/ddemangle
error: auto-patchelf could not satisfy dependency libgcc_s.so.1 wanted by
/nix/store/kl8bjrlmlzcjz47c0n6kjsj1yxi6zpqm-dmd-binary-2.098.0/bin/dmd
auto-patchelf failed to find all the required dependencies.
...
After investigation, it turned out that the cuase was a recent [change in
Nixpkgs][0] after which `libgcc_s.so` is no longer part of the `glibc` package:
Before (nixpkgs @ 2022-03-30):
> nix build --json 'github:NixOS/nixpkgs/710fed5a2483f945b14f4a58af2cd3676b42d8c8#glibc^out' \
| jq -r '.[0].outputs.out' \
| xargs -I{} find {} \( -type l -or -type f \) -name '*libgcc_s*'
/nix/store/q29bwjibv9gi9n86203s38n0577w09sx-glibc-2.33-117/lib/libgcc_s.so.1
/nix/store/q29bwjibv9gi9n86203s38n0577w09sx-glibc-2.33-117/lib/libgcc_s.so
After (nixpkgs @ 2023-04-18):
> nix build --json 'github:NixOS/nixpkgs/555daa9d339b3df75e58ee558a4fec98ea92521e#glibc^out' \
| jq -r '.[0].outputs.out' \
| xargs -I{} find {} \( -type l -or -type f \) -name '*libgcc_s*'
(no output)
Instead, we should use `gccForLibs.libgcc` as it includes exactly what we need:
> nix build --json 'github:NixOS/nixpkgs/555daa9d339b3df75e58ee558a4fec98ea92521e#gccForLibs^libgcc' \
| jq -r '.[0].outputs.libgcc' \
| xargs -I{} find {} \( -type l -or -type f \) -name '*libgcc_s*'
/nix/store/5w5qpm9z3iyib615pdih6nvk9spv3jbv-gcc-12.2.0-libgcc/lib/libgcc_s.so.1
/nix/store/5w5qpm9z3iyib615pdih6nvk9spv3jbv-gcc-12.2.0-libgcc/lib/libgcc_s.so
This is nixpkgs again @ 2023-04-18, this time using `gccForLibs.libgcc`
instead of `glibc.out`.
[`gccForLibs`][1] is essentially `gcc.lib`:
* an alias to `stdenv.cc.cc` if the host and target are the same and are GNU or
* an alias to `gcc.cc` when `stdenv` is LLVM based as then `stdenv.cc.cc` would
refer to clang and the `lib` output point to libclang libs, which are very
different from what we need.
[0]: NixOS/nixpkgs#209870
[1]: NixOS/nixpkgs#91293
PetarKirov
added a commit
to PetarKirov/dlang.nix
that referenced
this pull request
Apr 21, 2023
…so.1`
After upgrading to a recent version of Nixpkgs (2023-04-18), the build broke
with the following error:
...
auto-patchelf: 6 dependencies could not be satisfied
error: auto-patchelf could not satisfy dependency libgcc_s.so.1 wanted by
/nix/store/kl8bjrlmlzcjz47c0n6kjsj1yxi6zpqm-dmd-binary-2.098.0/lib/libphobos2.so.0.98.0
error: auto-patchelf could not satisfy dependency libgcc_s.so.1 wanted by
/nix/store/kl8bjrlmlzcjz47c0n6kjsj1yxi6zpqm-dmd-binary-2.098.0/bin/rdmd
error: auto-patchelf could not satisfy dependency libgcc_s.so.1 wanted by
/nix/store/kl8bjrlmlzcjz47c0n6kjsj1yxi6zpqm-dmd-binary-2.098.0/bin/dub
error: auto-patchelf could not satisfy dependency libgcc_s.so.1 wanted by
/nix/store/kl8bjrlmlzcjz47c0n6kjsj1yxi6zpqm-dmd-binary-2.098.0/bin/dustmite
error: auto-patchelf could not satisfy dependency libgcc_s.so.1 wanted by
/nix/store/kl8bjrlmlzcjz47c0n6kjsj1yxi6zpqm-dmd-binary-2.098.0/bin/ddemangle
error: auto-patchelf could not satisfy dependency libgcc_s.so.1 wanted by
/nix/store/kl8bjrlmlzcjz47c0n6kjsj1yxi6zpqm-dmd-binary-2.098.0/bin/dmd
auto-patchelf failed to find all the required dependencies.
...
After investigation, it turned out that the cuase was a recent [change in
Nixpkgs][0] after which `libgcc_s.so` is no longer part of the `glibc` package:
Before (nixpkgs @ 2022-03-30):
> nix build --json 'github:NixOS/nixpkgs/710fed5a2483f945b14f4a58af2cd3676b42d8c8#glibc^out' \
| jq -r '.[0].outputs.out' \
| xargs -I{} find {} \( -type l -or -type f \) -name '*libgcc_s*'
/nix/store/q29bwjibv9gi9n86203s38n0577w09sx-glibc-2.33-117/lib/libgcc_s.so.1
/nix/store/q29bwjibv9gi9n86203s38n0577w09sx-glibc-2.33-117/lib/libgcc_s.so
After (nixpkgs @ 2023-04-18):
> nix build --json 'github:NixOS/nixpkgs/555daa9d339b3df75e58ee558a4fec98ea92521e#glibc^out' \
| jq -r '.[0].outputs.out' \
| xargs -I{} find {} \( -type l -or -type f \) -name '*libgcc_s*'
(no output)
Instead, we should use `gccForLibs.libgcc` as it includes exactly what we need:
> nix build --json 'github:NixOS/nixpkgs/555daa9d339b3df75e58ee558a4fec98ea92521e#gccForLibs^libgcc' \
| jq -r '.[0].outputs.libgcc' \
| xargs -I{} find {} \( -type l -or -type f \) -name '*libgcc_s*'
/nix/store/5w5qpm9z3iyib615pdih6nvk9spv3jbv-gcc-12.2.0-libgcc/lib/libgcc_s.so.1
/nix/store/5w5qpm9z3iyib615pdih6nvk9spv3jbv-gcc-12.2.0-libgcc/lib/libgcc_s.so
This is nixpkgs again @ 2023-04-18, this time using `gccForLibs.libgcc`
instead of `glibc.out`.
[`gccForLibs`][1] is essentially `gcc.lib`:
* an alias to `stdenv.cc.cc` if the host and target are the same and are GNU or
* an alias to `gcc.cc` when `stdenv` is LLVM based as then `stdenv.cc.cc` would
refer to clang and the `lib` output point to libclang libs, which are very
different from what we need.
[0]: NixOS/nixpkgs#209870
[1]: NixOS/nixpkgs#91293
PetarKirov
added a commit
to PetarKirov/dlang.nix
that referenced
this pull request
Apr 21, 2023
…so.1`
After upgrading to a recent version of Nixpkgs (2023-04-18), the build broke
with the following error:
...
auto-patchelf: 6 dependencies could not be satisfied
error: auto-patchelf could not satisfy dependency libgcc_s.so.1 wanted by
/nix/store/kl8bjrlmlzcjz47c0n6kjsj1yxi6zpqm-dmd-binary-2.098.0/lib/libphobos2.so.0.98.0
error: auto-patchelf could not satisfy dependency libgcc_s.so.1 wanted by
/nix/store/kl8bjrlmlzcjz47c0n6kjsj1yxi6zpqm-dmd-binary-2.098.0/bin/rdmd
error: auto-patchelf could not satisfy dependency libgcc_s.so.1 wanted by
/nix/store/kl8bjrlmlzcjz47c0n6kjsj1yxi6zpqm-dmd-binary-2.098.0/bin/dub
error: auto-patchelf could not satisfy dependency libgcc_s.so.1 wanted by
/nix/store/kl8bjrlmlzcjz47c0n6kjsj1yxi6zpqm-dmd-binary-2.098.0/bin/dustmite
error: auto-patchelf could not satisfy dependency libgcc_s.so.1 wanted by
/nix/store/kl8bjrlmlzcjz47c0n6kjsj1yxi6zpqm-dmd-binary-2.098.0/bin/ddemangle
error: auto-patchelf could not satisfy dependency libgcc_s.so.1 wanted by
/nix/store/kl8bjrlmlzcjz47c0n6kjsj1yxi6zpqm-dmd-binary-2.098.0/bin/dmd
auto-patchelf failed to find all the required dependencies.
...
After investigation, it turned out that the cuase was a recent [change in
Nixpkgs][0] after which `libgcc_s.so` is no longer part of the `glibc` package:
Before (nixpkgs @ 2022-03-30):
> nix build --json 'github:NixOS/nixpkgs/710fed5a2483f945b14f4a58af2cd3676b42d8c8#glibc^out' \
| jq -r '.[0].outputs.out' \
| xargs -I{} find {} \( -type l -or -type f \) -name '*libgcc_s*'
/nix/store/q29bwjibv9gi9n86203s38n0577w09sx-glibc-2.33-117/lib/libgcc_s.so.1
/nix/store/q29bwjibv9gi9n86203s38n0577w09sx-glibc-2.33-117/lib/libgcc_s.so
After (nixpkgs @ 2023-04-18):
> nix build --json 'github:NixOS/nixpkgs/555daa9d339b3df75e58ee558a4fec98ea92521e#glibc^out' \
| jq -r '.[0].outputs.out' \
| xargs -I{} find {} \( -type l -or -type f \) -name '*libgcc_s*'
(no output)
Instead, we should use `gccForLibs.libgcc` as it includes exactly what we need:
> nix build --json 'github:NixOS/nixpkgs/555daa9d339b3df75e58ee558a4fec98ea92521e#gccForLibs^libgcc' \
| jq -r '.[0].outputs.libgcc' \
| xargs -I{} find {} \( -type l -or -type f \) -name '*libgcc_s*'
/nix/store/5w5qpm9z3iyib615pdih6nvk9spv3jbv-gcc-12.2.0-libgcc/lib/libgcc_s.so.1
/nix/store/5w5qpm9z3iyib615pdih6nvk9spv3jbv-gcc-12.2.0-libgcc/lib/libgcc_s.so
This is nixpkgs again @ 2023-04-18, this time using `gccForLibs.libgcc`
instead of `glibc.out`.
[`gccForLibs`][1] is essentially `gcc.lib`:
* an alias to `stdenv.cc.cc` if the host and target are the same and are GNU or
* an alias to `gcc.cc` when `stdenv` is LLVM based as then `stdenv.cc.cc` would
refer to clang and the `lib` output point to libclang libs, which are very
different from what we need.
[0]: NixOS/nixpkgs#209870
[1]: NixOS/nixpkgs#91293
PetarKirov
added a commit
to PetarKirov/dlang.nix
that referenced
this pull request
May 7, 2023
…so.1`
After upgrading to a recent version of Nixpkgs (2023-04-18), the build broke
with the following error:
...
auto-patchelf: 6 dependencies could not be satisfied
error: auto-patchelf could not satisfy dependency libgcc_s.so.1 wanted by
/nix/store/kl8bjrlmlzcjz47c0n6kjsj1yxi6zpqm-dmd-binary-2.098.0/lib/libphobos2.so.0.98.0
error: auto-patchelf could not satisfy dependency libgcc_s.so.1 wanted by
/nix/store/kl8bjrlmlzcjz47c0n6kjsj1yxi6zpqm-dmd-binary-2.098.0/bin/rdmd
error: auto-patchelf could not satisfy dependency libgcc_s.so.1 wanted by
/nix/store/kl8bjrlmlzcjz47c0n6kjsj1yxi6zpqm-dmd-binary-2.098.0/bin/dub
error: auto-patchelf could not satisfy dependency libgcc_s.so.1 wanted by
/nix/store/kl8bjrlmlzcjz47c0n6kjsj1yxi6zpqm-dmd-binary-2.098.0/bin/dustmite
error: auto-patchelf could not satisfy dependency libgcc_s.so.1 wanted by
/nix/store/kl8bjrlmlzcjz47c0n6kjsj1yxi6zpqm-dmd-binary-2.098.0/bin/ddemangle
error: auto-patchelf could not satisfy dependency libgcc_s.so.1 wanted by
/nix/store/kl8bjrlmlzcjz47c0n6kjsj1yxi6zpqm-dmd-binary-2.098.0/bin/dmd
auto-patchelf failed to find all the required dependencies.
...
After investigation, it turned out that the cuase was a recent [change in
Nixpkgs][0] after which `libgcc_s.so` is no longer part of the `glibc` package:
Before (nixpkgs @ 2022-03-30):
> nix build --json 'github:NixOS/nixpkgs/710fed5a2483f945b14f4a58af2cd3676b42d8c8#glibc^out' \
| jq -r '.[0].outputs.out' \
| xargs -I{} find {} \( -type l -or -type f \) -name '*libgcc_s*'
/nix/store/q29bwjibv9gi9n86203s38n0577w09sx-glibc-2.33-117/lib/libgcc_s.so.1
/nix/store/q29bwjibv9gi9n86203s38n0577w09sx-glibc-2.33-117/lib/libgcc_s.so
After (nixpkgs @ 2023-04-18):
> nix build --json 'github:NixOS/nixpkgs/555daa9d339b3df75e58ee558a4fec98ea92521e#glibc^out' \
| jq -r '.[0].outputs.out' \
| xargs -I{} find {} \( -type l -or -type f \) -name '*libgcc_s*'
(no output)
Instead, we should use `gccForLibs.libgcc` as it includes exactly what we need:
> nix build --json 'github:NixOS/nixpkgs/555daa9d339b3df75e58ee558a4fec98ea92521e#gccForLibs^libgcc' \
| jq -r '.[0].outputs.libgcc' \
| xargs -I{} find {} \( -type l -or -type f \) -name '*libgcc_s*'
/nix/store/5w5qpm9z3iyib615pdih6nvk9spv3jbv-gcc-12.2.0-libgcc/lib/libgcc_s.so.1
/nix/store/5w5qpm9z3iyib615pdih6nvk9spv3jbv-gcc-12.2.0-libgcc/lib/libgcc_s.so
This is nixpkgs again @ 2023-04-18, this time using `gccForLibs.libgcc`
instead of `glibc.out`.
[`gccForLibs`][1] is essentially `gcc.lib`:
* an alias to `stdenv.cc.cc` if the host and target are the same and are GNU or
* an alias to `gcc.cc` when `stdenv` is LLVM based as then `stdenv.cc.cc` would
refer to clang and the `lib` output point to libclang libs, which are very
different from what we need.
[0]: NixOS/nixpkgs#209870
[1]: NixOS/nixpkgs#91293
PetarKirov
added a commit
to PetarKirov/dlang.nix
that referenced
this pull request
Sep 4, 2023
…so.1`
After upgrading to a recent version of Nixpkgs (2023-04-18), the build broke
with the following error:
...
auto-patchelf: 6 dependencies could not be satisfied
error: auto-patchelf could not satisfy dependency libgcc_s.so.1 wanted by
/nix/store/kl8bjrlmlzcjz47c0n6kjsj1yxi6zpqm-dmd-binary-2.098.0/lib/libphobos2.so.0.98.0
error: auto-patchelf could not satisfy dependency libgcc_s.so.1 wanted by
/nix/store/kl8bjrlmlzcjz47c0n6kjsj1yxi6zpqm-dmd-binary-2.098.0/bin/rdmd
error: auto-patchelf could not satisfy dependency libgcc_s.so.1 wanted by
/nix/store/kl8bjrlmlzcjz47c0n6kjsj1yxi6zpqm-dmd-binary-2.098.0/bin/dub
error: auto-patchelf could not satisfy dependency libgcc_s.so.1 wanted by
/nix/store/kl8bjrlmlzcjz47c0n6kjsj1yxi6zpqm-dmd-binary-2.098.0/bin/dustmite
error: auto-patchelf could not satisfy dependency libgcc_s.so.1 wanted by
/nix/store/kl8bjrlmlzcjz47c0n6kjsj1yxi6zpqm-dmd-binary-2.098.0/bin/ddemangle
error: auto-patchelf could not satisfy dependency libgcc_s.so.1 wanted by
/nix/store/kl8bjrlmlzcjz47c0n6kjsj1yxi6zpqm-dmd-binary-2.098.0/bin/dmd
auto-patchelf failed to find all the required dependencies.
...
After investigation, it turned out that the cuase was a recent [change in
Nixpkgs][0] after which `libgcc_s.so` is no longer part of the `glibc` package:
Before (nixpkgs @ 2022-03-30):
> nix build --json 'github:NixOS/nixpkgs/710fed5a2483f945b14f4a58af2cd3676b42d8c8#glibc^out' \
| jq -r '.[0].outputs.out' \
| xargs -I{} find {} \( -type l -or -type f \) -name '*libgcc_s*'
/nix/store/q29bwjibv9gi9n86203s38n0577w09sx-glibc-2.33-117/lib/libgcc_s.so.1
/nix/store/q29bwjibv9gi9n86203s38n0577w09sx-glibc-2.33-117/lib/libgcc_s.so
After (nixpkgs @ 2023-04-18):
> nix build --json 'github:NixOS/nixpkgs/555daa9d339b3df75e58ee558a4fec98ea92521e#glibc^out' \
| jq -r '.[0].outputs.out' \
| xargs -I{} find {} \( -type l -or -type f \) -name '*libgcc_s*'
(no output)
Instead, we should use `gccForLibs.libgcc` as it includes exactly what we need:
> nix build --json 'github:NixOS/nixpkgs/555daa9d339b3df75e58ee558a4fec98ea92521e#gccForLibs^libgcc' \
| jq -r '.[0].outputs.libgcc' \
| xargs -I{} find {} \( -type l -or -type f \) -name '*libgcc_s*'
/nix/store/5w5qpm9z3iyib615pdih6nvk9spv3jbv-gcc-12.2.0-libgcc/lib/libgcc_s.so.1
/nix/store/5w5qpm9z3iyib615pdih6nvk9spv3jbv-gcc-12.2.0-libgcc/lib/libgcc_s.so
This is nixpkgs again @ 2023-04-18, this time using `gccForLibs.libgcc`
instead of `glibc.out`.
[`gccForLibs`][1] is essentially `gcc.lib`:
* an alias to `stdenv.cc.cc` if the host and target are the same and are GNU or
* an alias to `gcc.cc` when `stdenv` is LLVM based as then `stdenv.cc.cc` would
refer to clang and the `lib` output point to libclang libs, which are very
different from what we need.
[0]: NixOS/nixpkgs#209870
[1]: NixOS/nixpkgs#91293
PetarKirov
added a commit
to PetarKirov/dlang.nix
that referenced
this pull request
Sep 20, 2023
…so.1`
After upgrading to a recent version of Nixpkgs (2023-04-18), the build broke
with the following error:
...
auto-patchelf: 6 dependencies could not be satisfied
error: auto-patchelf could not satisfy dependency libgcc_s.so.1 wanted by
/nix/store/kl8bjrlmlzcjz47c0n6kjsj1yxi6zpqm-dmd-binary-2.098.0/lib/libphobos2.so.0.98.0
error: auto-patchelf could not satisfy dependency libgcc_s.so.1 wanted by
/nix/store/kl8bjrlmlzcjz47c0n6kjsj1yxi6zpqm-dmd-binary-2.098.0/bin/rdmd
error: auto-patchelf could not satisfy dependency libgcc_s.so.1 wanted by
/nix/store/kl8bjrlmlzcjz47c0n6kjsj1yxi6zpqm-dmd-binary-2.098.0/bin/dub
error: auto-patchelf could not satisfy dependency libgcc_s.so.1 wanted by
/nix/store/kl8bjrlmlzcjz47c0n6kjsj1yxi6zpqm-dmd-binary-2.098.0/bin/dustmite
error: auto-patchelf could not satisfy dependency libgcc_s.so.1 wanted by
/nix/store/kl8bjrlmlzcjz47c0n6kjsj1yxi6zpqm-dmd-binary-2.098.0/bin/ddemangle
error: auto-patchelf could not satisfy dependency libgcc_s.so.1 wanted by
/nix/store/kl8bjrlmlzcjz47c0n6kjsj1yxi6zpqm-dmd-binary-2.098.0/bin/dmd
auto-patchelf failed to find all the required dependencies.
...
After investigation, it turned out that the cuase was a recent [change in
Nixpkgs][0] after which `libgcc_s.so` is no longer part of the `glibc` package:
Before (nixpkgs @ 2022-03-30):
> nix build --json 'github:NixOS/nixpkgs/710fed5a2483f945b14f4a58af2cd3676b42d8c8#glibc^out' \
| jq -r '.[0].outputs.out' \
| xargs -I{} find {} \( -type l -or -type f \) -name '*libgcc_s*'
/nix/store/q29bwjibv9gi9n86203s38n0577w09sx-glibc-2.33-117/lib/libgcc_s.so.1
/nix/store/q29bwjibv9gi9n86203s38n0577w09sx-glibc-2.33-117/lib/libgcc_s.so
After (nixpkgs @ 2023-04-18):
> nix build --json 'github:NixOS/nixpkgs/555daa9d339b3df75e58ee558a4fec98ea92521e#glibc^out' \
| jq -r '.[0].outputs.out' \
| xargs -I{} find {} \( -type l -or -type f \) -name '*libgcc_s*'
(no output)
Instead, we should use `gccForLibs.libgcc` as it includes exactly what we need:
> nix build --json 'github:NixOS/nixpkgs/555daa9d339b3df75e58ee558a4fec98ea92521e#gccForLibs^libgcc' \
| jq -r '.[0].outputs.libgcc' \
| xargs -I{} find {} \( -type l -or -type f \) -name '*libgcc_s*'
/nix/store/5w5qpm9z3iyib615pdih6nvk9spv3jbv-gcc-12.2.0-libgcc/lib/libgcc_s.so.1
/nix/store/5w5qpm9z3iyib615pdih6nvk9spv3jbv-gcc-12.2.0-libgcc/lib/libgcc_s.so
This is nixpkgs again @ 2023-04-18, this time using `gccForLibs.libgcc`
instead of `glibc.out`.
[`gccForLibs`][1] is essentially `gcc.lib`:
* an alias to `stdenv.cc.cc` if the host and target are the same and are GNU or
* an alias to `gcc.cc` when `stdenv` is LLVM based as then `stdenv.cc.cc` would
refer to clang and the `lib` output point to libclang libs, which are very
different from what we need.
[0]: NixOS/nixpkgs#209870
[1]: NixOS/nixpkgs#91293
PetarKirov
added a commit
to PetarKirov/dlang.nix
that referenced
this pull request
Sep 20, 2023
…so.1`
After upgrading to a recent version of Nixpkgs (2023-04-18), the build broke
with the following error:
...
auto-patchelf: 6 dependencies could not be satisfied
error: auto-patchelf could not satisfy dependency libgcc_s.so.1 wanted by
/nix/store/kl8bjrlmlzcjz47c0n6kjsj1yxi6zpqm-dmd-binary-2.098.0/lib/libphobos2.so.0.98.0
error: auto-patchelf could not satisfy dependency libgcc_s.so.1 wanted by
/nix/store/kl8bjrlmlzcjz47c0n6kjsj1yxi6zpqm-dmd-binary-2.098.0/bin/rdmd
error: auto-patchelf could not satisfy dependency libgcc_s.so.1 wanted by
/nix/store/kl8bjrlmlzcjz47c0n6kjsj1yxi6zpqm-dmd-binary-2.098.0/bin/dub
error: auto-patchelf could not satisfy dependency libgcc_s.so.1 wanted by
/nix/store/kl8bjrlmlzcjz47c0n6kjsj1yxi6zpqm-dmd-binary-2.098.0/bin/dustmite
error: auto-patchelf could not satisfy dependency libgcc_s.so.1 wanted by
/nix/store/kl8bjrlmlzcjz47c0n6kjsj1yxi6zpqm-dmd-binary-2.098.0/bin/ddemangle
error: auto-patchelf could not satisfy dependency libgcc_s.so.1 wanted by
/nix/store/kl8bjrlmlzcjz47c0n6kjsj1yxi6zpqm-dmd-binary-2.098.0/bin/dmd
auto-patchelf failed to find all the required dependencies.
...
After investigation, it turned out that the cuase was a recent [change in
Nixpkgs][0] after which `libgcc_s.so` is no longer part of the `glibc` package:
Before (nixpkgs @ 2022-03-30):
> nix build --json 'github:NixOS/nixpkgs/710fed5a2483f945b14f4a58af2cd3676b42d8c8#glibc^out' \
| jq -r '.[0].outputs.out' \
| xargs -I{} find {} \( -type l -or -type f \) -name '*libgcc_s*'
/nix/store/q29bwjibv9gi9n86203s38n0577w09sx-glibc-2.33-117/lib/libgcc_s.so.1
/nix/store/q29bwjibv9gi9n86203s38n0577w09sx-glibc-2.33-117/lib/libgcc_s.so
After (nixpkgs @ 2023-04-18):
> nix build --json 'github:NixOS/nixpkgs/555daa9d339b3df75e58ee558a4fec98ea92521e#glibc^out' \
| jq -r '.[0].outputs.out' \
| xargs -I{} find {} \( -type l -or -type f \) -name '*libgcc_s*'
(no output)
Instead, we should use `gccForLibs.libgcc` as it includes exactly what we need:
> nix build --json 'github:NixOS/nixpkgs/555daa9d339b3df75e58ee558a4fec98ea92521e#gccForLibs^libgcc' \
| jq -r '.[0].outputs.libgcc' \
| xargs -I{} find {} \( -type l -or -type f \) -name '*libgcc_s*'
/nix/store/5w5qpm9z3iyib615pdih6nvk9spv3jbv-gcc-12.2.0-libgcc/lib/libgcc_s.so.1
/nix/store/5w5qpm9z3iyib615pdih6nvk9spv3jbv-gcc-12.2.0-libgcc/lib/libgcc_s.so
This is nixpkgs again @ 2023-04-18, this time using `gccForLibs.libgcc`
instead of `glibc.out`.
[`gccForLibs`][1] is essentially `gcc.lib`:
* an alias to `stdenv.cc.cc` if the host and target are the same and are GNU or
* an alias to `gcc.cc` when `stdenv` is LLVM based as then `stdenv.cc.cc` would
refer to clang and the `lib` output point to libclang libs, which are very
different from what we need.
[0]: NixOS/nixpkgs#209870
[1]: NixOS/nixpkgs#91293
PetarKirov
added a commit
to PetarKirov/dlang.nix
that referenced
this pull request
Sep 20, 2023
…so.1`
After upgrading to a recent version of Nixpkgs (2023-04-18), the build broke
with the following error:
...
auto-patchelf: 6 dependencies could not be satisfied
error: auto-patchelf could not satisfy dependency libgcc_s.so.1 wanted by
/nix/store/kl8bjrlmlzcjz47c0n6kjsj1yxi6zpqm-dmd-binary-2.098.0/lib/libphobos2.so.0.98.0
error: auto-patchelf could not satisfy dependency libgcc_s.so.1 wanted by
/nix/store/kl8bjrlmlzcjz47c0n6kjsj1yxi6zpqm-dmd-binary-2.098.0/bin/rdmd
error: auto-patchelf could not satisfy dependency libgcc_s.so.1 wanted by
/nix/store/kl8bjrlmlzcjz47c0n6kjsj1yxi6zpqm-dmd-binary-2.098.0/bin/dub
error: auto-patchelf could not satisfy dependency libgcc_s.so.1 wanted by
/nix/store/kl8bjrlmlzcjz47c0n6kjsj1yxi6zpqm-dmd-binary-2.098.0/bin/dustmite
error: auto-patchelf could not satisfy dependency libgcc_s.so.1 wanted by
/nix/store/kl8bjrlmlzcjz47c0n6kjsj1yxi6zpqm-dmd-binary-2.098.0/bin/ddemangle
error: auto-patchelf could not satisfy dependency libgcc_s.so.1 wanted by
/nix/store/kl8bjrlmlzcjz47c0n6kjsj1yxi6zpqm-dmd-binary-2.098.0/bin/dmd
auto-patchelf failed to find all the required dependencies.
...
After investigation, it turned out that the cuase was a recent [change in
Nixpkgs][0] after which `libgcc_s.so` is no longer part of the `glibc` package:
Before (nixpkgs @ 2022-03-30):
> nix build --json 'github:NixOS/nixpkgs/710fed5a2483f945b14f4a58af2cd3676b42d8c8#glibc^out' \
| jq -r '.[0].outputs.out' \
| xargs -I{} find {} \( -type l -or -type f \) -name '*libgcc_s*'
/nix/store/q29bwjibv9gi9n86203s38n0577w09sx-glibc-2.33-117/lib/libgcc_s.so.1
/nix/store/q29bwjibv9gi9n86203s38n0577w09sx-glibc-2.33-117/lib/libgcc_s.so
After (nixpkgs @ 2023-04-18):
> nix build --json 'github:NixOS/nixpkgs/555daa9d339b3df75e58ee558a4fec98ea92521e#glibc^out' \
| jq -r '.[0].outputs.out' \
| xargs -I{} find {} \( -type l -or -type f \) -name '*libgcc_s*'
(no output)
Instead, we should use `gccForLibs.libgcc` as it includes exactly what we need:
> nix build --json 'github:NixOS/nixpkgs/555daa9d339b3df75e58ee558a4fec98ea92521e#gccForLibs^libgcc' \
| jq -r '.[0].outputs.libgcc' \
| xargs -I{} find {} \( -type l -or -type f \) -name '*libgcc_s*'
/nix/store/5w5qpm9z3iyib615pdih6nvk9spv3jbv-gcc-12.2.0-libgcc/lib/libgcc_s.so.1
/nix/store/5w5qpm9z3iyib615pdih6nvk9spv3jbv-gcc-12.2.0-libgcc/lib/libgcc_s.so
This is nixpkgs again @ 2023-04-18, this time using `gccForLibs.libgcc`
instead of `glibc.out`.
[`gccForLibs`][1] is essentially `gcc.lib`:
* an alias to `stdenv.cc.cc` if the host and target are the same and are GNU or
* an alias to `gcc.cc` when `stdenv` is LLVM based as then `stdenv.cc.cc` would
refer to clang and the `lib` output point to libclang libs, which are very
different from what we need.
[0]: NixOS/nixpkgs#209870
[1]: NixOS/nixpkgs#91293
PetarKirov
added a commit
to PetarKirov/dlang.nix
that referenced
this pull request
Sep 21, 2023
…so.1`
After upgrading to a recent version of Nixpkgs (2023-04-18), the build broke
with the following error:
...
auto-patchelf: 6 dependencies could not be satisfied
error: auto-patchelf could not satisfy dependency libgcc_s.so.1 wanted by
/nix/store/kl8bjrlmlzcjz47c0n6kjsj1yxi6zpqm-dmd-binary-2.098.0/lib/libphobos2.so.0.98.0
error: auto-patchelf could not satisfy dependency libgcc_s.so.1 wanted by
/nix/store/kl8bjrlmlzcjz47c0n6kjsj1yxi6zpqm-dmd-binary-2.098.0/bin/rdmd
error: auto-patchelf could not satisfy dependency libgcc_s.so.1 wanted by
/nix/store/kl8bjrlmlzcjz47c0n6kjsj1yxi6zpqm-dmd-binary-2.098.0/bin/dub
error: auto-patchelf could not satisfy dependency libgcc_s.so.1 wanted by
/nix/store/kl8bjrlmlzcjz47c0n6kjsj1yxi6zpqm-dmd-binary-2.098.0/bin/dustmite
error: auto-patchelf could not satisfy dependency libgcc_s.so.1 wanted by
/nix/store/kl8bjrlmlzcjz47c0n6kjsj1yxi6zpqm-dmd-binary-2.098.0/bin/ddemangle
error: auto-patchelf could not satisfy dependency libgcc_s.so.1 wanted by
/nix/store/kl8bjrlmlzcjz47c0n6kjsj1yxi6zpqm-dmd-binary-2.098.0/bin/dmd
auto-patchelf failed to find all the required dependencies.
...
After investigation, it turned out that the cuase was a recent [change in
Nixpkgs][0] after which `libgcc_s.so` is no longer part of the `glibc` package:
Before (nixpkgs @ 2022-03-30):
> nix build --json 'github:NixOS/nixpkgs/710fed5a2483f945b14f4a58af2cd3676b42d8c8#glibc^out' \
| jq -r '.[0].outputs.out' \
| xargs -I{} find {} \( -type l -or -type f \) -name '*libgcc_s*'
/nix/store/q29bwjibv9gi9n86203s38n0577w09sx-glibc-2.33-117/lib/libgcc_s.so.1
/nix/store/q29bwjibv9gi9n86203s38n0577w09sx-glibc-2.33-117/lib/libgcc_s.so
After (nixpkgs @ 2023-04-18):
> nix build --json 'github:NixOS/nixpkgs/555daa9d339b3df75e58ee558a4fec98ea92521e#glibc^out' \
| jq -r '.[0].outputs.out' \
| xargs -I{} find {} \( -type l -or -type f \) -name '*libgcc_s*'
(no output)
Instead, we should use `gccForLibs.libgcc` as it includes exactly what we need:
> nix build --json 'github:NixOS/nixpkgs/555daa9d339b3df75e58ee558a4fec98ea92521e#gccForLibs^libgcc' \
| jq -r '.[0].outputs.libgcc' \
| xargs -I{} find {} \( -type l -or -type f \) -name '*libgcc_s*'
/nix/store/5w5qpm9z3iyib615pdih6nvk9spv3jbv-gcc-12.2.0-libgcc/lib/libgcc_s.so.1
/nix/store/5w5qpm9z3iyib615pdih6nvk9spv3jbv-gcc-12.2.0-libgcc/lib/libgcc_s.so
This is nixpkgs again @ 2023-04-18, this time using `gccForLibs.libgcc`
instead of `glibc.out`.
[`gccForLibs`][1] is essentially `gcc.lib`:
* an alias to `stdenv.cc.cc` if the host and target are the same and are GNU or
* an alias to `gcc.cc` when `stdenv` is LLVM based as then `stdenv.cc.cc` would
refer to clang and the `lib` output point to libclang libs, which are very
different from what we need.
[0]: NixOS/nixpkgs#209870
[1]: NixOS/nixpkgs#91293
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Motivation for this change
Instead, we have a new
gccForLibs, which has the appropriate definition for e.g. avoidingx86_32linking problems.Things done
sandboxinnix.confon non-NixOS linux)nix-shell -p nixpkgs-review --run "nixpkgs-review wip"./result/bin/)nix path-info -Sbefore and after)