The problem is rooted in this bug: http://bugzilla.adiscon.com/show_bug.cgi?id=202
Which I do not know how to fix, "thanks" to me too-weak autoconf knowledge. Help would be appriciated. Rainer > -----Original Message----- > From: [email protected] [mailto:rsyslog- > [email protected]] On Behalf Of Somchai Smythe > Sent: Wednesday, November 24, 2010 5:27 PM > To: rsyslog-users > Subject: Re: [rsyslog] rsyslog 4.6.5 (v4-stable) released > > Hello, > > 64bit kernel, 32bit userland, core2 CPU, compiled from source personal > system > > 2.6.4 worked, but after I upgraded my compiler toolchain to 4.4.5 this > was the first time I tried to build rsyslog. I build other stuff > daily and had no issues with the toolchain. 2.6.4 fails with the same > error now. I searched on the net and learned many people have this > compile error on rsyslog with various versions. > > rsyslog requires me to set -march and has no graceful message if I do > not. I had to modify my configure to be: > > ./configure \ > --prefix=/usr \ > --sysconfdir=/etc \ > --mandir=/usr/man \ > --infodir=/usr/info \ > --enable-relp \ > --enable-mail \ > --enable-gnutls \ > --build=i686-pc-linux-gnu \ > CFLAGS="${CFLAGS:=-O2 -march=i686 -mtune=core2 -fno-strict-aliasing > -fgnu89-inline}" > > and by adding that last line things work. If the configure fails the > test for the features you need, configure should exit with a non-zero > code and not generate the Makefile, in my opinion. Maybe configure > forgot to test for this mysterious atomic bitop stuff? Anyway, I have > a solution now, and I reply to the list so other people who hit this > will have the answer. > > JGH > > > On 11/24/10, Florian Riedl <[email protected]> wrote: > > Which was the last version, where this worked? And, which > distribution (and > > version) do you use? 32bit or 64bit? > > > > Florian > > > > -----Original Message----- > > From: [email protected] > > [mailto:[email protected]] On Behalf Of Somchai > Smythe > > Sent: Mittwoch, 24. November 2010 16:58 > > To: rsyslog-users > > Subject: Re: [rsyslog] rsyslog 4.6.5 (v4-stable) released > > > > My build won't complete (linux with gcc 4.4.5 and kernel 2.6.36.1 and > > gnutls-2.10.3): > > > > ./configure --prefix=/usr --sysconfdir=/etc --mandir=/usr/man > > --infodir=/usr/info --enable-relp --enable-mail --enable-gnutls > > --build=i686-pc-linux-gnu > > > > .... > > > > > > /bin/sh ../libtool --tag=CC --mode=link gcc -g -O2 -W -Wall > > -Wformat-security -Wshadow -Wcast-align -Wpointer-arith > > -Wmissing-format-attribute -g -export-dynamic -o rsyslogd > > rsyslogd-syslogd.o rsyslogd-omshell.o rsyslogd-omusrmsg.o > > rsyslogd-omfwd.o rsyslogd-omfile.o rsyslogd-ompipe.o > > rsyslogd-omdiscard.o rsyslogd-iminternal.o rsyslogd-pidfile.o -lz > > -lpthread ../runtime/librsyslog.la > > libtool: link: gcc -g -O2 -W -Wall -Wformat-security -Wshadow > > -Wcast-align -Wpointer-arith -Wmissing-format-attribute -g -o > rsyslogd > > rsyslogd-syslogd.o rsyslogd-omshell.o rsyslogd-omusrmsg.o > > rsyslogd-omfwd.o rsyslogd-omfile.o rsyslogd-ompipe.o > > rsyslogd-omdiscard.o rsyslogd-iminternal.o rsyslogd-pidfile.o > > -Wl,--export-dynamic -lz -lpthread ../runtime/.libs/librsyslog.a - > ldl > > -lrt > > ../runtime/.libs/librsyslog.a(librsyslog_la-msg.o): In function > > `msgDestruct': > > /tmp/rsyslog-4.6.5/runtime/msg.c:803: undefined reference to > > `ATOMIC_INC_AND_FETCH' > > ../runtime/.libs/librsyslog.a(librsyslog_la-wtp.o): In function > > `wtpProcessThrdChanges': > > /tmp/rsyslog-4.6.5/runtime/wtp.c:219: undefined reference to > > `ATOMIC_STORE_0_TO_INT' > > ../runtime/.libs/librsyslog.a(librsyslog_la-wti.o): In function > > `wtiSetState': > > /tmp/rsyslog-4.6.5/runtime/wti.c:149: undefined reference to > > `ATOMIC_CAS_VAL' > > ../runtime/.libs/librsyslog.a(librsyslog_la-wti.o): In function > > `wtiWorkerCancelCleanup': > > /tmp/rsyslog-4.6.5/runtime/wti.c:330: undefined reference to > > `ATOMIC_STORE_1_TO_INT' > > ../runtime/.libs/librsyslog.a(librsyslog_la-wti.o): In function > `wtiWorker': > > /tmp/rsyslog-4.6.5/runtime/wti.c:417: undefined reference to > > `ATOMIC_STORE_1_TO_INT' > > ../runtime/.libs/librsyslog.a(librsyslog_la-wti.o): In function > > `wtiCancelThrd': > > /tmp/rsyslog-4.6.5/runtime/wti.c:181: undefined reference to > > `ATOMIC_STORE_1_TO_INT' > > collect2: ld returned 1 exit status > > make[2]: *** [rsyslogd] Error 1 > > make[2]: Leaving directory `/tmp/rsyslog-4.6.5/tools' > > make[1]: *** [all-recursive] Error 1 > > make[1]: Leaving directory `/tmp/rsyslog-4.6.5' > > make: *** [all] Error 2 > > > > > > On 11/24/10, Florian Riedl <[email protected]> wrote: > >> Hi all, > >> > >> We have just released rsyslog 4.6.5, a member of the v4-stable > branch. > >> > >> This update addresses the TLS bug, that has been bothering a lot of > users > >> lately and a few other issues. It stops rsyslog from looping, thus > > disabling > >> functionality and bearing the risk of unresponsiveness of the whole > >> system. > >> More details about this issue can be found here: > >> > >> http://bugzilla.adiscon.com/show_bug.cgi?id=194 > >> <http://bugzilla.adiscon.com/show_bug.cgi?id=194> > >> > >> See ChangeLog for more details. > >> > >> ChangeLog: > >> > >> http://www.rsyslog.com/changelog-for-4-6-5-v4-stable/ > >> <http://www.rsyslog.com/changelog-for-4-6-5-v4-stable/> > >> > >> Download: > >> > >> http://www.rsyslog.com/rsyslog-4-6-5-v4-stable/ > >> <http://www.rsyslog.com/rsyslog-4-6-5-v4-stable/> > >> > >> As always, feedback is appreciated. > >> > >> Best regards, > >> Florian Riedl > >> > >> -- > >> > >> Support > >> > >> ======= > >> > >> > >> > >> Improving rsyslog is costly, but you can help! We are looking for > >> organizations that find rsyslog useful and wish to contribute back. > You > > can > >> contribute by reporting bugs, improve the software, or donate money > or > >> equipment. > >> > >> > >> > >> Commercial support contracts for rsyslog are available, and they > help > >> finance > >> continued maintenance. Adiscon GmbH, a privately held German > company, is > >> currently funding rsyslog development. We are always looking for > > interesting > >> development projects. For details on how to help, please see > >> http://www.rsyslog.com/doc-how2help.html > >> <http://www.rsyslog.com/doc-how2help.html> . > >> > >> > >> > >> _______________________________________________ > >> rsyslog mailing list > >> http://lists.adiscon.net/mailman/listinfo/rsyslog > >> http://www.rsyslog.com > >> > > _______________________________________________ > > rsyslog mailing list > > http://lists.adiscon.net/mailman/listinfo/rsyslog > > http://www.rsyslog.com > > _______________________________________________ > > rsyslog mailing list > > http://lists.adiscon.net/mailman/listinfo/rsyslog > > http://www.rsyslog.com > > > _______________________________________________ > rsyslog mailing list > http://lists.adiscon.net/mailman/listinfo/rsyslog > http://www.rsyslog.com _______________________________________________ rsyslog mailing list http://lists.adiscon.net/mailman/listinfo/rsyslog http://www.rsyslog.com
