Re: Compilation problems with 9.16.30 {External}
Maybe somebody set the CC in the default environment? You can pass the override by doing ./configure CC=pick_your_compiler (instead of environment), that way it’s recorded in the config.log and config.status. As for RHEL6 - you might not be able to compile 9.18 at all unless you home-cook all the dependencies (which you are probably doing anyway), so what’s the point of having this old “chassis” when you are welding new bits on top of it? Perhaps running BIND 9 in a container would be easier? 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 15. 6. 2022, at 21:09, William D. Colburn wrote: > > I didn't specify gnu99, but it did come from somewhere. -- 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: Compilation problems with 9.16.30 {External}
On Wed, Jun 15, 2022 at 08:55:59PM +0200, Ond??ej Surý wrote: >I believe the main problem might be that you were enforcing C99 with `CC=gcc >-std=gnu99`. BIND 9.16 requires C11 compatible compiler. (Well, apart from >using system past it???s respective end-of-life.) > >When I asked for exact configure invocation (options used), I asked for a >reason??? I didn't specify gnu99, but it did come from somewhere. I invoked configure and compiled as such ($REVERE was ""): PKG_CONFIG_PATH=/opt/services/libuv/lib/pkgconfig/:$PKG_CONFIG_PATH \ ./configure --disable-openssl-version-check \ --prefix=/opt/services/named/bind-$VERSION --sysconfdir=/etc \ --localstatedir=/var --disable-ipv6 --with-openssl=yes $REVERE || die failed to configure PKG_CONFIG_PATH=/opt/services/libuv/lib/pkgconfig/:$PKG_CONFIG_PATH make || die make failed PKG_CONFIG_PATH=/opt/services/libuv/lib/pkgconfig/:$PKG_CONFIG_PATH \ make install -e sysconfdir=/opt/services/named/etc -e \ localstatedir=/opt/services/named/var || die make install failed rsync -a /opt/services/libuv/lib/ /opt/services/named/bind-$VERSION/lib/ RHEL 6 is barely out of service! We will probably be running it until the year 2032 because we have no way to replace it. We are getting close to not needing our CP/M machines anymore, and dream of the day that we can replace all the equipment that can only be controlled/operated by an Apple []e. --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: Compilation problems with 9.16.30 {External}
I believe the main problem might be that you were enforcing C99 with `CC=gcc -std=gnu99`. BIND 9.16 requires C11 compatible compiler. (Well, apart from using system past it’s respective end-of-life.) When I asked for exact configure invocation (options used), I asked for a reason… Cheers, -- 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 15. 6. 2022, at 20:31, William D. Colburn wrote: > Compiler: gcc -std=gnu99 >gcc (GCC) 4.4.7 20120313 (Red Hat 4.4.7-23) -- 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: Compilation problems with 9.16.30 {External}
On Wed, Jun 15, 2022 at 07:22:50PM +0200, Ond??ej Surý wrote:
>You need to provide little bit more detail about the environment - operating
>system, compiler used, output of ./configure (including the options used).
>
>There???s no such thing as too many *relevant* details???
I'll trim down the configurte output:
===
Configuration summary:
---
Optional features enabled:
Mutex lock type: adaptive
GSS-API (--with-gssapi)
IPv6 support (--enable-ipv6)
Python tools (--with-python)
XML statistics (--with-libxml2)
HTTP zlib compression (--with-zlib)
Print backtrace on crash (--enable-backtrace)
Use symbol table for backtrace, named only (--enable-symtable)
DNSSEC validation active by default (--enable-auto-validation)
Dynamically loadable zone (DLZ) drivers:
None
---
Features disabled or unavailable on this platform:
Small-system tuning (--with-tuning)
Allow 'dnstap' packet logging (--enable-dnstap)
GeoIP2 access control (--enable-geoip)
DNS Response Policy Service interface (--enable-dnsrps)
Allow 'fixed' rrset-order (--enable-fixed-rrset)
Using PKCS#11 for Public-Key Cryptography (--with-native-pkcs11)
Very verbose query trace logging (--enable-querytrace)
Use GNU libtool (--with-libtool)
CMocka Unit Testing Framework (--with-cmocka)
JSON statistics (--with-json-c)
LMDB database to store configuration for 'addzone' zones (--with-lmdb)
IDN support (--with-libidn2)
---
Configured paths:
prefix: /tmp/bind
sysconfdir: /etc
localstatedir: /var
---
Compiler: gcc -std=gnu99
gcc (GCC) 4.4.7 20120313 (Red Hat 4.4.7-23)
Copyright (C) 2010 Free Software Foundation, Inc.
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
Unrecognized options:
--disable-openssl-version-check, --disable-ipv6
===
The system is an RHEL6.10.
root@zia# uname -a
Linux zia 2.6.32-696.20.1.el6.x86_64 #1 SMP Fri Jan 12 15:07:59 EST 2018 x86_64
x86_64 x86_64 GNU/Linux
root@zia# cat /etc/redhat-release
Red Hat Enterprise Linux Workstation release 6.10 (Santiago)
root@zia#
Since the C language doesn't allow a typedef to be redifined, none of
this (os, configure output) seemed relevant, but when I poke around, it appears
that at some
point the C language changed to allow a typedef to be redefined. I had no idea.
The program:
#include
typedef int int_t;
typedef int int_t;
int main( int argc, char **argv, char **envp ) {printf( "hello world\n" );}
Works with gcc 4.9.3, 5.4.0, 6.3.0, 7.2.0, and 8.5.0 (everything I had
handy to test with) but not 4.4.7, which is still the default on RHEL6.
So, I've updated my scripts that build bind to use one of our many
installed compilers, and now it works again
--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
