Re: Arla 0.42-RC2

On Thursday, 30 March 2006 16:48, Tomas Olsson wrote:
> Jean-Damien Durand <[email protected]> writes:
> > CFLAGS="-Wall -g -DHAVE_OPENSSL -O2 -Wl,-z,defs"
> >
> Is -DHAVE_OPENSSL still needed?

I retried with './configure; make' only and got:

Making all in rxkad
make[1]: Entering directory `/tmp/arla-0.42-RC2/rxkad'
/bin/sh ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I. -I../include -I../include -I../lib/roken -I../lib/roken -I../include -I. -I. -I../include -I./../include -I.. -I./.. -I../include -I/usr/include    -Wall -Wmissing-prototypes -Wpointer-arith -Wbad-function-cast -Wmissing-declarations -Wnested-externs -g  -Wall -Wmissing-prototypes -Wpointer-arith -Wmissing-declarations -Wnested-externs  -c -o rxk_locl.lo rxk_locl.c
 gcc -DHAVE_CONFIG_H -I. -I. -I../include -I../include -I../lib/roken -I../lib/roken -I../include -I. -I. -I../include -I./../include -I.. -I./.. -I../include -I/usr/include -Wall -Wmissing-prototypes -Wpointer-arith -Wbad-function-cast -Wmissing-declarations -Wnested-externs -g -Wall -Wmissing-prototypes -Wpointer-arith -Wmissing-declarations -Wnested-externs -c rxk_locl.c -o rxk_locl.o
In file included from rxk_locl.c:34:
rxkad_locl.h:67:17: error: des.h: No such file or directory
make[1]: *** [rxk_locl.lo] Error 1
make[1]: Leaving directory `/tmp/arla-0.42-RC2/rxkad'
make: *** [all-recursive] Error 1

> Also, my gcc is complaining  
> i486-linux-gnu-gcc: -z: linker input file unused because linking not done
> i486-linux-gnu-gcc: defs: linker input file unused because linking not done
> Maybe it should be in LDFLAGS or so.

How much I agree! It is just that the default debian/rules is created explicitely with these flags
(we start a new package doing: dh_make -f path_of.tar.gz - and voila, debian/rules is created
like that). Harmless so I did not change that... But in conclusion I definitely agree!

> > make[1]: *** No rule to make target `themis.texi', needed by `arla.info'.
> > 
> Thanks, fixed. I'm not sure why it wanted to build arla.info, though. It's
> in the tarball already. distclean?

Yes, rebuilding a package always start with distclean. at very first packaging distclean will fail, though,
since there was no ./configure yet; so there is another issue that I did never investigate. Will
do OOTD.

Cheers, JD.