I have now backported the patch to the beta branch.

BTW, branch namings: master - recent devel, beta current beta
v<x>-beta - older version beta (when version still receives feature updates)
v<x>-stable - older stable version

Rainer

> -----Original Message-----
> From: [email protected] [mailto:rsyslog-
> [email protected]] On Behalf Of Marc Schiffbauer
> Sent: Wednesday, December 09, 2009 3:16 PM
> To: rsyslog-users
> Subject: Re: [rsyslog] rsyslog 4.5.x queue file cleanup?
> 
> 
> Sorry, but I am bit puzzled from all the branches. Which one should I
> take
> now? Really the head master? I think I will get some 5.5.x version
> then, not?
> 
> What do you mean by "latest version" Head of a 5.3-Branch? Or checkout
> the
> 5.3.4 tag from git?
> 
> This has the same error:
> http://git.adiscon.com/?p=rsyslog.git;a=snapshot;h=c051786ea6318f9a9a5e
> 531c49512e4ae19f249b;sf=tgz
> 
> -Marc
> 
> 
> 
> Am Mittwoch, 9. Dezember 2009 14:52:15 schrieb Rainer Gerhards:
> > Marc,
> >
> > I guess you use a 32-bit platform. Please pull the latest version
> from the
> > git master branch, it contains a fix for this type of build error.
> >
> > Rainer
> >
> > > -----Original Message-----
> > > From: [email protected] [mailto:rsyslog-
> > > [email protected]] On Behalf Of Marc Schiffbauer
> > > Sent: Wednesday, December 09, 2009 2:40 PM
> > > To: rsyslog-users
> > > Subject: Re: [rsyslog] rsyslog 4.5.x queue file cleanup?
> > >
> > > Hallo Rainer,
> > >
> > > I am back now. And as promised I wanted to test 5.3.4 now... I saw
> > > 5.3.5 is
> > > out so I wanted to give that version a try.
> > >
> > > But unfortunately it does not build. Any hint?
> > >
> > >
> > >
> > > In file included from omfile.c:67:
> > > ../runtime/atomic.h:64:3: warning: #warning "atomic builtins not
> > > available,
> > > using nul operations - rsyslogd will probably be racy!"
> > > omfile.c: In function âgetClockFileAccessâ:
> > > omfile.c:91: warning: implicit declaration of function
> > > âATOMIC_INC_AND_FETCHâ
> > >   CC     rsyslogd-omdiscard.o
> > >   CC     rsyslogd-pmrfc5424.o
> > >   CC     rsyslogd-pmrfc3164.o
> > >   CC     rsyslogd-iminternal.o
> > >   CC     rsyslogd-pidfile.o
> > >   CCLD   rsyslogd
> > > rsyslogd-omfile.o: In function `getClockFileAccess':
> > > /root/src/rsyslog-5.3.5/tools/omfile.c:91: undefined reference to
> > > `ATOMIC_INC_AND_FETCH'
> > > /root/src/rsyslog-5.3.5/tools/omfile.c:91: undefined reference to
> > > `ATOMIC_INC_AND_FETCH'
> > > /root/src/rsyslog-5.3.5/tools/omfile.c:91: undefined reference to
> > > `ATOMIC_INC_AND_FETCH'
> > > /root/src/rsyslog-5.3.5/tools/omfile.c:91: undefined reference to
> > > `ATOMIC_INC_AND_FETCH'
> > > ../runtime/.libs/librsyslog.a(librsyslog_la-glbl.o): In function
> > > `SetGlobalInputTermination':
> > > /root/src/rsyslog-5.3.5/runtime/glbl.c:136: undefined reference to
> > > `ATOMIC_STORE_1_TO_INT'
> > > ../runtime/.libs/librsyslog.a(librsyslog_la-msg.o): In function
> > > `msgDestruct':
> > > /root/src/rsyslog-5.3.5/runtime/msg.c:802: undefined reference to
> > > `ATOMIC_INC_AND_FETCH'
> > > ../runtime/.libs/librsyslog.a(librsyslog_la-wti.o): In function
> > > `wtiSetState':
> > > /root/src/rsyslog-5.3.5/runtime/wti.c:111: undefined reference to
> > > `ATOMIC_STORE_0_TO_INT'
> > > /root/src/rsyslog-5.3.5/runtime/wti.c:109: undefined reference to
> > > `ATOMIC_STORE_1_TO_INT'
> > > ../runtime/.libs/librsyslog.a(librsyslog_la-queue.o): In function
> > > `DoDeleteBatchFromQStore':
> > > /root/src/rsyslog-5.3.5/runtime/queue.c:1291: undefined reference
> to
> > > `ATOMIC_SUB'
> > > /root/src/rsyslog-5.3.5/runtime/queue.c:1292: undefined reference
> to
> > > `ATOMIC_SUB'
> > > /root/src/rsyslog-5.3.5/runtime/queue.c:1291: undefined reference
> to
> > > `ATOMIC_SUB'
> > > /root/src/rsyslog-5.3.5/runtime/queue.c:1292: undefined reference
> to
> > > `ATOMIC_SUB'
> > > /root/src/rsyslog-5.3.5/runtime/queue.c:1291: undefined reference
> to
> > > `ATOMIC_SUB'
> > > ../runtime/.libs/librsyslog.a(librsyslog_la-
> > > queue.o):/root/src/rsyslog-5.3.5/runtime/queue.c:1292: more
> undefined
> > > references to `ATOMIC_SUB' follow
> > > collect2: ld returned 1 exit status
> > > make[2]: *** [rsyslogd] Error 1
> > > make[2]: Leaving directory `/root/src/rsyslog-5.3.5/tools'
> > > make[1]: *** [all-recursive] Error 1
> > > make[1]: Leaving directory `/root/src/rsyslog-5.3.5'
> > > make: *** [all] Error 2
> > >
> > > Am Donnerstag, 5. November 2009 17:42:01 schrieb Rainer Gerhards:
> > > > > -----Original Message-----
> > > > > From: [email protected] [mailto:rsyslog-
> > > > > [email protected]] On Behalf Of Marc Schiffbauer
> > > > > Sent: Tuesday, November 03, 2009 11:58 AM
> > > > > To: rsyslog-users
> > > > > Subject: Re: [rsyslog] rsyslog 4.5.x queue file cleanup?
> > > > >
> > > > > Hello Rainer,
> > > > >
> > > > > is there some news about this issue?
> > > >
> > > > Unfortuantely not at the moment (I guess you see it is a busy
> time).
> > >
> > > Could
> > >
> > > > you give 5.3.4 a try? It would be very interesting (even for a
> v4-
> > >
> > > fix) to
> > >
> > > >  see if the problem persists or not...
> > > >
> > > > Rainer
> > > >
> > > > > TIA
> > > > > -Marc
> > > > >
> > > > > Am Dienstag, 20. Oktober 2009 18:38:16 schrieb Rainer Gerhards:
> > > > > > thanks!
> > > > > >
> > > > > > Interesting, I see that only one of the messages that should
> be
> > >
> > > in
> > >
> > > > > the .qi
> > > > >
> > > > > > are actually present. I wonder if this is related to the fact
> > >
> > > that
> > >
> > > > > ompgsql
> > > > >
> > > > > > emits an error message itself while being down (the others
> don't
> > >
> > > do
> > >
> > > > > this
> > > > >
> > > > > > AFIK). Will try to dig down to this (but I have to do so as
> time
> > > > >
> > > > > permits).
> > > > >
> > > > > > Rainer
> > > > >
> > > > > _______________________________________________
> > > > > 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
_______________________________________________
rsyslog mailing list
http://lists.adiscon.net/mailman/listinfo/rsyslog
http://www.rsyslog.com

Reply via email to