> so far so good, everything gets compiled and the resulting 
> binaries are 
> now in the package directory. now i tried to figure out how to make a 
> working package out of this but with no success so far. i looked into 
> the src.rpm of the suse rpm for sapdb 7.3 but they are 
> applying so many 
> patches so i could not figure out yet what they are exactly 
> doing there.

I've added our rpm spec at 
ftp://ftp.sap.com/pub/sapdb/bin/tmp/sapdb-rpmspec-7.4.03.10.tgz.

> i also compared the compiled tree with the sapdb 7.4 rpm found on 
> ftp.sap.com. and there are many files this rpm which are not in the 
> compiled package directory - so it seems there is some stuff 
> missing in 
> the source which are probably required to make a installable 
> package out 
>   of it.

If you execute
imq quickknl
ims slowknl
two more kernels are built. quickknl contains additional assertions and is rarely used 
at a customers site. slowknl contains developer traces and there is the off chance 
that we require such a trace to detect certain problems.

Anything that is missing and that contains 'ni' or 'rfc' in it's name is SAP specific 
and not required.

If there is anything else that's missing from the the binary package, please post it 
here. That will spare me the trouble to compile a non SAPDB_INTERNAL tree and to 
compare the results.

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

Reply via email to