[Kolab-devel] [Partial SUMMARY] Installation of Kolab2 2.1.0 Final on Solaris 10 11/06 Sparc
ComCept Net GmbH Andrea Soliva
soliva at comcept.ch
Sat May 19 15:42:52 CEST 2007
Hi all
Ok here my summary what is the situation at the moment:
Using Solaris 11/06 Sparc Recommended Cluster May 2007 kolab2 2.1.0 final.
Base to compile are sunfreeware package meaning following package and
adjustments has to be done:
SMCautoc autoconf autoconf-2.60-sol10-sparc-local.gz
SMCautom automake automake-1.10-sol10-sparc-local.gz
SMCbison bison bison-2.3-sol10-sparc-local.gz
SMCflex flex flex-2.5.4a-sol10-sparc-local.gz
SMCgcc gcc gcc-3.4.6-sol10-sparc-local.gz
SMCgrep grep grep-2.5.1a-sol10-sparc-local.gz
SMCliconv libiconv libiconv-1.9.2-sol10-sparc-local.gz
SMCmake make make-3.81-sol10-sparc-local.gz
SMCncurs ncurses ncurses-5.6-sol10-sparc-local.gz
SMCpcre pcre pcre-6.7-sol10-sparc-local.gz
SMCtexi textinfo texinfo-4.8-sol10-sparc-local.gz
# crle
--------------- output of crle ---------------
Default configuration file (/var/ld/ld.config) not found
Default Library Path (ELF): /lib:/usr/lib (system default)
Trusted Directories (ELF): /lib/secure:/usr/lib/secure (system
default)
--------------- output of crle ---------------
Add "/usr/local/lib":
# crle -l /lib:/usr/lib:/usr/local/lib
# crle
--------------- output of crle ---------------
Default configuration file (/var/ld/ld.config) not found
Default Library Path (ELF): /lib:/usr/lib:/usr/local/lib (system
default)
Trusted Directories (ELF): /lib/secure:/usr/lib/secure (system
default)
--------------- output of crle ---------------
# cat /root/.profile
--------------- /root/.profile ---------------
# This is the default standard profile provided to a user.
# They are expected to edit it to meet their own needs.
MAIL=/usr/mail/${LOGNAME:?}
ENV=$HOME/.kshrc
PATH=/usr/sbin:/usr/bin:/usr/dt/bin:/usr/openwin/bin:/bin:/usr/ucb:/opt/sfw/
bin:/usr/local/bin:/usr/ccs/bin
TERM=vt100
export ENV PATH
--------------- /root/.profile ---------------
If following link will not be done error appears within kolab compilation
meaning "can not create executables....":
# ln -s /usr/local/bin/gcc /usr/bin/cc
# ls -la /usr/bin/cc
lrwxrwxrwx 1 root root 18 Feb 17 19:17 /usr/bin/cc ->
/usr/local/bin/gcc
In the first try I had the error message within the postfix compilation:
****************************************************************************
******
/usr/include/rpc/svc.h:19:28: error: sys/tsol/label.h: No such file or
directory
In file included from /usr/include/rpc/rpc.h:42,
from /usr/include/rpcsvc/nis.h:9,
from dict_nisplus.c:48:
/usr/include/rpc/svc.h:86: error: syntax error before 'bslabel_t'
make: *** [dict_nisplus.o] Error 1
make: *** [update] Error 1
error: Bad exit status from /kolab/RPM/TMP/rpm-tmp.12530 (%build)
RPM build errors:
Bad exit status from /kolab/RPM/TMP/rpm-tmp.12530 (%build)
****************************************************************************
******
I could solve the problem with updating the header information from my gcc
meaning sunfreeware gcc (seems to be an issue because of a patch within
recommended cluster April 2007 which updates some headers SUNWhea SUNWcsu)
Following has to be done:
cd /usr/local/lib/gcc/sparc-sun-solaris2.10/3.4.6/install-tools
Put the line SHELL=/bin/sh on the first line of the mkheaders.conf file.
Then run
/opt/local/libexec/gcc/sparc-sun-solaris2.10/3.4.6/install-tools/mkheaders
This will correct some header files and make the build gcc usable on higher
builds.
After that I start from scratch again to compile kolab2 2.1.0 final and
postfix could successful compiled but I had another error which I can not
solve at the moment. It is within the configure of php 4.4.0 meaning for
some reason db4 will not be recognized. In the first view I thought the
check looks for a db4 on the system but after looking cloose to it I
recognized that the check looks in the kolab dir for db.h meaning
installation of db-4.3.29.0-2.5.0.src.rpm. Is this correct....?
It is a little bit a pitty because if I can solve this issue I'm pretty sure
kolab will compile successful because php is needed by apache but if these
twos are not available kolab-framework etc. will not compile etc. etc.
Anybody a idea what can be tried etc.? Any help really appriciated!?
****************************************************************************
******
checking for cyrus imap support... no
checking for xDBM support... no
checking whether to enable DBA... no
checking for GDBM support... no
checking for NDBM support... no
checking for db4 major version... configure: error: Header contains
different version
+ /kolab/bin/make --no-print-directory
make: *** No targets specified and no makefile found. Stop.
+ /kolab/bin/make --no-print-directory install
INSTALL_ROOT=/kolab/RPM/TMP/apache-1.3.33-root
make: *** No rule to make target `install'. Stop.
+ exit 2
error: Bad exit status from /kolab/RPM/TMP/rpm-tmp.23244 (%build)
****************************************************************************
******
I recognzed by the way something which from my point of view should be
adjusted meaning following error was found in the build.log:
****************************************************************************
******
Preparing...
##################################################
kolabd
##################################################
Installing crontab entry
crontab: illegal option -- u
crontab: proper usage is:
crontab [file | -e | -l | -r ] [user]
crontab: proper usage is:
crontab [file | -e | -l | -r ] [user]
For a fresh install please initialize Kolab by running
'/kolab/etc/kolab/kolab_bootstrap -b' as user root.
If you upgraded from a previous version simply refresh Kolab by running run
'/kolab/sbin/kolabconf' as user root.
In every case execute '/kolab/bin/openpkg rc kolabd restart' as user root.
****************************************************************************
******
On Solaris a "u" option does not exists. What entry does this add to the
crontab and to which user?
Another issues is also not so bad but must be known otherwise all fails
(files can not be upgraded because they are in use):
If you try to upgrade an existing 2.0.x Installation it is recommended to
stop kolab before starting the upgrade with "sh obmtool kolab 2>&1 | tee
kolab-build.log". This is not possible because even you stop all (nothing
anymore running) the compilation/installation process starts kolab after
initiating "sh obmtool kolab 2>&1 | tee kolab-build.log" (after 3 minutes).
The reason for this is to be found in the way "SFM" (Service Facility
Management) is working. This means the compilaton/installation process
copies kolab.xml in the manifest directory and it seems that the file is
asap imported. The confirmation of that is that after starting the
compilaton/installation process you see a new service with svcs -x kolab.
Even you try to stop kolab with the init script it starts kolab again and
again (base functionality of SFM..meaining if something fails it starts the
service again automaticaly). A solution would be to indicate in the specific
position within the process of compilation/installation a svcadm disable -t
kolab. This would disable kolab temporarly.
At the moment it is a little bit frustratin for me because I'm 100% sure if
the issue with php could be solved kolab would successful compile. I do not
know if it is visible to use a newer php version because within the existing
package I saw a lot of patch's etc. Another way would be to find out "why is
the specific db4 in kolab2 not recognized". I controlled the installation of
db4 meaning db-4.3.29.0-2.5.0.src.rpm and this was successful without any
errors?!?
Again any hints very appriciated.
Kind regards
Andrea
More information about the devel
mailing list