Install help for Kolab newbie

Gunnar Wrobel wrobel at pardus.de
Mon Dec 3 16:00:57 CET 2007


Gunnar Wrobel <wrobel at pardus.de> writes:

> Paul Waldo <paul at waldoware.com> writes:
>
>> Hi all,
>>
>> I have been trying to evaluate Kolab, without much success.  Before I
>> moved to another groupware solution, I thought I'd try to get some help
>> from the experts :-)
>>
>> I'm running a Kubuntu Gusty AMD64 machine.  I first tried the kolab
>> packages that came with the OS.  I successfully ran kolab_bootstrap, but
>> now when I try to get initially logged in via the web admin interface
>> (https://kolab.mydomain/admin/), I just get a blank page.  I've looked
>> in the apache logs, but the only thing of note I see is
>> 10.0.0.10 - - [30/Nov/2007:13:54:49 +0000] "GET /admin/ HTTP/1.1" 200 -
>> Not very interesting...
>> I'm not sure where to procede from her in debugging.  Ubuntu packages
>> would be my preferred method of install, but just to be thourough, I
>> figured I would try compiling from source.  This is on a Kubuntu 6.06 box.
>
> The Kolab server is a rather complex structure of many different
> components. This makes all the native ports of Kolab rather
> problematic. They do not tend to have the same kind of quality you get
> from the OpenPKG variant. The OpenPKG based install can be far better
> quality tested since the devs are in full control of the environment.
>
>>
>> I got all of the files from
>> http://max.kde.org:8080/mirrors/ftp.kolab.org/server/release/kolab-server-2.1.0/sources/
>> I followed the instructions at
>> http://wiki.kolab.org/index.php/Ubuntu_6.06 to get gcc 3.4
>> I followed the intructions at
>> http://wiki.kolab.org/index.php/Kolab2_Installation_-_Source
>>
>> Compilation fails like this:
>> pwd: /kolab/RPM/TMP/gcc-4.0.2/obj/x86_64-unknown-linux-gnu/libstdc++-v3
>> Running configure in multilib subdir 32
>> pwd: /kolab/RPM/TMP/gcc-4.0.2/obj/x86_64-unknown-linux-gnu
>> mkdir 32
>> configure: creating cache ./config.cache
>> checking build system type... x86_64-unknown-linux-gnu
>> checking host system type... x86_64-unknown-linux-gnu
>> checking target system type... x86_64-unknown-linux-gnu
>> checking for a BSD-compatible install... /usr/bin/install -c
>> checking whether build environment is sane... yes
>> checking for gawk... no
>> checking for mawk... mawk
>> checking whether /kolab/bin/make --no-print-directory sets $(MAKE)... yes
>> checking for x86_64-unknown-linux-gnu-gcc...
>> /kolab/RPM/TMP/gcc-4.0.2/obj/gcc/xgcc
>> -B/kolab/RPM/TMP/gcc-4.0.2/obj/gcc/
>> -B/kolab/x86_64-unknown-linux-gnu/bin/
>> -B/kolab/x86_64-unknown-linux-gnu/lib/ -isystem
>> /kolab/x86_64-unknown-linux-gnu/include -isystem
>> /kolab/x86_64-unknown-linux-gnu/sys-include  -m32
>> checking for C compiler default output file name... configure: error: C
>> compiler cannot create executables
>> See `config.log' for more details.
>> make[1]: *** [configure-target-libstdc++-v3] Error 1
>> make: *** [bootstrap-lean] Error 2
>> error: Bad exit status from /kolab/RPM/TMP/rpm-tmp.49252 (%build)
>>
>> Any help with either of these install scenarios would be greatly
>> appreciated!  TIA.
>
> You basically hit this bug:
>
> http://wiki.kolab.org/index.php/Ubuntu_6.06
>
> You can either try to follow the instructions given there or you can
> try the current beta version. I'd actually suggest the latter.

Sorry, I didn't read well enough. You problem is related to using a
64bit machine. I'd definitely suggest using the latest beta then.

Cheers,

Gunnar

>
> While OpenPKG has the advantage of providing a very stable and
> controlled environment we always have the problem that our stable
> server versions get outdated at some point and we collect more and
> more problems installing on newer distribution versions.
>
> In general we try to collect the required workarounds in the wiki.
>
>
>>
>> Paul
>>
>> PS
>> Is there a demo server that I can access just to see how kolab works?
>> I'd hate to go through all this effort only to find that it doesn't fit
>> my needs :-(
>
> I'm sorry, we don't have that at the moment. But now that the Horde
> webmail is available we should consider setting one up. Without Horde
> you wouldn't have had too much to see to be honest :)
>
> Cheers,
>
> Gunnar
>
> -- 
> ______ http://kdab.com _______________ http://kolab-konsortium.com _
>
> p at rdus Kolab work is funded in part by KDAB and the Kolab Konsortium
>
> ____ http://www.pardus.de _________________ http://gunnarwrobel.de _
> E-mail : p at rdus.de                                 Dr. Gunnar Wrobel
> Tel.   : +49 40 432 72335                           Bundesstrasse 29
> Fax    : +49 40 432 70855                            D-20146 Hamburg
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>    >> Mail at ease - Rent a kolab groupware server at p at rdus <<                 
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>
> _______________________________________________
> Kolab-users mailing list
> Kolab-users at kolab.org
> https://kolab.org/mailman/listinfo/kolab-users

-- 
______ http://kdab.com _______________ http://kolab-konsortium.com _

p at rdus Kolab work is funded in part by KDAB and the Kolab Konsortium

____ http://www.pardus.de _________________ http://gunnarwrobel.de _
E-mail : p at rdus.de                                 Dr. Gunnar Wrobel
Tel.   : +49 40 432 72335                           Bundesstrasse 29
Fax    : +49 40 432 70855                            D-20146 Hamburg
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
   >> Mail at ease - Rent a kolab groupware server at p at rdus <<                 
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~




More information about the users mailing list