building ulogd fails

[Terry Chan]

Remco,

While your optimizations setting are still NOT safe, they are not the
cause of the problem here.  I've fixed the BUILD script in ulogd module
to work correctly now, if the user says "no" to installing libpcap module.

-foptimize-sibling-calls and --fforce-addr are NOT safe optimizations and
will cause you problems sooner or later if your entire lunar box is compiled
with those settings.

Terry Chan
--------------------------------------------------------------
On Wed, Mar 24, 2004 at 11:50:55AM +0100, Remco Lubbers wrote:
> 
> Hi All,
> 
> 'lin ulogd' gave me:
> [output]
> make[1]: Entering directory `/usr/src/ulogd-1.00/extensions'
> gcc -O2 -mcpu=athlon-xp -march=athlon-xp -fomit-frame-pointer
> -foptimize-sibling-calls -fforce-addr -mfpmath=387  
> -DULOGD_CONFIGFILE=\"/etc/ulogd.conf\" -I/usr/src/linux/include -I..
> -I../libipulog/include -I../include -fPIC -o ulogd_BASE_sh.o -c ulogd_BASE.c
> ulogd_BASE.c:379: warning: initialization from incompatible pointer type
> ulogd_BASE.c:380: warning: initialization from incompatible pointer type
> ulogd_BASE.c:381: warning: initialization from incompatible pointer type
> ulogd_BASE.c:382: warning: initialization from incompatible pointer type
> ulogd_BASE.c:383: warning: initialization from incompatible pointer type
> ulogd_BASE.c:384: warning: initialization from incompatible pointer type
> ulogd_BASE.c:385: warning: initialization from incompatible pointer type
> [/output]
> 
> is that because of a optimization setting I have choosen?
> 
> Remco