paul barnes wrote: > Thank you for your reply. > As a precision I use gnake, I use MKS, I read the Building page on Windows http://directory.fedora.redhat.com/wiki/Building#Windows. > > I do not understand your reply as I might miss some information. What is the relation between the FDS modules and the fact there is Apache for Win 32 ? Are the FDS modules only used in the admin server ? What is then the list of components I can remove from the compilation list if I don't want the admin server to be compiled ? Or what is the list of components I do have to compile to get the FDS server only ? FDS includes a java-based console to administer the server. This requires a web server to work and we currently use Apache. We wrote several Apache modules to make console work, notably: mod_nss, mod_admserv and mod_restartd. We have done zero testing with these on win32. I didn't look but I doubt there is an option to not build the admin server. It would likely require some Makefile hacking (or probably a .mk file). The components used can be found in components.mk and/or components_versions.mk. Looking at the building page it looks like adminserver/console requires: console onlinehelp setuputil adminutil adminserver dsonlinehelp directoryconsole crimson dsmlgwjars mod_admserv mod_nss mod_restartd Everything else looks like core FDS. rob > > Thank you in advance > > Paul Barnes > > > Rob Crittenden <rcritten at redhat.com> a ?crit : > paul barnes wrote: >> Hello, >> I've compiled,installed,run,configured FDS with no pb so far, for a simple applicative schema, on Linux. >> I wish to do same things on Windows 2003, then to begin with, to compile. >> I've tried with MKS (see 1 below) but some pbs, I've tried with cygwin (see 2 below) but some pbs as well... >> I wonder what is the best strategy: going on with MKS, going on with cygwin, >> What must I check to succeed in compiling FDS on windows ? >> >> Or can I find "somewhere" a binary version for windows.... >> >> Thank you very much in advance >> Paul Barnes >> >> >> >> 1) MKS (gmake), but quite quickly, make fails the following way >> **************************************************************************** >> >>> make >> [ : ] >> make: execvp: true: Invalid argument >> make: *** [pre-everything] Error 127 >> >> >> 2) I've tried on cygwin, I do face an other pb : >> ****************************************************** >> cd md; make export >> make[5]: Entering directory `/home/desgranp/fedora/dsbuild-fds102/ds/mozilla/wor >> k/mozilla/nsprpub/OPT.OBJ/pr/include/md' >> sh ../../../../build/cygwin-wrapper nsinstall -m 444 ../../../../pr/include/md/_ >> aix32.cfg ../../../../pr/include/md/_aix64.cfg ../../../../pr/include/md/_beos.c >> fg ../../../../pr/include/md/_bsdi.cfg ../../../../pr/include/md/_darwin.cfg ../ >> ../../../pr/include/md/_dgux.cfg ../../../../pr/include/md/_freebsd.cfg ../../.. >> /../pr/include/md/_hpux32.cfg ../../../../pr/include/md/_hpux64.cfg ../../../../ >> pr/include/md/_irix32.cfg ../../../../pr/include/md/_irix64.cfg ../../../../pr/i >> nclude/md/_linux.cfg ../../../../pr/include/md/_ncr.cfg ../../../../pr/include/m >> d/_nec.cfg ../../../../pr/include/md/_netbsd.cfg ../../../../pr/include/md/_next >> step.cfg ../../../../pr/include/md/_nto.cfg ../../../../pr/include/md/_openbsd.c >> fg ../../../../pr/include/md/_openvms.cfg ../../../../pr/include/md/_os2.cfg ../ >> ../../../pr/include/md/_osf1.cfg ../../../../pr/include/md/_qnx.cfg ../../../../ >> pr/include/md/_reliantunix.cfg ../../../../pr/include/md/_rhapsody.cfg ../../../ >> ../pr/include/md/_scoos.cfg ../../../../pr/include/md/_solaris.cfg ../../../../p >> r/include/md/_sony.cfg ../../../../pr/include/md/_sunos4.cfg ../../../../pr/incl >> ude/md/_unixware.cfg ../../../../pr/include/md/_unixware7.cfg ../../../../pr/inc >> lude/md/_win16.cfg ../../../../pr/include/md/_win95.cfg ../../../../pr/include/m >> d/_winnt.cfg ../../../../pr/include/md/_aix.h ../../../../pr/include/md/_beos.h >> ../../../../pr/include/md/_bsdi.h ../../../../pr/include/md/_darwin.h ../../../. >> ./pr/include/md/_dgux.h ../../../../pr/include/md/_freebsd.h ../../../../pr/incl >> ude/md/_hpux.h ../../../../pr/include/md/_irix.h ../../../../pr/include/md/_linu >> x.h ../../../../pr/include/md/_macos.h ../../../../pr/include/md/_ncr.h ../../.. >> /../pr/include/md/_nec.h ../../../../pr/include/md/_netbsd.h ../../../../pr/incl >> ude/md/_nextstep.h ../../../../pr/include/md/_nspr_pthread.h ../../../../pr/incl >> ude/md/_nto.h ../../../../pr/include/md/_openbsd.h ../../../../pr/include/md/_op >> envms.h ../../../../pr/include/md/_os2.h ../../../../pr/include/md/_os2_errors.h >> ../../../../pr/include/md/_osf1.h ../../../../pr/include/md/_pcos.h ../../../.. >> /pr/include/md/_pth.h ../../../../pr/include/md/_qnx.h ../../../../pr/include/md >> /_reliantunix.h ../../../../pr/include/md/_rhapsody.h ../../../../pr/include/md/ >> _scoos.h ../../../../pr/include/md/_solaris.h ../../../../pr/include/md/_sony.h >> ../../../../pr/include/md/_sunos4.h ../../../../pr/include/md/_unix_errors.h ../ >> ../../../pr/include/md/_unixos.h ../../../../pr/include/md/_unixware.h ../../../ >> ../pr/include/md/_win16.h ../../../../pr/include/md/_win32_errors.h ../../../../ >> pr/include/md/_win95.h ../../../../pr/include/md/_winnt.h ../../../../pr/include >> /md/prosdep.h ../../../../pr/include/md/sunos4.h /home/desgranp/fedora/dsbuild-f >> ds102/ds/mozilla/work/mozilla/dist/OPT.OBJ/include/md >> ../../../../build/cygwin-wrapper: line 75: exec: nsinstall: not found >> make[5]: *** [export] Error 127 >> >> > > A couple of thoughts: > > 1. You almost certainly need to use GNU make > 2. Starting with dsbuild is probably not the best way to do this > 3. While there is Apache for win32 the FDS modules haven't been tested > at all under Windows and I suspect won't even compile. > > Historically what we've done internally is to prebuild the components > (NSPR, NSS, SASL, SNMP, etc) and put that into a "components" area so we > don't have to build the entire world all the time. That is probably a > better starting point. The trick is to get the binaries put into the > proper directory structure. I believe there is an argument you need to > pass to gmake for it to use "internal" components. The file > components.mk would be a good place to start. > > I'd use the Building page on the FDS wiki as a starting point for > building. IIRC we used the MKS tools (except for make). > > How you can get past the missing admin server I don't know. FDS doesn't > really need an admin server to run. You may even be able to use one > admin server to manage multiple FDS servers but I'm a little fuzzy on that. > > rob > -- -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/x-pkcs7-signature Size: 3178 bytes Desc: S/MIME Cryptographic Signature Url : http://lists.fedoraproject.org/pipermail/389-users/attachments/20060602/6eefcfbb/attachment.bin