Re: Problems building bind 9.18.1 on FreeBSD
> On 25. 3. 2022, at 16:16, Borja Marcos wrote: > > That said (and this is just an opinion) with all due respect of course, if > bind evolves in a way that makes > it much harder to build on non Linux systems, I am concerned. That’s simply not true in general. We stopped supporting **dead** systems, but we do not prevent anybody from doing the porting. Just check this: https://buildd.debian.org/status/package.php?p=bind9 The only thing failing is GNU Hurd, sh4 and m68k architectures. These are issues related to MacPorts: https://gitlab.isc.org/isc-projects/bind9/-/issues?scope=all=closed=Macports For all of these, we either prepared and/or merged a fix or provided a workaround (for the second issue on the list, you need to run autoreconf -if). 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. > Cheers, > > > > > Borja. > > -- 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 building bind 9.18.1 on FreeBSD
> On 25. 3. 2022, at 17:43, Dennis Clarke via bind-users > wrote: > > The entire ISC *preocess* has become gradually more toxic for at > least a decade. The only thing that’s toxic here is your current and previous communication to the bind-users mailing list. Please, stop. > Many systems and architectures are slowly dropped > and they fall to the wayside to be forgotten and abandoned. Yes, and that’s a good thing. Also you cannot expect so few developers to support every possible nook and cranny you can find in the operating system world. Naturally, the developers pick the stuff they are going to work on. The supported and unsupported platforms are clearly described in the documentation: https://bind9.readthedocs.io/en/v9_18_1/requirements.html#supported-platforms including a paragraph on the community maintained platforms: > These systems may not all have the required dependencies for building BIND > easily available, although it will be possible in many cases to compile those > directly from source. The community and interested parties may wish to help > with maintenance, and we welcome patch contributions, although we cannot > guarantee that we will accept them. All contributions will be assessed against > the risk of adverse effect on officially supported platforms. The requirements for building BIND 9 are aligned with what you would expect by system created in 2022. > Regardless if you have a decent compiler or really substantial processors and > memory and various standard compliant headers etc. One may file a bug > report and then be politely told to go away. Stop spreading FUD. I cannot find any issues opened by you that would support your claims. The last time your communication involved accusations of “gnuisms” (which I showed you that are not gnuisms) and system tests. The system tests have more requirements than the standard build process and we (the developers) are more lenient when it comes to dependencies to build and run system tests. > Expect that. That is what will happen. And more FUD. This is not simply not true. We do carefully consider every issue. We are just not going to impose more work and more pain on us and use C89 to implement everything from scratch to just support some niche system. We focus on building DNS server, which means it’s OK to use modern C specification, external libraries (networking, TLS, HTTP/2, etc…) because we should do what we understand best - DNS. But as a matter of fact, we have contributed back to many of the libraries we are using to build BIND 9 (libuv, cmocka, …). This is how the open source should work - everybody improving the reusable components which works for everybody’s benefit. > The build process has become more toxic and complicated > and even outright obfuscated to the point that it is hopeless This is just pure nonsense. On the contrary, the build system in 9.18+ become more standard - it uses autoconf + automake + libtool and the syntax is more declarative (to the extent possible with automake). That makes the build system easier to understand and easier to improve. > to even bother looking at a system running FreeBSD on RISC-V or some > other UNIX on just about any architecture. Hmm, there are no issues opened about RISC-V support: https://gitlab.isc.org/search?search=RISC-V So, more FUD? In fact, we are happy to support modern architectures when they become commodity. I am not aware of anything that would intentionally prevent building modern BIND 9 on RISC-V or any other new architectures like OpenPOWER. There’s very little code in BIND 9 that’s architecture dependent. In fact, the only place that I am aware of is isc_rwlock_pause(), that in fact has a graceful fallback - if the processor “pause” is not available it does nothing. > Even Python3 was slammed into the mess > for a code base that was always pure clean portable C. No, that’s not true. Python3 was optional in BIND 9.16 and the Python components were replaced dnssec-policy (in C) in 9.18+. We require python + pytest as testing framework for system tests. The system tests are primarily meant for developers. > My opinion is > that ISC is all about the "Support Subscription" business and quite > frankly it stopped being any sort of a welcome "community" a long time > ago. Stop spreading FUD. You are the one behaving rude and arrogant here. > To the point that I now consider it a waste of time to even bother > dealing with BIND. That’s obviously not true since you still lurk here. Maybe you should consider putting your foot where your mouth is? > If it works ( at all ) on the future FreeBSD 13.1 > release then be happy and say nothing. Don't expect it to stay that way. More FUD not supported by any evidence. FreeBSD is one of our primary platforms. > Expect future problems and more toxic traffic Even more FUD not supported by any evidence at all. > until it is all just a Linux SystemD service. It’s **systemd**, not SystemD. And we are not
Re: Problems building bind 9.18.1 on FreeBSD
On 3/25/22 09:37, The Doctor via bind-users wrote: On Fri, Mar 25, 2022 at 11:49:54AM +0100, Borja Marcos wrote: Following up on this subject, looks like there were substantial changes to the build process for 9.18.1? The port maintainers seem to be having a hard time with it. You got that right. One include is messed up and so are some libraries and man pages. The entire ISC *preocess* has become gradually more toxic for at least a decade. Many systems and architectures are slowly dropped and they fall to the wayside to be forgotten and abandoned. Regardless if you have a decent compiler or really substantial processors and memory and various standard compliant headers etc. One may file a bug report and then be politely told to go away. Expect that. That is what will happen. The build process has become more toxic and complicated and even outright obfuscated to the point that it is hopeless to even bother looking at a system running FreeBSD on RISC-V or some other UNIX on just about any architecture. Even Python3 was slammed into the mess for a code base that was always pure clean portable C. My opinion is that ISC is all about the "Support Subscription" business and quite frankly it stopped being any sort of a welcome "community" a long time ago. To the point that I now consider it a waste of time to even bother dealing with BIND. If it works ( at all ) on the future FreeBSD 13.1 release then be happy and say nothing. Don't expect it to stay that way. Expect future problems and more toxic traffic until it is all just a Linux SystemD service. -- Dennis Clarke RISC-V/SPARC/PPC/ARM/CISC UNIX and Linux spoken GreyBeard and suspenders optional -- 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 building bind 9.18.1 on FreeBSD
> On 25. 3. 2022, at 16:16, Borja Marcos wrote: > > That said (and this is just an opinion) with all due respect of course, if > bind evolves in a way that makes > it much harder to build on non Linux systems, I am concerned. That’s certainly not true for systems listed in the Supported Platforms: https://bind9.readthedocs.io/en/v9_18_1/requirements.html#supported-platforms 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. -- 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 building bind 9.18.1 on FreeBSD
> On 25 Mar 2022, at 14:34, Ondřej Surý wrote: > >> On 25. 3. 2022, at 11:49, Borja Marcos wrote: >> >> Following up on this subject, looks like there were substantial changes to >> the build process for 9.18.1? > > Yes. Thanks. I was just wondering. > >> The port maintainers seem to be having a hard time with it. > > There’s an issue tracker for any bugs found. Making general statements like > this is neither helpful > to those “maintainers” (they can speak for themselves, do they) nor the the > upstream developers. My apologies. I am not intending to be offensive of course! I am just a spectator (I am using bind but I am not one of the maintainers nor I have time for that). That said (and this is just an opinion) with all due respect of course, if bind evolves in a way that makes it much harder to build on non Linux systems, I am concerned. Cheers, Borja. -- 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 building bind 9.18.1 on FreeBSD
On Fri, Mar 25, 2022 at 11:49:54AM +0100, Borja Marcos wrote: > Following up on this subject, looks like there were substantial changes to > the build process for 9.18.1? The port maintainers > seem to be having a hard time with it. > > You got that right. One include is messed up and so are some libraries and man pages. > Cheers, > > > > > > Borja. > > -- > 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 -- Member - Liberal International This is doctor@@nl2k.ab.ca Ici doctor@@nl2k.ab.ca Yahweh, Queen & country!Never Satan President Republic!Beware AntiChrist rising! Look at Psalms 14 and 53 on Atheism https://www.empire.kred/ROOTNK?t=94a1f39b Doing something easy and useless is the call of the world. -unknown Beware https://mindspring.com -- 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 building bind 9.18.1 on FreeBSD
> On 25. 3. 2022, at 11:49, Borja Marcos wrote: > > Following up on this subject, looks like there were substantial changes to > the build process for 9.18.1? Yes. > The port maintainers seem to be having a hard time with it. There’s an issue tracker for any bugs found. Making general statements like this is neither helpful to those “maintainers” (they can speak for themselves, do they) nor the the upstream developers. Ondrej -- 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. -- 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 building bind 9.18.1 on FreeBSD
Following up on this subject, looks like there were substantial changes to the build process for 9.18.1? The port maintainers seem to be having a hard time with it. Cheers, Borja. -- 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 building bind 9.18.1 on FreeBSD
> On 17 Mar 2022, at 10:41, Petr Špaček wrote:
*** Error code 2
>>> Interesting!
>>>
>>> How do you build it?
>> Pretty straightforward.
>> ./configure with some options,
>> ./configure --disable-linux-caps --localstatedir=/var
>> --sysconfdir=/usr/local/etc/namedb --with-dlopen=yes --with-libxml2
>> --with-openssl=/usr --enable-dnsrps --with-readline=libedit --enable-dnstap
>> --disable-fixed-rrset --disable-geoip --without-maxminddb --without-gssapi
>> --with-libidn2=/usr/local --with-json-c --disable-largefile
>> --with-lmdb=/usr/local --disable-querytrace --enable-tcp-fastopen
>> --prefix=/usr/local --mandir=/usr/local/man --disable-silent-rules
>> --infodir=/usr/local/share/info/ --build=amd64-portbld-freebsd13.0
>> make
>> I built 9.18.0 without any issues, it was as straightforward as it can be!
>> Make is the FreeBSD version, not GNU Make.
>
> This is even more interesting. Can you retry with GNU Make to see if the
> substitution will work?
Sure!
So “make” was making war instead of love.
With GNU Make (latest version in ports) it compiled and Sphinx didn’t complain.
And of course I ran configure after installing Sphinx.
Making all in man
gmake[3]: Entering directory '/usr/home/borjam/src/bind-9.18.1/doc/man'
echo ".. |rndc_conf| replace:: ``@sysconfdir@/rndc.conf``\n.. |rndc_key|
replace:: ``@sysconfdir@/rndc.key``\n.. |named_conf| replace::
``@sysconfdir@/named.conf``\n.. |bind_keys| replace::
``@sysconfdir@/bind.keys``\n.. |named_pid| replace::
``@runstatedir@/named.pid``\n.. |session_key| replace::
``@runstatedir@/session.key``"
.. |rndc_conf| replace:: @sysconfdir@/rndc.conf\n.. |rndc_key| replace::
@sysconfdir@/rndc.key\n.. |named_conf| replace:: @sysconfdir@/named.conf\n..
|bind_keys| replace:: @sysconfdir@/bind.keys\n.. |named_pid| replace::
@runstatedir@/named.pid\n.. |session_key| replace:: @runstatedir@/session.key
/usr/local/bin/sphinx-build -b man -d ./_build/.doctrees/man -W -c . -a -n -D
version="@""PACKAGE_VERSION@" -D today="@""RELEASE_DATE@" -D
release="@""PACKAGE_VERSION@" -D rst_epilog="$(printf "${man_RST_EPILOG}")" .
./_build/man
Running Sphinx v4.3.1
making output directory... done
building [mo]: all of 0 po files
building [man]: all source files
updating environment: [new config] 34 added, 0 changed, 0 removed
reading sources... [100%] tsig-keygen
looking for now-outdated files... none found
pickling environment... done
checking consistency... done
writing... arpaname.1 { } ddns-confgen.8 { } delv.1 { } dig.1 { } dnssec-cds.1
{ } dnssec-dsfromkey.1 { } dnssec-importkey.1 { } dnssec-keyfromlabel.1 { }
dnssec-keygen.1 { } dnssec-revoke.1 { } dnssec-settime.1 { } dnssec-signzone.1
{ } dnssec-verify.1 { } dnstap-read.1 { } filter-.8 { } filter-a.8 { }
host.1 { } mdig.1 { } named-checkconf.1 { } named-checkzone.1 { }
named-compilezone.1 { } named-journalprint.1 { } named-nzd2nzf.1 { }
named-rrchecker.1 { } named.conf.5 { } named.8 { } nsec3hash.1 { } nslookup.1 {
} nsupdate.1 { } rndc-confgen.8 { } rndc.conf.5 { } rndc.8 { } tsig-keygen.8 {
} done
build succeeded.
The manual pages are in _build/man.
---
And for comparison this is what happened with FreeBSD stock make.
Making all in man
echo ""
/usr/local/bin/sphinx-build -b man -d ./_build/.doctrees/man -W
-c .-a -n
-D version="@""PACKAGE_VERSION@"-D today="@""RELEASE_DATE@"
-D release="@""PACKAGE_VERSION@"-D rst_epilog="$(printf
"${man_RST_EPILOG}")" . ./_build/man
Running Sphinx v4.3.1
making output directory... done
building [mo]: all of 0 po files
building [man]: all source files
updating environment: [new config] 34 added, 0 changed, 0 removed
reading sources... [100%] tsig-keygen
Warning, treated as error:
../../bin/delv/delv.rst:99:Undefined substitution referenced: "bind_keys".
*** Error code 2
Stop.
make[3]: stopped in /usr/home/borjam/src/bind-9.18.1/doc/man
*** Error code 1
Stop.
make[2]: stopped in /usr/home/borjam/src/bind-9.18.1/doc
*** Error code 1
Stop.
make[1]: stopped in /usr/home/borjam/src/bind-9.18.1
*** Error code 1
Stop.
make: stopped in /usr/home/borjam/src/bind-9.18.1
Cheers,
Borja.
--
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 building bind 9.18.1 on FreeBSD
On 17. 03. 22 10:02, Borja Marcos wrote: On 17 Mar 2022, at 08:59, Petr Špaček wrote: Hello, On 17. 03. 22 8:49, Borja Marcos wrote: Trying to compile bind 9.18.1 on FreeBSD I am stumbling upon a really silly problem. Getting plenty of errors like this building the man pages. building [man]: all source files updating environment: [new config] 34 added, 0 changed, 0 removed reading sources... [100%] tsig-keygen Warning, treated as error: ../../bin/named/named.conf.rst:901:Undefined substitution referenced: "named_conf". *** Error code 2 Interesting! How do you build it? Pretty straightforward. ./configure with some options, ./configure --disable-linux-caps --localstatedir=/var --sysconfdir=/usr/local/etc/namedb --with-dlopen=yes --with-libxml2 --with-openssl=/usr --enable-dnsrps --with-readline=libedit --enable-dnstap --disable-fixed-rrset --disable-geoip --without-maxminddb --without-gssapi --with-libidn2=/usr/local --with-json-c --disable-largefile --with-lmdb=/usr/local --disable-querytrace --enable-tcp-fastopen --prefix=/usr/local --mandir=/usr/local/man --disable-silent-rules --infodir=/usr/local/share/info/ --build=amd64-portbld-freebsd13.0 make I built 9.18.0 without any issues, it was as straightforward as it can be! Make is the FreeBSD version, not GNU Make. This is even more interesting. Can you retry with GNU Make to see if the substitution will work? Thanks. -- Petr Špaček -- 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 building bind 9.18.1 on FreeBSD
> On 17 Mar 2022, at 08:59, Petr Špaček wrote: > > Hello, > > On 17. 03. 22 8:49, Borja Marcos wrote: >> Trying to compile bind 9.18.1 on FreeBSD I am stumbling upon a really silly >> problem. Getting plenty of errors like this >> building the man pages. >> building [man]: all source files >> updating environment: [new config] 34 added, 0 changed, 0 removed >> reading sources... [100%] tsig-keygen >> Warning, treated as error: >> ../../bin/named/named.conf.rst:901:Undefined substitution referenced: >> "named_conf". >> *** Error code 2 > > Interesting! > > How do you build it? Pretty straightforward. ./configure with some options, ./configure --disable-linux-caps --localstatedir=/var --sysconfdir=/usr/local/etc/namedb --with-dlopen=yes --with-libxml2 --with-openssl=/usr --enable-dnsrps --with-readline=libedit --enable-dnstap --disable-fixed-rrset --disable-geoip --without-maxminddb --without-gssapi --with-libidn2=/usr/local --with-json-c --disable-largefile --with-lmdb=/usr/local --disable-querytrace --enable-tcp-fastopen --prefix=/usr/local --mandir=/usr/local/man --disable-silent-rules --infodir=/usr/local/share/info/ --build=amd64-portbld-freebsd13.0 make I built 9.18.0 without any issues, it was as straightforward as it can be! Make is the FreeBSD version, not GNU Make. > Please provide exact sequence of commands along with Sphinx and make version > information. I had Sphinx sphinx-3.5.2_1,1 built with Python 3.7.12 I deleted Python 3.7 and Sphinx, rebuilt with Python 3.8.12, Sphinx version 4.3.1, same result. > >> I wonder whether I am missing some needed package. Also, is it really >> necessary to complicate the generation of man pages to >> this extent? > > Depends on who you ask. There are people who like to have correct path names > in the the man pages, and other group of people don't that much :shrug:. I understand it is important to have proper documentation. But I wonder whether things have gone out of control with dependencies. Especially for such an important piece of software as Bind 9. But there are plenty of simple ways to achieve that substitution. Per Ondřej Surý’s suggestion (I didn’t know you can avoid using Sphinx) I have removed Sphinx, with was installed as a dependency from another port, and now it builds perfectly. THANK YOU! Anyway, with all due respect I would suggest to examine dependencies carefully. Such an important package should keep dependencies to the really mandatory ones. Or documentation should state somewhere that you don’t need Sphinx, _or_ there should be a configure option to ignore it. Cheers, Borja. -- 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 building bind 9.18.1 on FreeBSD
You don’t have to have sphinx-build installed for manpages to be generated. There’s nothing complicated in the build system. All is pretty standard stuff. Ondřej -- 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 17. 3. 2022, at 8:59, Petr Špaček wrote: >> Also, is it really necessary to complicate the generation of man pages to >> this extent? > > Depends on who you ask. There are people who like to have correct path names > in the the man pages, and other group of people don't that much :shrug:. -- 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 building bind 9.18.1 on FreeBSD
Hello, On 17. 03. 22 8:49, Borja Marcos wrote: Trying to compile bind 9.18.1 on FreeBSD I am stumbling upon a really silly problem. Getting plenty of errors like this building the man pages. building [man]: all source files updating environment: [new config] 34 added, 0 changed, 0 removed reading sources... [100%] tsig-keygen Warning, treated as error: ../../bin/named/named.conf.rst:901:Undefined substitution referenced: "named_conf". *** Error code 2 Interesting! How do you build it? Please provide exact sequence of commands along with Sphinx and make version information. I wonder whether I am missing some needed package. Also, is it really necessary to complicate the generation of man pages to this extent? Depends on who you ask. There are people who like to have correct path names in the the man pages, and other group of people don't that much :shrug:. Petr Špaček -- 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
