[rsyslog] Creating new output module

[Rainer Gerhards]

> -----Original Message-----
> From: rsyslog-bounces at lists.adiscon.com 
> [mailto:rsyslog-bounces at lists.adiscon.com] On Behalf Of Michael Miller
> Sent: Tuesday, August 18, 2009 8:45 PM
> To: rsyslog at lists.adiscon.com
> Subject: [rsyslog] Creating new output module
> 
> Hi,
> 
> I'm trying to follow the examples to create a new output 
> module.  I'm  
> pretty happy with the documentation of what needs to be done within  
> the c code, but I'm struggling with adding a new output module into  
> the build. I though that that the steps were:
> 
> 1) modify rsyslog-5.1.3/configure.ac to add the blocks:
> 
> # omfoo
> AC_ARG_ENABLE(omfoo,
>         [AS_HELP_STRING([--enable-omfoo],[Compiles omfoo template  
> module @<:@default=no@:>@])],
>         [case "${enableval}" in
>          yes) enable_omfoo="yes" ;;
>           no) enable_omfoo="no" ;;
>            *) AC_MSG_ERROR(bad value ${enableval} for 
> --enable-omfoo) ;;
>          esac],
>         [enable_omfoo=no]
> )
> AM_CONDITIONAL(ENABLE_OMTEMPLATE, test x$enable_omfoo = xyes)

Here you overlooked to replace ENABLE_OMTEMPLATE

> # end of copy template
> 
> and:
> 
> 		plugins/omfoo/Makefile \
> 
> at the bottom.
> 
> 2) Creat a plugins/omfoo/ directory, populate it from omtemplate and  
> suitably change the makefile and source code
> 
> 3) Generate new configure scripts:
> 
> install m4-1.4.13
> install autoconf-2.64
> install libtool-2.2.6
> 
> autoreconf
> autoconf
> ./configure --enable-omfoo
> make
> 
> However, something seems fishy with the configure scripts that I  
> generated, they end up creating makefiles that contain: 'gcc .... - 
> rpath ...' and in my version of gcc (gcc (Ubuntu 4.3.2-1ubuntu12)  
> 4.3.2) seems to expect --rpath instead of -rpath.  Looks like 
> osx gets  

I don't know about the particular options, but don't think they are affected
by the config files (but I am far from being an autotools expert...).

> lucky and respects both.   But the fact that autotools didn't 
> get this  
> right makes me suspicious that I've screwed up.  I also tried adding  
> an automake before autoconf, but same error.  My build also 
> fails if I  
> remove the --enable-omfoo option to ./configure.  I've moved my  
> current version aside and gone back to building/running the 
> unmodified  
> rsyslog-5.1.3 version from vanilla source and it's fine, so it has  
> nothing to do with the install of m4, autoconf, or libtool. 
> Any advice  
> would be greatly appreciated.

Maybe the problem is caused by the one replacement you have overlooked. If it
persists, you can post a tarball and I'll have a look at the complete tree.
All in all, what you wrote sounds good to me.

Rainer

> 
> -Mike Miller
> 
> 
> 
> _______________________________________________
> rsyslog mailing list
> http://lists.adiscon.net/mailman/listinfo/rsyslog
> http://www.rsyslog.com
>