You know, whenever I run over a spark plug as I'm driving down the road,
the first thing that goes through my mind is good on them for ruling out
the spark plug as the cause of rough running, and too bad they'll have
to have the valves and rings checked.
On 12/22/23 12:42 AM, Ondřej Surý wrote:
>
This is what I use for my ThreadSanitizer enabled builds. DON'T USE IT
VERBATIM! (It enables ThreadSanitizer and disables optimizations, etc...)
TL;DR The part you want is -Wl,-rpath=$PREFIX/lib
If that doesn't work, experiment with -Wl,--enable-new-dtags vs
-Wl,--disable-new-dtags (see here
On Fri, Dec 22, 2023 at 05:43:09PM +0100, Ond??ej Surý wrote:
>No, you missed my point - I asked why do you pretend to run stuff on RHEL 6
>while in fact you do not because all the critical libraries are self-compiled.
>
>You can run BIND 9 in a container (on RHEL 6) using a still-maintained
Please keep Cc when responding to a message from the mailing list. Re-added,
but redacted most of your email.
No, you missed my point - I asked why do you pretend to run stuff on RHEL 6
while in fact you do not because all the critical libraries are self-compiled.
You can run BIND 9 in a
You need to use rpath to build the libraries that are not in the places where
dynamic linker can find them. This will solve your issue.
But RHEL 6? What’s the point of pretending you are running on old system when
everything you run is new?
Ondrej
--
Ondřej Surý — ISC (He/Him)
My working
I'm compiling bind 9.18.21 on RHEL 6.10. I had to make my own libuv and
openssl packages (and I still need a jemalloc package). I told bind
about them via the PKG_CONFIG_PATH variable, which mostly works. The
problem is in bind-9.18.21/doc/misc which doesn't seem to receive any
information from
I am missing your point. The documentation is readily available from both the RTD and the FTP along with the source tarballs.The sources are in Sphinx doc format, so everyone can modify and build in whatever output format sphinx-build provides:
7 matches
Mail list logo
