> From: Gaganis Giorgos [mailto:[EMAIL PROTECTED]
> I have tried to build MaxDB on Linux.
> the script installsources.pl which at some point contained a
> reference
> to a directory named SAPDB_ORG which was obviously changed to
> MaxDB_ORG.
I fixed it so it won't appear in the next version.
> connect error -709
> caution: Can't get a buildnumber. Won't use buildnumber.
This is to be expected if the build is started outside of the SAP environment.
> sql__ckl.c fast
> sql__ckl.c: In function `sql__ckl':
> sql__ckl.c:61: error: `_SC_CLK_TCK' undeclared (first use in
This looks like a porting problem. Could you try to find out which system header
defines _SC_CLK_TCK. That include is probably missing from sys/src/libptc/sql__clock.c
> !dbmcli -s -R $INSTROOT inst_reg -k $INSTROOT -c
> Failed to get indep data work path:Open Registry:No such file
> or directo\
> ryIndepData [0:No system errortext for ERRNO 0]
> Error! Connection failed to node (local) for database (no
> dbname): Erro\
> r writing to pipe:(32:Broken pipe) A
> COMMAND error 2
There are some instructions missing in sources.readme, as the global registry
has changed from 7.4 to 7.5. The following will be part of the next sources.readme:
== Prerequisites ==
- The build tools must be installed
- UNIX/Linux: curses header files and libraries must be installed
- UNIX/Linux: Create the file /etc/opt/sdb, which must be
world readable and contain the following lines:
[Globals]
IndepData=<indep_data_path>
IndepPrograms=<indep_programs_path>
SdbOwner=<current_user>
SdbGroup=<primary_group_of_current_user>
where
<indep_dat_path>:
- an existing directory
- subdirectories wrk and config must exist and be
writable by <current_user>
- this is the default directory for newly created
databases, so it shouldn't be placed on a small
partition
<indep_programs_path>: not used by the development
environment (because $SAPDB_NO_INDEPPATH is set)
<current_user>: You could use another user, but this would
require that the following program in $TOOL/bin
are set to suid root:
instdbmverifypw
<primary_group_of_current_user>:
If the file /etc/opt/sdb exists from another MaxDB
installation, then it is best to replace the existing file
during development. Otherwise you would overwrite files
in your current installation.
The remaining errors appear to be caused by the previouus errors.
Daniel Dittmar
--
Daniel Dittmar
SAP Labs Berlin
[EMAIL PROTECTED]
--
MaxDB Discussion Mailing List
For list archives: http://lists.mysql.com/maxdb
To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
