perl: Work around cross-compilation issue with gcc 7 #35529
Conversation
| nativeBuildInputs = [ buildPackages.stdenv.cc ]; | ||
| # Hacky! But not sure how else we can access a native-targeted gcc6 | ||
| # https://github.com/arsv/perl-cross/issues/60 | ||
| nativeBuildInputs = [ buildPackages.buildPackages.gcc6 ]; |
There was a problem hiding this comment.
@Ericson2314 can we do better than this?
There was a problem hiding this comment.
depsBuildBuild = [ buildPackages.stdenv.cc ]; I think, though I'm still not sure in cross stuff.
There was a problem hiding this comment.
This is at least what we do in (some) other cases when a build needs to compile stuff to use it during the build already.
There was a problem hiding this comment.
@vcunat That's what was here, but I specifically need gcc6
There was a problem hiding this comment.
I didn't see depsBuildBuild here.
There was a problem hiding this comment.
Ah, right, it was nativeBuildInputs. But even putting in depsBuildBuild, simple buildPackages.gcc6 gives me a cross-compiler, I need the double buildPackages (which seems wrong).
There was a problem hiding this comment.
That's surprising to me. It might be a bug in the implementation, docs, or my understanding...
There was a problem hiding this comment.
OK #35543 should now explain everything, but the short answer is this should be
depsBuildBuild = [ gcc6 ];
which, after elaborating the effect of callPackage splicing, is equivalentl to
depsBuildBuild = [ buildPackages.buildPackages.gcc6 ];
|
Success on x86_64-linux (full log) Partial log (click to expand)
|
|
Success on aarch64-linux (full log) Partial log (click to expand)
|
|
Success on x86_64-darwin (full log) Partial log (click to expand)
|
|
FWIW I can confirm the segfault behavior occurred on aarch64-musl as well (with gcc7) and that this fix resolved the problem. Thanks! |
No description provided.