Package Details: libfiber-git r215.111db17-4

Git Clone URL: (read-only, click to copy)
Package Base: libfiber-git
Description: A User Space Threading Library Supporting Multi-Core Systems
Upstream URL:
Licenses: custom:ISC
Conflicts: libfiber
Provides: libfiber
Submitter: anatolik
Maintainer: None
Last Packager: ayekat
Votes: 0
Popularity: 0.000000
First Submitted: 2013-07-25 04:35 (UTC)
Last Updated: 2019-07-15 06:45 (UTC)

Latest Comments

anatolik commented on 2018-12-08 00:53 (UTC)

Tinu, I see that you did amazing job with this package and I'm sure that you can drive it without me. So let's leave you as an owner and I will stay just a user.

ayekat commented on 2018-12-07 23:13 (UTC)

Oh, thanks! Do you still use it and would thus be interested in co-maintaining it?

anatolik commented on 2018-12-07 20:12 (UTC)

Hi I just this only the package. Feel free to adopt and make required changes.

ayekat commented on 2018-12-07 18:14 (UTC) (edited on 2018-12-07 18:16 (UTC) by ayekat)

Hi, I'm currently maintaining a PKGBUILD for libfiber here, where I have applied the following changes:

  • It is built against Arch's packaged libev (rather than the one bundled with the upstream code, as it doesn't appear to have any libfiber-specific changes).

  • It changes the Makefile to compile libev with the dist scheduler rather than wsd (work-stealing), because latter appears to schedule fibers in a weird way (it somehow jumps back and forth between the same two fibers and never schedules any of the others; I'll have to investigate this a bit and perhaps ask upstream).

  • It installs also the headers + a pkgconf file for compiling and linking against libfiber.

  • It installs the LICENSE file (as it's custom:ISC).

Would you mind taking a look at that to see if those changes could be incorporated into the AUR package (so we don't have to maintain duplicate versions of the package)?

As I've only got an x86_64 machine to test, I have hardcoded the package and the pkgconf file to that architecture for now, so if you wish to support other architectures, it may need some tweaking.