Ainsi parlait Dave Ahn : [..] > > RES-RSA can be built and installed separatly, right ? So if i make > > Vanilla package requires it for building, where is the problem ? > > Well, RES-RSA doesn't produce any installable runtimes. You could bulid > a dev package that contains it, however. I tought it was an independant project, but it seems actually to be a netrek-dependant one. I guess it is used by several netrek client/servers, right ? Howevern Vanilla-2.9p17 archive already ships everyting from res-rsa-2.9.2 one, with even one more source file rsa-server.c. So, what's the use of the additional archive ? [..] > > Just tell me wich other image i should use for nice menu entry. > > I don't think we have anything really useful. You're welcome to take any > graphic from the home page (snapshots, etc), slice it down and use those. > One of the ship bitmaps might be nice. There is a library of decent > snapshots at: http://www.netrek.org/images/random/ As it concerns only the config utility, i used gum.xpm found in the tarball. However, once reduced to 32x32 pixels, it's not really readable :-) [..] > No, it's definitely a system header file. It looks like "struct tm" is > not being defined. Try adding "#include <time.h>" before the line > "#include <sys/time.h>" Ok, fixed. Now with the new problems... Vanilla use standard autoconf/automake, however: 1) installation fails: Neither %configure rpm macros (which get expanded to make \ prefix=$RPM_BUILD_ROOT/usr \ exec_prefix=$RPM_BUILD_ROOT/usr \ bindir=$RPM_BUILD_ROOT/usr/bin \ sbindir=$RPM_BUILD_ROOT/usr/sbin \ sysconfdir=/$RPM_BUILD_ROOTetc \ datadir=$RPM_BUILD_ROOT/usr/share \ includedir=$RPM_BUILD_ROOT/usr/include \ libdir=$RPM_BUILD_ROOT/usr/lib \ libexecdir=$RPM_BUILD_ROOT/usr/lib \ localstatedir=$RPM_BUILD_ROOT/var/lib \ sharedstatedir=$RPM_BUILD_ROOT/usr/com \ mandir=$RPM_BUILD_ROOT/usr/share/man \ infodir=$RPM_BUILD_ROOT/usr/share/info \ install ), nor make install destdir=$RPM_BUILD_ROOT were sucessful to install in $RPM_BUILD_ROOT fake filesystem root :-( Seems i'll had to install everything by hand. 2) compilation flags fails %configure macro result in the following output + CFLAGS=-O3 -fomit-frame-pointer -pipe -mcpu=pentiumpro -march=i586 -ffast-math -fno-strength-reduce + export CFLAGS + CXXFLAGS=-O3 -fomit-frame-pointer -pipe -mcpu=pentiumpro -march=i586 -ffast-math -fno-strength-reduce + export CXXFLAGS + FFLAGS=-O3 -fomit-frame-pointer -pipe -mcpu=pentiumpro -march=i586 -ffast-math -fno-strength-reduce + export FFLAGS + '[' -f configure.in ']' + libtoolize --copy --force Remember to add `AC_PROG_LIBTOOL' to `configure.in'. You should add the contents of `/usr/share/aclocal/libtool.m4' to `aclocal.m4'. + ./configure i586-mandrake-linux-gnu --prefix=/usr --exec-prefix=/usr --bindir=/usr/bin --sbindir=/usr/sbin --sysconfdir=/etc --datadir=/usr/share --includedir=/usr/include --libdir=/usr/lib --libexecdir=/usr/lib --localstatedir=/var/lib --sharedstatedir=/usr/com --mandir=/usr/share/man --infodir=/usr/share/info However, everything is compiled thereafter without any optimisation flag: gcc -g -I../ntserv -DRSA -I.. -c -o cluecheck.o cluecheck.c Finaly, i'm a bit confused about the config utility name. It seems to be gum, so why symlink it as netrekcfg, and ships it in a config package ? -- Guillaume Rousse <rousse at ccr.jussieu.fr> GPG key http://lis.snv.jussieu.fr/~rousse/gpgkey.html