Conversation
|
It looks like the ofborg eval doesn't show aarch64. Maybe you want to update meta.platforms? |
|
Result of 1 package built:2 suggestions:
|
|
AArch64 won't work as it is, but I've been looking quickly and with some changes it works. @jojosch might be able to help with figuring out the actual solution, as my method is bad. |
|
Weird flex, but here it is running on an aarch64 desktop^W phone. The changes I did to make it run, they are not change propositions, but a proof of concept showing the build should work. https://gist.github.com/45e28c83bda842b5a1b8f36cc5dbeef8 Let me explain. The If we don't force aarch64, it will build something on aarch64, but it will be an x86_64 binary! Weird! (But probably expected.) |
|
Added Previously a build on aarch64 (nix-on-droid) resulted in a x86_64 binary (as @samueldr mentioned) and now results in a proper aarch64 binary ( I also added the missing runHook's to |
|
By the way, I wasn't running on And I confirm it works as expected still. |


Motivation for this change
New upstream release https://dbeaver.io/2021/02/28/dbeaver-21-0/.
Upstream switched to calendar versioning therefore the large version bump.
@samueldr you mentioned in #108417 (comment) that you tried to build under aarch64 - this should now be possible (see dbeaver/dbeaver@699f1e2). If you got time, can you try if building/running under aarch64 works now?
Things done
sandboxinnix.confon non-NixOS linux)nix-shell -p nixpkgs-review --run "nixpkgs-review wip"./result/bin/)nix path-info -Sbefore and after)