requirements when source files changes (was Re: [syslog-ng]syslog-ng vs (of all things) Win2k + IIS)

[Scott McDermott]

matthew.copeland@honeywell.com on Tue 10/10 15:41 -0500:
> I tried changing the max_connections in afinet.c from 10 to 11, and it
> will no longer compile when I do this.  It seems to throw errors from
> make_class saying that there is no file or directory.  If I change it
> back to 10, it will still not compile.  (It compiles before the change
> to 11.) No other changes from the standard 1.4.7.   Any thoughts?

Yes, I ran into this myself when screwing around with the source.
Here's my relevant build notes:

README/syslog-ng

        requires libol to be installed, but links statically, so we give
        it --with-libol pointed at the build tree (we are the only
        program as of 20001004 that uses libol)

        note that any change to the source files seems to cause the
        libol class configurator (libol seems to basically be a bunch of
        routines for OO C programming, and comes with a preprocessor for
        C source files where you can define classes in the .x file or
        something like that) to need to be run.  This of course requires
        scsh, see README/libol

README/libol

        This package requires scsh (the Scheme shell from MIT) to build
        properly.  It will appear to build without it, but some of the
        resulting scripts specify "#! \" as their interpreter (it's
        supposed to be #!/path/to/scsh but since it wasn't found...) and
        if they are ever called on (syslog-ng does call on them if you
        make changes to source files) they will fail to execute.

        configure like this:

        # important! watch configure output to be sure it detects the
        # scsh
        export PATH=$PATH:/path/to/scsh/build/tree/root/scsh
        ./configure

README/scsh

        Currently only using this package to support reconfiguration of
        libol/syslog-ng tree.  For this reason we are not installing the
        program but leaving it in the build directory.  To do this use

                make libdir=`pwd`

        else it won't run properly.  `configure' needs to be given no
        special arguments since we don't care where it's installed and
        there's not any special features to enable or disable.

        Also note that, although not documented, scsh requires scshvm in
        the same directory as itself.  Simply copy buildroot/scshvm to
        buildroot/scsh/

Hope this helps.