[syslog-ng]crashbug fix in recent syslog-ng versions

[William Yodlowsky]

Balazs Scheidler <bazsi@balabit.hu> wrote:

> On Tue, Oct 29, 2002 at 09:43:49AM -0500, William Yodlowsky wrote:
> > Balazs Scheidler <bazsi@balabit.hu> wrote:
>
> > Now that you mention it... on Solaris 2.6 I had to use the attached
> > patch for syslog-ng to build.  On Solaris 8 I had to invoke configure
> > this way in order to *really* disable res_init:
> > 
> > /bin/env blb_cv_c_res_init=no ./configure --sysconfdir=/etc
> > 
> > Otherwise, I ended up with this (notice there are two res_init() checks,
> > and one succeeds):
>
> the two different checks are fixed now (the EGREP one remains, as it is the
> one which works on Linux)
>
> Why is this #include <arpa/nameser.h> needed?
>
> res_init() is not defined by <resolv.h> ?
> 
> That might cause a warning, but it should still compile. (I only have
> solaris 8, and res_init() is defined by <resolv.h>

On 2.6 it is too.  The issue is actually a little different; sorry about
the confusion...

% uname -a
SunOS ss5.example.com 5.6 Generic_105181-29 sun4m sparc SUNW,SPARCstation-5

% cd syslog-ng-1.5.23
% ./configure --with-libol=../libol-0.3.5

[snip]

% make
Making all in src
make  all-recursive
Making all in .
gcc -DHAVE_CONFIG_H -I.  -I/tmp/syslog-ng-1.5.23/src -I.     -Wall -I/tmp/libol-0.3.5/src -D_GNU_SOURCE -c main.c
In file included from main.c:44:
/usr/include/resolv.h:140: `MAXDNAME' undeclared here (not in a function)
*** Error code 1
make: Fatal error: Command failed for target `main.o'
Current working directory /tmp/syslog-ng-1.5.23/src
*** Error code 1
make: Fatal error: Command failed for target `all-recursive'
Current working directory /tmp/syslog-ng-1.5.23/src
*** Error code 1
make: Fatal error: Command failed for target `all-recursive-am'
Current working directory /tmp/syslog-ng-1.5.23/src
*** Error code 1
make: Fatal error: Command failed for target `all-recursive'

%

MAXDNAME is defined inside arpa/nameser.h...