| Git Clone URL: | https://aur.archlinux.org/folly.git (read-only, click to copy) |
|---|---|
| Package Base: | folly |
| Description: | An open-source C++ library developed and used at Facebook |
| Upstream URL: | https://github.com/facebook/folly |
| Licenses: | Apache-2.0 |
| Provides: | libfolly.so, libfollybenchmark.so, libfolly_test_util.so |
| Submitter: | dseg |
| Maintainer: | ftiasch (MrAnno, carsme) |
| Last Packager: | ftiasch |
| Votes: | 7 |
| Popularity: | 0.000016 |
| First Submitted: | 2015-03-20 08:29 (UTC) |
| Last Updated: | 2025-06-04 04:44 (UTC) |
Thank you for maintaining the package!
For some people who are not familiar with the testing repositories, https://wiki.archlinux.org/title/Official_repositories#Testing_repositories
you can wait for the liburing>=2.10 to be on stable repositories.
I'm not sure it's OK to enable testing repositories even when you need to build the latest version now.
@envolution I successfully built and updated the package. Thanks for your help! I also listed you as a contributor.
by the way, testing has liburing 2.10 - https://archlinux.org/packages/extra-testing/x86_64/liburing/
I think it's fine to just require liburing>=2.10
@ftiasch I got it to compile with the following: https://github.com/envolution/aur/tree/main/abandoned/folly
Both patches changed, the cmake one I just changed the offset to match the current version
I left some comments about things that may not be needed, but my laptop takes too long to run through more full compilations to confirm. In any case it seems to compile happily now
Hi all. I managed to bump the version to v2025.06.02.00.
I first encountered an issue regarding of missing io_uring_zcrx_*. I found it was added in the commit, which in turn will appear in liburing-2.10. As the official package is for 2.9, changing the dep from liburing to liburing-git will fix this, for now.
Next, I struggled with some random errors relating to glog. I also found this issue, where the mentioned fixes already included in this package somehow stopped working. I can't figure out why, so I sincerely ask someone to help.
No worries - I did take a quick look and ran into at least one file missing from the release archive that exists in the git repo. You may find cloning the version tag a requirement to get it to build
using release folly-2025.06.02.00.tar.gz for reference:
CMake Error at folly/CMakeLists.txt:108 (add_library):
Cannot find source file:
python/executor.cpp
Tried extensions .c .C .c++ .cc .cpp .cxx .cu .mpp .m .M .mm .ixx .cppm
.ccm .cxxm .c++m .h .hh .h++ .hm .hpp .hxx .in .txx .f .F .for .f77 .f90
.f95 .f03 .hip .ispc
CMake Error at folly/CMakeLists.txt:108 (add_library):
No SOURCES given to target: folly_python_cpp
@envolution I can try to fix it. But it's been a long time since my last commit. It may take me sometime to figure out why.
This fails for me:
In file included from /tmp/trizen-leont/folly/src/folly-2024.10.28.00/folly/python/ProactorExecutor.h:20,
from folly/ProactorExecutor.cpp:17:
/tmp/trizen-leont/folly/src/folly-2024.10.28.00/folly/python/AsyncioExecutor.h: In static member function ‘static bool folly::python::AsyncioExecutor::isPyFinalizing()’:
/tmp/trizen-leont/folly/src/folly-2024.10.28.00/folly/python/AsyncioExecutor.h:82:12: error: ‘_Py_IsFinalizing’ was not declared in this scope; did you mean ‘Py_IsFinalizing’?
82 | return _Py_IsFinalizing();
| ^~~~~~~~~~~~~~~~
| Py_IsFinalizing
Apparently _Py_IsFinalizing is depreciated
It looks like it needs https://github.com/facebook/folly/pull/2360 to build
@joshm No, it's not. cython is listed as a make dependency. You can try makepkg -s to ensure make dependencies are installed properly if you built the AUR package manually.
Pinned Comments
carsme commented on 2023-12-07 04:02 (UTC)
BREAKING CHANGE: This package now builds shared objects:
instead of the static libraries:
Downstream packages must move
follyfrom themakedependstodependsarray to stay functional.We are doing this change since dynamic rather than static linking between packages is more in line with Arch Linux packaging practices (or just Linux packaging practices in general).