Hi, Jonathan, Sandor, thanks for the report and the proposed fix. I've commited it to eventlog git tree. On Thu, 2012-03-01 at 13:03 -0600, Jonathan Kaufman wrote:
Awesome!
Thank you very much.
Just in case anyone else is working on Aix 7.1 builds of Syslog-NG here is what worked (or didn't) for me.
1. Update to the LATEST version of IBM VisualAge C/C++, I couldn't get it to compile until I updated to the 2012 patch set (I was at the early 2011 patch set) for V11 2. There were also a few Aix APARs that would have affected compiling code dealing with the assembler or whatnot. I sidestepped them and upgraded to the latest TL and SP (TL1 SP3) 3. I couldn't get the bundled libtool that is included with the Syslog-NG source to recognize that you can create shared libraries, so I couldn't create shared libraries for the modules (that was an issue) I "upgraded" the bundled libtool to 2.4.2 which fixed it so I could created shared libraries for the modules. The make install didn't copy them, so I had to do it manually but at least it works. I would expect this isn't the preferred method for fixing this, but so far it doesn't seem to have a downside. 4. I had the libiconv library from perzl.org loaded for a different application, and if Syslog-NG used that either during compile or runtime it would coredump. Moral of the story seems to be to use the IBM libiconv library. 5. And lastly Sandor's suggestion. Add the alloca.h include to evtstr.c if you are using the IBM VisualAge compiler you may be able to use the -ma compiler option. I don't know if it does the same thing, but if I used the option (and didn't add it to the source) syslog-ng didn't core. I will likely just add it to the source, but thought to mention the -ma option *seems* to work just the same.
Hopefully this will be the last of my instability woes on Aix 7.1 with Syslog-NG.
-- Bazsi