Re: version errata Re: Remove PDF-related bits from the build system
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: > Are you really complaining about the lack of handholding because you > want to build the documentation yourself and just can’t download it? > Because it really seems like the case here. I concerned you've lost control of your build. However it does look correct in 9.19.19. -- Fred Morris -- Visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from this list ISC funds the development of this software with paid support subscriptions. Contact us at https://www.isc.org/contact/ for more information. bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users
Re: Problems with openssl pkgconfig in bind 9.18.21 (but probably all 9.18) {External}
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 for explanation:
https://stackoverflow.com/questions/52018092/how-to-set-rpath-and-runpath-with-gcc-ld)
Also there's always an option to add the paths where you installed the updated
libraries to /etc/ld.so.conf (or to /etc/ld.so.conf.d/local.conf).
Cheers,
Ondřej
$ cat tsan-env
#!/bin/sh
export CC="${CC:-clang-18}"
export PREFIX="$HOME/.tsan-${CC}"
case "$CC" in
clang-*) export CXX=clang++-${CC#clang-} ;;
gcc-*) export CXX=g++-${CC#gcc-} ;;
*) exit 1 ;;
esac
export CFLAGS="$CFLAGS -rdynamic -ggdb -O0 -Wno-deprecated-declarations
-fno-omit-frame-pointer -fno-optimize-sibling-calls -fPIC -fsanitize=thread
-Wl,-rpath=$PREFIX/lib -Wl,--enable-new-dtags"
export CXXFLAGS="$CXXFLAGS -rdynamic -ggdb -O0 -Wno-deprecated-declarations
-fno-omit-frame-pointer -fno-optimize-sibling-calls -fPIC -fsanitize=thread
-Wl,-rpath=$PREFIX/lib -Wl,--enable-new-dtags"
export LDFLAGS="$LDFLAGS -fPIE -fsanitize=thread -Wl,-rpath=$PREFIX/lib
-Wl,--enable-new-dtags"
export PKG_CONFIG_PATH="$PREFIX/lib/pkgconfig:$PKG_CONFIG_PATH"
export PATH="$PREFIX/sbin:$PREFIX/bin:$PATH"
$ cat build
#!/bin/sh
. ./tsan-env
rm -rf "$PREFIX"
# OpenSSL (skip, it takes too long)
#./config no-asm no-ssl3 no-comp no-weak-ssl-ciphers --prefix="$PREFIX"
&& \
(cd openssl && \
git clean -xdf && \
git reset --hard HEAD && \
./config no-ssl3 no-weak-ssl-ciphers --prefix="$PREFIX"
--libdir="$PREFIX/lib" && \
make -j && \
make install_sw)
# libuv
(cd libuv && \
git clean -xdf && \
git reset --hard HEAD && \
./autogen.sh && \
./configure --prefix="$PREFIX" && \
make -j && \
make install
)
# userspace-rcu
(cd userspace-rcu && \
git clean -xdf && \
git reset --hard HEAD && \
./bootstrap && \
./configure --prefix="$PREFIX" --enable-compiler-atomic-builtins
--disable-legacy-mb && \
make -j && \
make install
)
--
Ondřej Surý (He/Him)
ond...@isc.org
My working hours and your working hours may be different. Please do not feel
obligated to reply outside your normal working hours.
> On 22. 12. 2023, at 16:44, William D. Colburn wrote:
>
> Your build system did say to manually change it. I used an environment
> variable, but thought (still think actually) that yhour build system
> should honor pkgconfig for finding packages.
--
Visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from
this list
ISC funds the development of this software with paid support subscriptions.
Contact us at https://www.isc.org/contact/ for more information.
bind-users mailing list
bind-users@lists.isc.org
https://lists.isc.org/mailman/listinfo/bind-users
Re: Problems with openssl pkgconfig in bind 9.18.21 (but probably all 9.18) {External}
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 >distribution, where you don???t have to self-watch the required upgrades for >all the dependencies (libuv, OpenSSL, and others???) There is a lot of momentum in our organization. Take timekeeping. There is local time, UTC, TAI, GPS time, Julian time, modified Julian time, nutation sidereal time, mean sideral time, Greenwich sideral time, modified local sidereal time, and probably more I can't remember. We have to keep track of contintal drift because of General Relativity with regards to timekeeping, and our most demanding applications require femtosecond accuracies in the clocks (which isn't possible with today's technology). Not only do we use all of those timekeeping standards in different places, but we also invented our own timekeeping standard back in the 1970s that we still use and is one of our main ways of keeping track of things. Some groups here here don't trust DHCP. They started out soldering and wirewraping IP addresses into boards that are inaccessible in the bowels of the machines, but have progressed to selectable IP addresses controlled by dip switches inside brass boxes that have up to 206 screws holding them closed. The modern data stream uses ethernet, but I'm told not ethernet collisions. It was deemed better to time every packet from every device so that no collisions ever happen in the ethernet network. But containers are something we plan to try soon! This coming calendar year actually. Using one for RHEL6.5 to support Xilinx is high on my list. --Schlake Sysadmin IV, NRAO Work: 575-835-7281 (BACK IN THE OFFICE!) Cell: 575-517-5668 (out of work hours) -- Visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from this list ISC funds the development of this software with paid support subscriptions. Contact us at https://www.isc.org/contact/ for more information. bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users
Re: Problems with openssl pkgconfig in bind 9.18.21 (but probably all 9.18) {External}
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 container (on RHEL 6) using a still-maintained distribution, where you don’t have to self-watch the required upgrades for all the dependencies (libuv, OpenSSL, and others…) Ondrej -- Ondřej Surý — ISC (He/Him) My working hours and your working hours may be different. Please do not feel obligated to reply outside your normal working hours. > On 22. 12. 2023, at 16:50, William D. Colburn wrote: > RHEL6.10 is pretty new in the grand scheme of things. -- Visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from this list ISC funds the development of this software with paid support subscriptions. Contact us at https://www.isc.org/contact/ for more information. bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users
Re: Problems with openssl pkgconfig in bind 9.18.21 (but probably all 9.18)
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 hours and your working hours may be different. Please do not feel obligated to reply outside your normal working hours. > On 22. 12. 2023, at 16:14, William D. Colburn wrote: > > 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 the build system about the location of where openssl > is. I got around it by adding an LD_LIBRARY_PATH= to the initial make > command that pointed into where I had installed openssl 3.2.0, but that's a > little fragile. It also means I don't know if doc/misc is the only > place with this problem. > > And no, I can't just upgrade the computer. But we did manage to > decomission a vendor bind on a Sun workstation in a jungle on an island > in the Pacific ocean a couple of months ago, so you can take some joy > from that. :) > > I never what or how much information to send and I always get it wrong, > so I'll just wait for Ondrej (I have no idea how to type that correctly) > to chastise me and then forward on whatever else you need. Also :) > > --Schlake > Sysadmin IV, NRAO > Work: 575-835-7281 (BACK IN THE OFFICE!) > Cell: 575-517-5668 (out of work hours) > -- > Visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from > this list > > ISC funds the development of this software with paid support subscriptions. > Contact us at https://www.isc.org/contact/ for more information. > > > bind-users mailing list > bind-users@lists.isc.org > https://lists.isc.org/mailman/listinfo/bind-users -- Visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from this list ISC funds the development of this software with paid support subscriptions. Contact us at https://www.isc.org/contact/ for more information. bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users
Problems with openssl pkgconfig in bind 9.18.21 (but probably all 9.18)
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 the build system about the location of where openssl is. I got around it by adding an LD_LIBRARY_PATH= to the initial make command that pointed into where I had installed openssl 3.2.0, but that's a little fragile. It also means I don't know if doc/misc is the only place with this problem. And no, I can't just upgrade the computer. But we did manage to decomission a vendor bind on a Sun workstation in a jungle on an island in the Pacific ocean a couple of months ago, so you can take some joy from that. :) I never what or how much information to send and I always get it wrong, so I'll just wait for Ondrej (I have no idea how to type that correctly) to chastise me and then forward on whatever else you need. Also :) --Schlake Sysadmin IV, NRAO Work: 575-835-7281 (BACK IN THE OFFICE!) Cell: 575-517-5668 (out of work hours) -- Visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from this list ISC funds the development of this software with paid support subscriptions. Contact us at https://www.isc.org/contact/ for more information. bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users
Re: version errata Re: Remove PDF-related bits from the build system
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: https://www.sphinx-doc.org/en/master/man/sphinx-build.htmlAre you really complaining about the lack of handholding because you want to build the documentation yourself and just can’t download it? Because it really seems like the case here.Ondrej--Ondřej Surý — ISC (He/Him)My working hours and your working hours may be different. Please do not feel obligated to reply outside your normal working hours.On 21. 12. 2023, at 21:32, Fred Morris wrote: Just pulled the 9.18.21 tarball and checked, same thing. m3047@sophia:/opt/downloads/bind-9.18.21> grep -B18 '> Change log' README.md ### Documentation The *BIND 9 Administrator Reference Manual* (ARM) is included with the source distribution, and in .rst format, in the `doc/arm` directory. HTML and PDF versions are automatically generated and can be viewed at [https://bind9.readthedocs.io/en/latest/index.html](https://bind9.readthedocs.io/en/latest/index.html). Man pages for some of the programs in the BIND 9 distribution are also included in the BIND ARM. Frequently (and not-so-frequently) asked questions and their answers can be found in the ISC Knowledgebase at [https://kb.isc.org](https://kb.isc.org). Additional information on various subjects can be found in other `README` files throughout the source tree. ### Change log m3047@sophia:/opt/downloads/bind-9.18.21> sum README.md 3778511 m3047@sophia:/opt/downloads/bind-9.18.21> md5sum README.md c4e08add5a135ce2573483eb0e5b1207 README.md m3047@sophia:/opt/downloads/bind-9.18.21> sha256sum README.md 080e914decc2ed554d8887b0f719b82736c45380b987f23b3eba4ef7418f03f3 README.md On 12/21/23 12:24 PM, Fred Morris wrote: No, I was correct the first time, but I had the wrong version. It is a 9.18.9 tarball, not 9.18.21. Checksums are correct for that README.md. On 12/21/23 12:18 PM, Fred Morris wrote: I'm sorry 9.18.9 was the version where I discovered that the build didn't build the PDF, and all it says is ### Building BIND 9 For information about building BIND 9, see the ["Building BIND 9"](doc/arm/build.inc.rst) section in the BIND 9 Administrator Reference Manual. The checksums correct for that version of README.md. I think I must have mistakenly cut & pasted from the source tree in GitLab for 9.18. On 12/21/23 10:50 AM, Fred Morris wrote: On 12/21/23 10:08 AM, Ondřej Surý wrote: In the commit you referenced: https://gitlab.isc.org/isc-projects/bind9/-/commit/561a83a29182b00bda9237ae30343d76a68dcdf4#8ec9a00bfd09b3190ac6b22251dbb1aa95a0579d_147_147 On 21. 12. 2023, at 18:59, Fred Morris wrote: According to the commit (https://gitlab.isc.org/isc-projects/bind9/-/commit/561a83a29182b00bda9237ae30343d76a68dcdf4) Not sure how this works, but I'm looking at what came out of the 9.18.21 tarball and it doesn't build the PDF, and neither does README.md contain the build instructions: ### Documentation The *BIND 9 Administrator Reference Manual* (ARM) is included with the source distribution, and in .rst format, in the `doc/arm` directory. HTML and PDF versions are automatically generated and can be viewed at [https://bind9.readthedocs.io/en/latest/index.html](https://bind9.readthedocs.io/en/latest/index.html). Man pages for some of the programs in the BIND 9 distribution are also included in the BIND ARM. Frequently (and not-so-frequently) asked questions and their answers can be found in the ISC Knowledgebase at [https://kb.isc.org](https://kb.isc.org). Additional information on various subjects can be found in other `README` files throughout the source tree. # sum README.md 30538 11 README.md # md5sum README.md 4b7916a768467c54d1d1f0fd96cff505 README.md # sha256sum README.md ed0a9280fe2f1d1fd6616f95184c6901709e79897b22205e5200bf1f5a7b1bea README.md -- Fred Morris **PerlJacket** deleted text/html part. -- Visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from this listISC funds the development of this software with paid support subscriptions. Contact us at https://www.isc.org/contact/ for more information.bind-users mailing listbind-users@lists.isc.orghttps://lists.isc.org/mailman/listinfo/bind-users-- Visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from this
