linking with `cc` failed: multiple definition of `__muloti4'

[mimoo]

linking with `cc` failed: multiple definition of `__muloti4'

[yiwu-arbug]

The file int128_builtins.cpp seems to be from libc++. We static link with libc++ in our build file: https://github.com/tikv/rust-rocksdb/blob/master/librocksdb_sys/build.rs#L86. Maybe oss-fuzz or some of its other dependency also link with a different version of libc++, causing conflict? Just a wild guess.

[mimoo]

the error seems to indicate this crate no?

Step #4:           /tmp/rustcjXWpoV/liblibrocksdb_sys-eab822076e906c87.rlib(int128_builtins.cpp.o):int128_builtins.cpp:(.text.__muloti4+0x0): first defined here

[yiwu-arbug]

the error seems to indicate this crate no?

Step #4:           /tmp/rustcjXWpoV/liblibrocksdb_sys-eab822076e906c87.rlib(int128_builtins.cpp.o):int128_builtins.cpp:(.text.__muloti4+0x0): first defined here

See my comment above.

[mimoo]

mmm, I'm not sure how to investigate these kind of errors. It looks like libfuzzer uses stdc++ as well: https://github.com/rust-fuzz/libfuzzer/blob/master/build.rs#L14

and it is re-defined in the docker env: https://github.com/google/oss-fuzz/blob/daa9523feefad08cf42a1ab18e5d44f7630055aa/projects/libra/build.sh#L26

[yiwu-arbug]

Discuss with @BusyJay, we should provide static link with libc++ as a feature, not by default. The original purpose of static link was to make binaries can run on system without installing libc++ dylib.

[yiwu-arbug]

@mimoo Feel free to submit a PR for fix.