Arch Linux User Repository

That is a problem with the luac5.4, compiler not with lsyncd.

Jul 21 23:57:38 thermi-probook systemd[1]: Started Process Core Dump (PID 925922/UID 0).
Jul 21 23:57:38 thermi-probook systemd-coredump[925928]: [🡕] Process 925921 (luac5.4) of user 1000 dumped core.

                                                         Module linux-vdso.so.1 with build-id d3c210522f2d619f9e3c2d7196aaa6ec2037e14b
                                                         Module ld-linux-x86-64.so.2 with build-id 0effd0e43efa4468d3c31871c93af0b7f3005673
                                                         Module libc.so.6 with build-id 60df1df31f02a7b23da83e8ef923359885b81492
                                                         Module libm.so.6 with build-id 1b7296ef9fd806e47060788389293c824b09ad72
                                                         Module luac with build-id 6a9bcb38fc643906774d6f9c6b2a792c0eda2897
                                                         Stack trace of thread 925921:
                                                         #0  0x00007f972188e36c n/a (libc.so.6 + 0x8e36c)
                                                         #1  0x00007f972183e838 raise (libc.so.6 + 0x3e838)
                                                         #2  0x00007f9721828535 abort (libc.so.6 + 0x28535)
                                                         #3  0x00007f972188245e n/a (libc.so.6 + 0x8245e)
                                                         #4  0x00007f97218980cc n/a (libc.so.6 + 0x980cc)
                                                         #5  0x00007f9721898bf4 n/a (libc.so.6 + 0x98bf4)
                                                         #6  0x00007f9721899ca3 n/a (libc.so.6 + 0x99ca3)
                                                         #7  0x00007f972189c8f3 free (libc.so.6 + 0x9c8f3)
                                                         #8  0x00005613142e96a2 n/a (luac + 0x206a2)
                                                         #9  0x00005613142d5ef9 n/a (luac + 0xcef9)
                                                         #10 0x00005613142d6956 n/a (luac + 0xd956)
                                                         #11 0x00005613142dbaaf n/a (luac + 0x12aaf)
                                                         #12 0x00005613142ce1f4 main (luac + 0x51f4)
                                                         #13 0x00007f9721829290 n/a (libc.so.6 + 0x29290)
                                                         #14 0x00007f972182934a __libc_start_main (libc.so.6 + 0x2934a)
                                                         #15 0x00005613142ce38e _start (luac + 0x538e)
                                                         ELF object binary architecture: AMD x86-64

I get a similar error since 2.3.0:

[  0%] Built target prepare_tests
[ 11%] Generating runner.out
Compiling built-in runner
[ 22%] Generating defaults.out
Compiling built-in default configs
corrupted double-linked list
make[2]: *** [CMakeFiles/lsyncd.dir/build.make:93: defaults.out] Aborted
make[2]: *** Deleting file 'defaults.out'
make[1]: *** [CMakeFiles/Makefile2:191: CMakeFiles/lsyncd.dir/all] Error 2
make: *** [Makefile:136: all] Error 2
==> ERROR: A failure occurred in build().
    Aborting...

I get this error when building this package in a CI pipeline running on a server. I don't get this error locally. Haven't figured out what is the difference though.

I get this for 2.3.0-1 update:

[ 22%] Built target prepare_tests
[ 33%] Generating runner.c
Generating built-in runner linkable
make[2]: *** [CMakeFiles/lsyncd.dir/build.make:93: defaults.out] Segmentation fault         (core dumped)
make[2]: *** Deleting file 'defaults.out'
make[1]: *** [CMakeFiles/Makefile2:191: CMakeFiles/lsyncd.dir/all] Error 2
make: *** [Makefile:136: all] Error 2
==> ERROR: A failure occurred in build().
    Aborting...

I just found a hardcoded usage of luac5.3 in the cmake instructions. I patched that out. Please let me know if that works for you.

Since it has been 518 days since the last AUR release, is it time to submit a request to mark this package as "orphaned"? I've never done this before, and I don't know what the rules or the customs are; I'm just asking.

I could not get foobster's patch to work. I had to follow roks532's suggestions. Note that you have to change directories into the build directory after you create it.

@foobster Also thanks from me, your simple addition works just fine.

@foobster thanks for the patch. It does work! Have to admit - took me a while to figure it out, though.

@foobster Huge thanks! This one finally works, I have lsyncd back. And now I can work comfortably too :)

The problem is that the generated make files end up referencing a mix of lua versions. The build itself works fine with lua 5.4 as long as it's used consistently. Fixing the CMake config would be preferable, but this is a quick and dirty fix that gets the job done:

diff --git a/PKGBUILD b/PKGBUILD
index eb03747..d25a424 100644
--- a/PKGBUILD
+++ b/PKGBUILD
@@ -29,6 +29,7 @@ build() {
     cd ${srcdir}/${pkgname}-release-${pkgver}
     mkdir -p build
     cd build
     cmake -DCMAKE_INSTALL_PREFIX=/usr ..
+    grep -E -rl 'luac?5\.[1-4]' . | xargs sed -i 's/\(luac\?5\.\)[1-4]/\14/g'
     make
 }

@kepi Yes, it's true.

@dpvpro unfortunately it doesn't help. It builds without any problem, but same error during runtime.

To be clear, I'm not able to remove lua package, as I had three more packages depending on it.

I didn't manage to get the last version working because of the lua version mismatch not with pacaur and also not from github directly. However I did manage to get the version 2.2.2 from github working on manjaro

the procedure to make it work:

  pacaur -Rs lsyncd  #remove lsyncd
  pacman -Rdd lua    #remove latest lua

download and unpack lsyncd version 2.2.2 from github: https://github.com/axkibe/lsyncd/releases/tag/release-2.2.2

 mkdir build #inside the unpacked directory
 cmake ..
 make
 sudo make install

Lsyncd should now work, for the config you should create /etc/lsyncd/lsyncd.conf.lua. I also created a service in /usr/lib/systemd/system/lsyncd.service

Now all works as it should

Same problem, unfortunately I'm not able to remove older luas myself but still need lsyncd badly :(

I opened issue in lsyncd (not sure if it helps as there is not much activity in repo): https://github.com/axkibe/lsyncd/issues/622

If you found another workaround but removing other luas, let me know please.

I'll add a workaround/fix once one becomes available. I myself don't use lsyncd anymore, so it's not a priority.

I removed lua53 and lua52 (losing VLC and GIMP as they had to go along with them), reinstalled lsyncd and now it works. Not optimal but I need lsyncd more than those two. Thanks njam for the tip.

I experience the same error ("bad binary format (version mismatch)").

Maybe caused by different lua versions installed (package "lua" (5.4), "lua53" (5.3) and "lua52" (5.2)), and then lsyncd picking the wrong one? See also https://github.com/axkibe/lsyncd/issues/413

I get this error after last update: error loading precompiled runner: runner: bad binary format (version mismatch) Any ideas?

Thank you for your work, I incorporated the changes made by wwwlea into the sources here.

@wwwlea's patch worked perfectly for me. @Thermi, can you update the package so that it includes his patches?

I had some errors building with the newest version of Lua (5.4) that was released earlier this month. I resolved these with two changes:

• A macro in lsyncd.h needs to be renamed from from "LUA_COMPAT_5_1" to "LUA_COMPAT_5_3"

• The "FindLua.cmake.patch" needs to be updated so that it also finds version 5.4 and not just 5.3 and 5.2

I have put these changes on GitHub at https://github.com/HippocampusGirl/lsyncd-aur

I think this should now depend on lua53 instead of lua.

I updated the PKGBUILD and made a patch to have this build against lua5.3. Upstream prefers Lua5.2 because Debian doesn't have some lua libraries for 5.3 packaged.

Would you consider incorporating the latest commit from https://github.com/vamega/lsyncd-aur/ into this package.

@Noeljunior it will build against lua 5.3 now. I was having trouble getting a working binary so I removed the 5.2 libs so it would stop building against them, modified pkgbuild so it would not require them, and it built successfully against 5.3.

As of lsyncd 2.2.3 it's supposed to be compatible with lua 5.3 moving forward so perhaps it's time to get this package updated to reflect that, and use it.

Good luck.

@beac0n, @ArcCha you've managed how to install; could you run it standalone? I mean, by running lsyncd in terminal.

based on the comment from ArcCha, this oneliner installed the package successfully on my machine:

LUA_DIR=/usr/include/lua5.2 yaourt -S lsyncd --noconfirm

This package failed to install on my system with the following error - https://pastebin.com/6VYspd5H

I was able to successfully install this package by issuing export LUA_DIR=/usr/include/lua5.2 before invoking the build itself using yaourt -S lsyncd.