Arch Linux User Repository

Please use this package for stable more reliable builds

https://aur.archlinux.org/packages/darling/

This one is identical but locked in on a last known working git ref and I will update as often as I can.

I have also raised an issue about versioning so maybe we can get some kind of tags for future versions and stable working builds

https://github.com/darlinghq/darling/issues/537

Yes I am.

@LeRieur: Are you using Arch Linux x86_64?

It doesn't build: https://0bin.net/paste/2Xv8WyeK8VkIcwoN#228SBG-bwAb+1F93Qm4qN43c1CZhL5P8ZvB59kkK4Qj

@Maxqia: I'm able to build darling-git without lib32-clang. Do you need lib32-clang? @leftyb: You need gcc-multilib to install darling-git. gcc-multilib provides gcc, you can safely answer 'Y' on Yaourt prompt.

Hi all when i run : yaourt -S darling-git I get the following error: :: gcc-multilib and gcc are in conflict. Remove gcc? [y/N] N uname -a Linux leftyPC 4.6.3-1-ARCH #1 SMP PREEMPT Fri Jun 24 21:19:13 CEST 2016 x86_64 GNU/Linux Any ideas? Thank you.

I think you have to have lib32-clang to build this package for 32-bit. Can you replace gcc-multilib with lib32-clang, because lib32-clang has gcc-multilib as a dependancy.

@jamesan: Ok, that's done. I'll do a similar change in Darling PKGBUILD too. Thank you.

The version string doesn't follow the VCS package guidelines. For git repos that have "no tags then use number of revisions since beginning of the history" followed by the abbreviated hash commit name with the format: rREVISION.HASH (i.e. "r23.4036a2b" given the current package version). Just as the REVISION count only counts revisions that involve the "src/lkm" path of the source, the HASH value should refer not necessarily to the current HEAD commit but rather to the last commit that involved changes under the "src/lkm" path. The prevents unnecessary package upgrades due to version string changes resulting from a commit made upstream that doesn't affect anything under the "src/lkm" path, as the HASH (and version string) should remain unchanged until a commit is made affect code under that path. This can be done by replacing the latter git-rev-parse command with git-rev-list like so: git rev-list --abbrev-commit --max-count=1 HEAD -- "src/lkm" That fetches abbreivated hash of the one commit closest to HEAD under the "src/lkm" path. Putting it all together and adopting the guideline's example use of printf instead of echo, the one pkgver() line (#22) deriving the version string can be: printf "r%s.%s" "$(git rev-list --count HEAD -- "src/lkm")" "$(git rev-list --abbrev-commit --max-count=1 HEAD -- "src/lkm")" You can find this all nicely packaged as a patch file here: http://pastebin.com/w46cs7yF Reference: https://wiki.archlinux.org/index.php/VCS_package_guidelines#The_pkgver.28.29_function

@wenLiangcan: Ok, it's done. Thank.

I think darling-mach-dkms-git should be declared providing darling-mach-git