aboutsummaryrefslogtreecommitdiffstats
path: root/lib/fuse_versionscript
diff options
context:
space:
mode:
authorBernd Schubert <bernd.schubert@fastmail.fm>2023-07-07 17:18:38 +0200
committerGitHub <noreply@github.com>2023-07-07 16:18:38 +0100
commit624783d73baf151747fa72359af16c37260bfee2 (patch)
treee875a44edd8cd7cec6b30e112120b6fc21bc88e2 /lib/fuse_versionscript
parentd888c305970d73e9ca75e90b7705183299b36b04 (diff)
downloadlibfuse-624783d73baf151747fa72359af16c37260bfee2.tar.gz
Allow linking with mold / fix the version script (#814)
This fixes issue https://github.com/libfuse/libfuse/issues/810 and should avoid mold linking errors. Commit d4e294b removed made fuse_register_module() a static function, but forgot to remove it from the version script. Commit fe4f942 introduced copy_file_range to libfuse and added the non-exiting (neither declared nor defined) function fuse_reply_copy_file_range() to the version script. Kernel side just exects an integer reply how much was copied, using fuse_reply_write() as in fuse_lib_copy_file_range() is sufficient and no extra function is needed. Co-authored-by: Bernd Schubert <bschubert@ddn.com>
Diffstat (limited to 'lib/fuse_versionscript')
-rw-r--r--lib/fuse_versionscript2
1 files changed, 0 insertions, 2 deletions
diff --git a/lib/fuse_versionscript b/lib/fuse_versionscript
index 55ab9e5..c0d58bf 100644
--- a/lib/fuse_versionscript
+++ b/lib/fuse_versionscript
@@ -83,7 +83,6 @@ FUSE_3.0 {
fuse_fs_unlink;
fuse_fs_utimens;
fuse_fs_write;
- fuse_register_module;
fuse_reply_iov;
fuse_version;
fuse_pkgversion;
@@ -161,7 +160,6 @@ FUSE_3.3 {
FUSE_3.4 {
global:
fuse_fs_copy_file_range;
- fuse_reply_copy_file_range;
} FUSE_3.3;
FUSE_3.7 {