Per Jessen wrote: >> dbpinstall.dld fast !xregcomp $INSTLIB/dbpinstall >> Opening registery file /opt/sapdb/sapdb-7.4/usr/wrk/Registry.dcom failed\ >> >> Creating registery file /opt/sapdb/sapdb-7.4/usr/wrk/Registry.dcom fail\ >> ed >> sqlComObjectRegister error: 'access_denied_eo78' >> Calling 'DllRegisterServer' returned error: 0x80000057 >> Adding 'strace' before xregcomp would show which directory or file >> can't be written to. > > > > I never looked at this, but when rebuilding with python properly > configured, > it didn't show again. I'll try a full build.
That 'xregcomp $INSTLIB/dbpinstall' fails doesn't affect the build, but the database probably won't start because it can't find some information. > >> vin77.c fast In file included from vin77.c:35: >> /usr/include/python/Python.h:24: pyconfig.h: No such file or directory >> In file included from /usr/include/python/Python.h:62, >> from vin77.c:35: >> > OK, did a ./configure --prefix=/usr on the python 2.2.1 sources. Seemed > to do the trick, > Might I suggest that sapdb shouldn't have dependencies such as this ? Ie. > unless the installed/available Python is way too old, it should be enough. If Python.h can be found, but pyconfig is missing, then the header files have been copied from the sources without a ./configure. sapdb only relies on finding Python.h. But I'm working on including the Python headers for several versions in the sources, thus making it possibly to build for several Python versions in one make, regardless of the python release present. 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
