[syslog-ng] Use of sockaddr_storage in src/fdread.c
Balazs Scheidler
bazsi at balabit.hu
Tue Dec 19 13:20:59 CET 2006
On Sun, 2006-12-17 at 13:04 -0600, Albert Chin wrote:
> While building syslog-ng-2.0.0 on Solaris 7/SPARC:
> cc -DHAVE_CONFIG_H -I. -I. -I..
> -DPATH_SYSCONFDIR=\"/etc/opt/TWWfsw/syslogng20\"
> -DPATH_LOCALSTATEDIR=\"/var/opt/TWWfsw/syslogng20\"
> -I/opt/TWWfsw/libglib26/include -I/opt/TWWfsw/libglib26/lib/include
> -I/opt/TWWfsw/gettext014/include
> -I/opt/TWWfsw/syslogng20/include/eventlog -D_GNU_SOURCE -mr -Qn
> -xstrconst -xO2 -xtarget=ultra2 -xarch=v8plusa -c fdread.c
> "fdread.c", line 45: incomplete struct/union/enum sockaddr_storage: sas
>
> This platform does not have struct sockaddr_storage, as used in
> src/fdread.c. Is syslog-ng _only_ for IPV6 systems?
>
No, sockaddr_storage is address family independent, I had the impression
that it is available on a wide range of platforms. (we compile on
solaris 8/9 ourselves and it works there)
I'd need to put together some configure tests and work around the
problem. I only need to find some time to do that.
--
Bazsi
More information about the syslog-ng
mailing list