As was already suggested, the painless way is to use the SAP DB specific web server.
It could be possible to run this behind Apache using the url rewrite and proxy modules (see http://www.zope.org/Members/anser/apache_zserver for this solution for a totally unrelated application server). =============================== Building a modified fastcgi: imf.pl wafcgi.lnk fastcgi.mac These targets aren't actually part of 'imf.pl all'. It is probably necessary that you use you're own Apache headers, the ones we use are in sys/src/wd/*.ap[13]. <Sidebar> Why do we use our own versions of these headers? Having them as part of the sources frees us from installing them on each machine and we use a very well defined version of these headers. But there are some ideas which would make switching to a different set of headers more painless. </Sidebar> > directory. In an example appears an include directory where > supposedly must have a config.h file, but in the equivalent > directory of python2.2 doesn't have such file. It's the > pyconfig.h? We have to fix that one in installsources.pl. > Where should I modify the compiling options to meet > my installation? toolvars.pl is the right place. Setting 'export NOQUIET=YES' will let you see what is actually passed to the compiler. Some modules set specific compiler options on specific platforms to get around optimizer bugs. Daniel Dittmar -- Daniel Dittmar SAP DB, SAP Labs Berlin [EMAIL PROTECTED] http://www.sapdb.org/ _______________________________________________ sapdb.general mailing list [EMAIL PROTECTED] http://listserv.sap.com/mailman/listinfo/sapdb.general
