Jerome Gravel-Niquet

Ah, looks like `openssl s_client -cipher 'RSA'` doesn't include some of these... ``` $ openssl s_client -debug -connect debug.fly.dev:443 -cipher 'ECDHE-RSA-AES256-GCM-SHA384' -tls1_2 => sig schemes [RSA_PSS_SHA256, RSA_PSS_SHA384, RSA_PSS_SHA512, RSA_PKCS1_SHA256, RSA_PKCS1_SHA384,...

I've been facing the same issue. I added logs and compiled my own `cargo-hakari`. I found that this happened when trying to find the `pkg-config` in the `computed_map_build`. It's a...

dqlite itself doesn’t need to replace SQLite, it only needs to link to a forked SQLite (which has the same lib name). What I mean by this is: dqlite expects...

#510 might be the cause yes. I'll investigate. I had taken a look at the output previously and it does look right: ``` cargo:rerun-if-env-changed=SQLITE3_INCLUDE_DIR cargo:rerun-if-env-changed=SQLITE3_LIB_DIR cargo:rerun-if-env-changed=SQLITE3_STATIC cargo:link-target=sqlite3 cargo:rustc-link-search=native=/usr/lib/sqlite-replication cargo:rustc-link-lib=sqlite3 ```

Unfortunately, reverting https://github.com/rusqlite/rusqlite/commit/9f009fe1e03c7c428305e88dc5e2269c69c421cf does not help. I guess my only recourse might be to symlink sqlite-replcation over sqlite.

I think I see what's happening. I need to use `LD_LIBRARY_PATH` to point to the `/usr/lib/sqlite-replication` forked sqlite3 lib at runtime or else dqlite will load the non-forked sqlite3 from...

Maybe adding: ```rust println!("cargo:rustc-env=LD_LIBRARY_PATH={}:{}", $SQLITE3_LIB_DIR, $LD_LIBRARY_PATH); ``` (replace the env vars by actual code that fetches them) Might fix #510 too?

@hamelsmu sure, go ahead.

@AkihiroSuda I might end up doing that, but I hoped I wouldn't have to re-implement the same logic present in this package.

I'd be very interested in this. @jacksontj if you can point me at the right bits of code, I'm sure i could come up with a PR. My company would...