-
-
Notifications
You must be signed in to change notification settings - Fork 14.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
pkgsCross.armv7l-hf-multiplatform.btrfs-progs fails to build #50925
Comments
Tries to locate python3 via pkg-config. Below is the config.log.
Apparently, there is no such pc:
|
I was able to add the following and make pkg-config work.
Then I've got the following:
|
ping @matthewbauer |
python3 is in nativeBuildInputs I am not sure pkg-config will pick it up from there. |
Yeah no buildPackages is needed here - it needs to link against the cross built python. |
@Mic92 It doesn't pick, therefore the PKG_CONFIG_PATH.
The above is what I get, @matthewbauer . |
For what it's worth, I've successfully built btrfs-progs for arm on my cross-compilation branches. Perhaps this has to do with python cross-compilation support (nixpkgs currently produces broken python3 extensions), which I'll be submitting some more patches for. |
This doesn't work pretty much.
|
I think matthewbauer@e23b753 will fix this. |
Hey @matthewbauer, I'm recompiling from scratch after #50915 |
Hello back @matthewbauer , I get
The python I get in the build env is 2.7.15. How did you get python3 w/ the settings above? best. |
Mic92@3c31069 should fix this |
This got further by now - it's now failing here:
|
Thank you for your contributions. This has been automatically marked as stale because it has had no activity for 180 days. If this is still important to you, we ask that you leave a comment below. Your comment can be as simple as "still important to me". This lets people see that at least one person still cares about this. Someone will have to do this at most twice a year if there is no other activity. Here are suggestions that might help resolve this more quickly:
|
This now fails in
I don't really understand why it tries to invoke the aarch64 cmake - it's passed into |
for me it still fails with the above-mentioned i was told to cc @FRidh as he might have valuable insight |
It takes the header from x86 instead of arm hence it fails because |
Aah, I see - it fails at |
Actually, no. The
Weird. |
@flokli i can't confirm that building
|
@flokli on |
The original issue sounds like precisely the sort of thing my pkg-config wrapper we supposed to fix. I bet @matthewbauer's change, unreverted, will get us close. |
OK this builds for me now after #91177, no changes needed. |
@Ericson2314 i can confirm that this now cross-compiles for |
I can confirm the same findings, with nixpkgs master at d8d19f2.
|
This breaks the minimal cross build, as udisks2 is pulled in by default in the minimal image. Reasoning on why we usually want udisks: #49270 (comment) |
I'm thinking it very well might |
@Ericson2314 If you're referring to #91178 making a difference to #63043, I checked and it doesn't. |
This is fixed by #98915. |
Issue description
Steps to reproduce
Im on nixpkgs/staging.
The text was updated successfully, but these errors were encountered: