Hilko Bengen

I am not quite sure about `New()`. Other than that, the `error()` method is only called in actual error paths, i.e. if the corresponding Augeas C API function has returned...

Just tried to reproduce the error. Apparently, the directory must exist. Tried the following in an empty directory (augeas 1.8, Debian/stretch chroot): ``` $ augtool --root . augtool> set /augeas/load/Xmgmt/lens...

Digging further... a simple C test program to reproduce this issue behaves correctly in the sense that -1 is returned. ``` c #include #include #include int main(int argc, char** argv)...

As long as there is no CGO support for Go's WASM backend, I don't see an **easy** solution. I think that libyara-wasm may be a good start, but you'd have...

Are you expecting the file to be found relative to the current working directory of your program? Or are you expecting it to be found relative to the directory in...

~Curious. I just ran into the problem you described today. Without having looked at the commit history, I'm pretty sure that this has to do with a behavior change in...

I just created `a.yar` containing the following two lines: ```yara include "b.yar" include "subdir/c.yar" ``` Both included files exist and are empty. I can compile this using `yarac` from both...

@uggwar The problem you encountered may have to do with your ruleset resulting in multiple errors: When I try to compile `index.yar` from with `yarac` from a YARA build without...

@uggwar Ping? Do you think that my analysis is correct?

The `log2` function needs libm, so I suppose that the compiler switch `-lm` is missing there. For x86 it seems that the linker is only finding libyara.a for the wrong...