<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<META NAME="Generator" CONTENT="MS Exchange Server version 5.5.2657.73">
<TITLE>RE: Kolab-OpenPKG segfault while compiling GCC...</TITLE>
</HEAD>
<BODY>
<P><FONT SIZE=2>Thank you for your answer !</FONT>
</P>
<P><FONT SIZE=2>In fact it was not GCC compiling process that was failing, but the command /bin/as used in its configure which is crashing. I tried to launch /kolab/bin/as by hand , and guess what ... it crashed whatever argument I gave it! So I guess something is wrong with binutils package first. May be it would be a good idea to look the way official debian packages are built.</FONT></P>
<BR>
<P><FONT SIZE=2>Regards,</FONT>
</P>
<P><FONT SIZE=2>Christophe Painchaud</FONT>
</P>
<P><FONT SIZE=2>-----Message d'origine-----</FONT>
<BR><FONT SIZE=2>De : Franz Skale [<A HREF="mailto:frankenheimer@para.cc">mailto:frankenheimer@para.cc</A>] </FONT>
<BR><FONT SIZE=2>Envoyé : Tuesday, June 06, 2006 9:19 PM</FONT>
<BR><FONT SIZE=2>À : PAINCHAUD Christophe; kolab-users@kolab.org</FONT>
<BR><FONT SIZE=2>Objet : Re: Kolab-OpenPKG segfault while compiling GCC...</FONT>
</P>
<P><FONT SIZE=2>Dear Christophe !</FONT>
</P>
<P><FONT SIZE=2>I am playing around about 1 month getting kolab working on debian pure 64.</FONT>
<BR><FONT SIZE=2>What i can say is, that i had the same troubles like you.</FONT>
<BR><FONT SIZE=2>My gcc didn't compile an the build process always terminated.</FONT>
<BR><FONT SIZE=2>You have to use the switch --disable-multilib. I found the hint on an </FONT>
<BR><FONT SIZE=2>forum in the internet.</FONT>
<BR><FONT SIZE=2>But that's not enough. The next prob you will run into is the thread </FONT>
<BR><FONT SIZE=2>problem in the openldap build.</FONT>
<BR><FONT SIZE=2>The reason is very hidden. The problem is the db4 library.</FONT>
<BR><FONT SIZE=2>You have to enable the thread support in db4 too.</FONT>
<BR><FONT SIZE=2>I wonder that all packages i built weren't 64 bit clean.</FONT>
<BR><FONT SIZE=2>So i began to port on package on another.</FONT>
<BR><FONT SIZE=2>It was very tricky.</FONT>
<BR><FONT SIZE=2>So, on now, my build is runnig. But there's problem with the amavis.</FONT>
<BR><FONT SIZE=2>I ported all perl-packages to 5.8.8 (openpkg cvs mirror) but the error </FONT>
<BR><FONT SIZE=2>still remains.</FONT>
<BR><FONT SIZE=2>Amavis always segfaults if spamassassin and clamav are enabled.</FONT>
<BR><FONT SIZE=2>This is reproducable with the version 2.3.3 - 2.4.1 which i tried all </FONT>
<BR><FONT SIZE=2>one by one.</FONT>
<BR><FONT SIZE=2>Is there a working config for clamav and spamassasin for kolab ? Please </FONT>
<BR><FONT SIZE=2>provide me the config. I tried all the configs i found on the net.</FONT>
<BR><FONT SIZE=2>So for my setup, i disabled amavis in the postfix config. I use </FONT>
<BR><FONT SIZE=2>clamsmtpd to scan mails vor viruses.</FONT>
<BR><FONT SIZE=2>Btw, the debian packages i tried first weren't working.</FONT>
<BR><FONT SIZE=2>So if you or the kolab group provide me an upload space, i will upload </FONT>
<BR><FONT SIZE=2>all src.rpm and amd64 rpms to install kolab without troubles on debian </FONT>
<BR><FONT SIZE=2>pure64.</FONT>
<BR><FONT SIZE=2>I would be pleased to someone honor my porting and provide me an upload </FONT>
<BR><FONT SIZE=2>space.</FONT>
</P>
<P><FONT SIZE=2>Specs:</FONT>
<BR><FONT SIZE=2>I used the beta1 repository for my build.</FONT>
<BR><FONT SIZE=2>I used the openpackage cvs repository for perl 5.8.8 bindings.</FONT>
<BR><FONT SIZE=2>I patched nearly al spec files.</FONT>
</P>
<P><FONT SIZE=2>Some questions: Why you don't disable the mulitlib support and make a </FONT>
<BR><FONT SIZE=2>configure rule to find the right arch for the build ?</FONT>
</P>
<P><FONT SIZE=2>Thanks in advance</FONT>
</P>
<P><FONT SIZE=2>Franz</FONT>
</P>
</BODY>
</HTML>