Thanks for the reply, Alain.  Here is what the config.log says:

This file contains any messages produced by compilers while
running configure, to aid debugging if configure makes a mistake.

configure:595: checking host system type
configure:616: checking target system type
configure:634: checking build system type
configure:689: checking for a BSD compatible install
configure:742: checking whether ln works
configure:766: checking whether ln -s works
configure:1808: checking for gcc
configure:1921: checking whether the C compiler (cc -fPIC ) works
configure:1937: cc -o conftest -fPIC   conftest.c  1>&5
/usr/lib/gcc/x86_64-linux-gnu/3.4.6/libgcc_s.so: file not recognized: File format not recognized
collect2: ld returned 1 exit status
configure: failed program was:

#line 1932 "configure"
#include "confdefs.h"

main(){return(0);}


Alain Spineux wrote:

some idea : - 1 - in your first email, I read : 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) Did you look at config.log ? - 2 - you can try to find debian source files for gcc-4.0.2 or close, compile it and compare the log and maybe the result - 3 - You could try to get the last binutils, gcc, and maybe openpkg and openpkg-tools package from from openpkg site, integrate them in your kolab build system and make a try. To rebuild the 00INDEX.rdf make a search on the list archive, maybe the devel one for one of one of my post. Regards. On Dec 5, 2007 4:24 PM, Paul Waldo <paul <at> waldoware.com> wrote:

Anyone else care to take a stab? Here is the synopsis: Running Kubuntu Gutsy **64-bit**, trying to compile either the stable or beta version results in problems compiling GCC (below). Thanks for any help!! checking for C compiler default output file name... configure: error: C compiler cannot create executables Paul Waldo wrote:

Gunnar Wrobel wrote:

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.

Hi Gunnar, I tried the beta version and did exactly as described at http://max.kde.org:8080/mirrors/ftp.kolab.org/server/release/kolab-server-2.1.0/sources. Unfortunately I got the same problem trying to compile gcc (see below). I can send you the entire output if it will help. I even tried the GCC switch at http://wiki.kolab.org/index.php/Ubuntu_6.06. BTW, this is a Kubunty Gutsy AMD64 machine. Any help would be appreciated! Paul shtool:subst:Warning: substitution resulted in no content change on any file + case "amd64-linux2.6" in + /kolab/lib/openpkg/shtool subst -e s/GLIBCXX_IS_NATIVE=false/GLIBCXX_IS_NATIVE=true/g -e 's/test x.gcc_no_link = xyes/false/g' libstdc++-v3/configure + exit 0 Executing(%build): env -i /kolab/lib/openpkg/bash --norc --noprofile --posix -e /kolab/RPM/TMP/rpm-tmp.68549 + cd /kolab/RPM/TMP + cd gcc-4.0.2 + mkdir obj + cd obj + l_with_gnu_ld_as= + l_with_gnu_ld_as=' --with-gnu-ld --with-ld=/kolab/bin/ld' + l_with_gnu_ld_as=' --with-gnu-ld --with-ld=/kolab/bin/ld --with-gnu-as --with-as=/kolab/bin/as' + case "amd64-linux2.6" in + l_enable_threads=posix + case "amd64-linux2.6" in + l_enable_languages=c + l_enable_languages=c,c++ + echo am_cv_func_iconv=no + echo am_cv_lib_iconv=no ++ pwd + CC=cc + CFLAGS=-fPIC + CONFIG_SHELL=/kolab/lib/openpkg/bash + ../configure --cache-file=./config.cache --srcdir=/kolab/RPM/TMP/gcc-4.0.2/obj/.. --prefix=/kolab --exec-prefix=/kolab --includedir=/kolab/include/gcc --libexecdir=/kolab/libexec/gcc --with-gxx-include-dir=/kolab/include/g++ --with-local-prefix=/kolab/lib/gcc --enable-languages=c,c++ --enable-threads=posix --disable-maintainer-mode --disable-shared --disable-nls --with-gnu-ld --with-ld=/kolab/bin/ld --with-gnu-as --with-as=/kolab/bin/as loading cache ./config.cache checking host system type... x86_64-unknown-linux-gnu checking target system type... x86_64-unknown-linux-gnu checking build system type... x86_64-unknown-linux-gnu checking for a BSD compatible install... /usr/bin/install -c checking whether ln works... yes checking whether ln -s works... yes checking for gcc... cc checking whether the C compiler (cc -fPIC ) works... no configure: error: installation or configuration problem: C compiler cannot create executables. error: Bad exit status from /kolab/RPM/TMP/rpm-tmp.68549 (%build) RPM build errors: Bad exit status from /kolab/RPM/TMP/rpm-tmp.68549 (%build) obmtool:WARNING: install failure. Missing /kolab/RPM/PKG/gcc-4.0.2-2.5.0.amd64-ubuntu7.10-kolab.rpm ------------------------------------------------------------------------

_______________________________________________ Kolab-users mailing list Kolab-users <at> kolab.org https://kolab.org/mailman/listinfo/kolab-users

_______________________________________________ Kolab-users mailing list Kolab-users <at> kolab.org https://kolab.org/mailman/listinfo/kolab-users

_______________________________________________
Kolab-users mailing list
Kolab-users <at> kolab.org
https://kolab.org/mailman/listinfo/kolab-users