Install help for Kolab newbie

[Matthew Smart]

I went through the same problems as you, and eventually just tried
this. It's a nice clean way of installing without interfering with any
system packages. It essentially builds kolab in a chrooted
environment. Using the same kubuntu system, the guide here worked
perfectly for me:

http://wiki.kolab.org/index.php/Kolab2_Installation_-_Beta_Sources


Regards,

Matt

On Nov 30, 2007 12:22 PM, Paul Waldo <paul at waldoware.com> wrote:
> 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.
>
> 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.
>
> 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 :-(
>
> _______________________________________________
> Kolab-users mailing list
> Kolab-users at kolab.org
> https://kolab.org/mailman/listinfo/kolab-users
>