update Re: bind 9 on tru64

From: <ldg_at_ulysium.net>
Date: Tue, 01 Apr 2003 13:10:09 -0500

Here's a bit of relevant info that I should've given in my previous post:
I'm compiling bind 9 with the following options:

--with-libtool
--with-openssl
--enable-libbind
--enable-ipv6
--enable-threads

I also use --with-randomdev=/dev/urandom but that shouldn't affect this
compilation issue.

One or more of those options must be turning on the part of the source in
bind 9 that calls in those re-definitions of variables, basically the
problem is that tru64 5.1b has the following variables defined in an ifdef
block of _OSF_SOURCE in /usr/include/unistd.h :

extern int getnetgrent __((char **, char **, char **));
extern int innetgr __((char *, char *, char *, char *));
extern void setnetgrent __((char *));

those are lines 703,704 and 720 and those variables are re-defined in bind 9
in the file lib/bind/port_after.h like this:

int getnetgrent(const char **machinep, const char **userp,
                const char **domainp);

void setnetgrent(const char *netgroup);

int innetgr(const char *netgroup, const char *machine,
            const char *user, const char *domain);

at lines 366, 371 and 375

Those who were able to compile bind 9 on tru64 without encountering this
must've not used the same option switches I'm using or have made changes to
the source code somehow.
The only way I was able to compile bind 9 so far is by commenting out those
3 lines in unistd.h which I restore after bind is compiled, but this is
really not the way it should be done, so do we change the bind 9 source code
or do we try to undef _OSF_SOURCE somehow???

-- 
Didier Godefroy
mailto:dg_at_ulysium.net
on 4/1/03 7:00 AM, Paul A Sand at pas_at_unh.edu uttered the following:
> 
> I was able to compile 9.2.2 on my 5.1B (pk1) system with just
> 
> ./configure
> make
> 
> This system doesn't have gcc installed. 
Received on Tue Apr 01 2003 - 18:12:03 NZST

This archive was generated by hypermail 2.4.0 : Wed Nov 08 2023 - 11:53:44 NZDT