Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#42037 - [rtorrent] [libtorrent] fallocate
Attached to Project:
Community Packages
Opened by cupcake (muffins) - Saturday, 20 September 2014, 17:17 GMT
Last edited by Gaetan Bisson (vesath) - Saturday, 13 December 2014, 21:25 GMT
Opened by cupcake (muffins) - Saturday, 20 September 2014, 17:17 GMT
Last edited by Gaetan Bisson (vesath) - Saturday, 13 December 2014, 21:25 GMT
|
DetailsDescription:
I don't think there's any reason that these are built without --with-posix-fallocate https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=557521 |
This task depends upon
Closed by Gaetan Bisson (vesath)
Saturday, 13 December 2014, 21:25 GMT
Reason for closing: No response
Saturday, 13 December 2014, 21:25 GMT
Reason for closing: No response
Comment by Gaetan Bisson (vesath) -
Monday, 22 September 2014, 04:18 GMT
Should --with-posix-fallocate be the default upstream, then?
Comment by Gaetan Bisson (vesath) -
Monday, 22 September 2014, 04:25 GMT
Also, our libtorrent build already finds fallocate and uses it. It seems to me that enabling posix_fallocate yields no advantage over that. See lines 108 to 118 of libtorrent-0.13.4's src/data/socket_file.cc for instance.