Bug 60522 – syslog-ng-1.6.4 fails to build

• Status: RESOLVED FIXED
• Product: Gentoo Linux

[Description archan 2004-08-15 23:20:32 UTC]

I tried to build syslog-ng-1.6.4 and I found that it fails in one of my gentoo configuration while it compiles well in another gentoo system. 

The error log is as follows - 
make[3]: Entering directory `/tmp/syslog-ng-1.6.4/src'
gcc  -g -O2 -Wall -I/usr/include/libol -D_GNU_SOURCE  -o syslog-ng  main.o sourc
es.o center.o filters.o destinations.o log.o cfgfile.o cfg-grammar.o cfg-lex.o a
ffile.o afsocket.o afunix.o afinet.o afinter.o afuser.o afstreams.o afprogram.o 
afremctrl.o nscache.o utils.o syslog-names.o macros.o  -lnsl -lresolv  -lfl /usr
/lib/libol.a -lnsl
sources.o(.text+0x185): In function `do_read_line':
/tmp/syslog-ng-1.6.4/src/sources.c:91: undefined reference to `MIN'
sources.o(.text+0x4f1): In function `make_log_reader':
/tmp/syslog-ng-1.6.4/src/sources.c:169: undefined reference to `MAX'
cfg-lex.o(.text+0x1491): In function `append_string':
/tmp/syslog-ng-1.6.4/src/cfg-lex.l:246: undefined reference to `MIN'
affile.o(.text+0x716): In function `do_init_dest_writer':
/tmp/syslog-ng-1.6.4/src/affile.c:287: undefined reference to `MAX'
afinet.o(.text+0xa9f): In function `do_init_afinet_dest':
/tmp/syslog-ng-1.6.4/src/afinet.c:517: undefined reference to `MAX'
macros.o(.text+0x9e): In function `append_string':
/tmp/syslog-ng-1.6.4/src/macros.c:84: undefined reference to `MIN'
macros.o(.text+0x4ab): In function `expand_macro':
/tmp/syslog-ng-1.6.4/src/macros.c:198: undefined reference to `MIN'
collect2: ld returned 1 exit status
make[3]: *** [syslog-ng] Error 1

I have found that this problem is related to conditional compilation of snprintf.c . Though the configure script reported availability of snprintf, but the linking failed.

Then I updated the ebuild to syslog-ng-1.6.5 It worked without a problem. I am wondering what was the wrong with 1.6.4 version!!

Reproducible: Always
Steps to Reproduce:
1. emerge syslog-ng

[Comment 1 Seemant Kulleen (RETIRED) 2004-08-16 00:06:40 UTC]

archan, please post the output of `emerge info`

[Comment 2 archan 2004-08-16 02:04:24 UTC]

Seemant, it is as follows - 

archan@localhost my_gento # emerge info
Portage 2.0.50-r9 (default-x86-2004.2, gcc-3.3.4, glibc-2.3.4.20040808-r0, 2.6.7
)
=================================================================
System uname: 2.6.7 i686 
Gentoo Base System version 1.5.2
Autoconf: sys-devel/autoconf-2.59-r4
Automake: sys-devel/automake-1.8.5-r1
ACCEPT_KEYWORDS="x86 ~x86"
AUTOCLEAN="yes"
CFLAGS="-O3 -march=i686 -pipe -fomit-frame-pointer"
CHOST="i686-pc-linux-gnu"
COMPILER="gcc3"
CONFIG_PROTECT="/etc /usr/X11R6/lib/X11/xkb /usr/kde/2/share/config /usr/kde/3/s
hare/config /usr/lib/mozilla/defaults/pref /usr/share/config /var/qmail/control"
CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d"
CXXFLAGS="-O3 -march=i686 -pipe -fomit-frame-pointer"
DISTDIR="/usr/portage/distfiles"
FEATURES="autoaddcvs buildpkg ccache sandbox userpriv usersandbox"
GENTOO_MIRRORS="ftp://ftp.ecc.u-tokyo.ac.jp/GENTOO/ http://mirror.gentoo.gr.jp/ 
http://gentoo.oregonstate.edu http://www.ibiblio.org/pub/Linux/distributions/gen
too"
MAKEOPTS="-j2"
PKGDIR="/usr/portage/packages"
PORTAGE_TMPDIR="/var/tmp"
PORTDIR="/usr/portage"
PORTDIR_OVERLAY="/usr/local/portage"
SYNC="rsync://rsync.asia.gentoo.org/gentoo-portage"
USE="3dnow X acl acpi alsa apache2 apm avi berkdb bindist canna cdr crypt cscope
 cups dga doc dvd dvdr encode ethereal fbcon flac flash foomaticdb gdbm gif gpho
to2 gpm gps gstreamer gtk gtk2 imap ipv6 jabber java joystick jpeg ldap libg++ l
irc mad maildir mbox memlimit mikmod mmx mozilla mpeg msn ncurses nls odbc oggvo
rbis opengl oss pcmcia pdflib png pnp postgres python quicktime readline sdl snm
p socks5 spell sse ssl svga tcpd tiff truetype trusted unicode usb vhosts wavelan wmf x86 xml xml2 xosd xv yahoo zlib"

[Comment 3 Jay Pfeifer (RETIRED) 2004-08-16 06:48:41 UTC]

downgrade your dev-libs/libol to 0.3.13 ... 0.3.14 has some issues.

ie.  emerge -v =libol-0.3.13 && emerge -v syslog-ng

That should fix it.

Jay

[Comment 4 Mr. Bones. (RETIRED) 2004-08-16 19:26:46 UTC]

I understand 1.6.5 doesn't have this issue.  Please upgrading and see if that solves your problem.

[Comment 5 archan 2004-08-22 19:54:10 UTC]

I have already done that.

[Comment 6 Matthew Schulkind 2004-08-25 12:06:41 UTC]

Are there any reasons for using 1.6.4 over 1.6.5? 

If not, I think this bug should be closed since there is already a fix in the newer version.

[Comment 7 Mr. Bones. (RETIRED) 2004-09-24 17:05:38 UTC]

yep.  I just marked 1.6.5 stable for x86 so I'll close this now.