Simson L. Garfinkel

Is this resolved?

@brianc - I think that the default should be not to build java unless requested, since most TSK users probably do not require the Java bindings. As of #3038, you...

Hi. 1. Can you give us a test case that demonstrates this problem? 2. Do you think that it would be useful to have a mode in raw.c in which...

@joachimmetz - any idea why this is happening? ``` /usr/bin/ld: /usr/lib/gcc/x86_64-linux-gnu/11/../../../x86_64-linux-gnu/libqcow.a(libbfio_handle.o): in function `libbfio_handle_clone': (.text+0x1180): multiple definition of `libbfio_handle_clone'; /usr/lib/gcc/x86_64-linux-gnu/11/../../../x86_64-linux-gnu/libbfio.a(libbfio_handle.o):(.text+0x1050): first defined here ```

Can you try removing `--without-afflib --without-libcrypto --without-libewf --without-libvhdi --without-libvmdk` and see what happens?

License implications other than the need to distribute the source code? On Wed, Oct 16, 2024 at 1:23 PM Joachim Metz ***@***.***> wrote: > For full static tooling builds you...

If you are just using the static tools and not distributing them, the issue doesn't apply. But I think that @joachimmetz is writing that some libraries may have incompatible licenses....

> I'm not seeing the connection between an unspecified license problem and what is making this PR fail to build, which is multiply defined symbols. Two different issues. The build...

Well, the static build could make a copy of the library and then use the archive manager tool to pull out the problematic object files. Any other suggestions? On Thu,...

updating branch to get better build system.