2014-10-01 6:16 GMT+02:00 Radu Gheorghe <[email protected]>:
> But the problem isn't on 8.4.1, is on master, right? Yes, exactly, that was the question. As it looks, there is an obvious difference between what configure detects and what actually is present on the system. Here it causes no harm, just the deprecated functions are being used instead the new ones (which are not found by configure). Interestingly, the json_tokener_error_desc() function is also not detected, and this also applies to v8.4.1 (I right now checked). Rsyslog still builds. > I'm not sure I can > help *solving* the problem (I had similar issues before and I was pretty > clueless), I could only try reproducing it on my openSUSE-fied laptop. Let > me know if that would help. > > Wait, just one thing: did you follow the instructions from the earlier > thread named "fyi, src build of rsyslog/head + json-c/head (on openSUSE) > works"? It basically requires you to build json-c from master and use that, > and the procedure worked for me last week while testing the Elasticsearch > fixes. > Ah, OK. No I didn't do that. In fact, that closes the issue for me. As I said, it's not a real problem (at least now). If there is some issue with openSuSe packaging, just let's wait until the dust settles. I just wanted to make sure the average user can build rsyslog, and this seems to be possible. I don't intend (nor am I able to) dig into the specifics on how json-c is provided on openSuSe. Thanks! Rainer _______________________________________________ rsyslog mailing list http://lists.adiscon.net/mailman/listinfo/rsyslog http://www.rsyslog.com/professional-services/ What's up with rsyslog? Follow https://twitter.com/rgerhards NOTE WELL: This is a PUBLIC mailing list, posts are ARCHIVED by a myriad of sites beyond our control. PLEASE UNSUBSCRIBE and DO NOT POST if you DON'T LIKE THAT.
