7 messages in net.sourceforge.lists.courier-maildropRe: [maildropl] Problems using rfc822...
FromSent OnAttachments
Dave HartburnFeb 26, 2007 5:16 am 
Sam VarshavchikFeb 26, 2007 3:15 pm 
Dave HartburnFeb 27, 2007 2:04 am 
Sam VarshavchikFeb 27, 2007 4:06 am 
Dave HartburnFeb 27, 2007 6:04 am 
Sam VarshavchikFeb 27, 2007 3:19 pm 
Dave HartburnFeb 28, 2007 2:28 am 
Actions with this message:
Paste this link in email or IM:
Paste this link in email or IM:
Atom feed for this thread
Paste this URL into your reader:
Subject:Re: [maildropl] Problems using rfc822 and rfc2045 librariesActions...
From:Sam Varshavchik (mrs@courier-mta.com)
Date:Feb 27, 2007 3:19:27 pm
List:net.sourceforge.lists.courier-maildrop

Dave Hartburn writes:

First of all, I don't see how you got librfc822, and others, built as shared libraries. Maildrop's default makefile always builds them as static libraries. You must've hacked the makefile to do that. Well, since that would be your hacks, the old saying goes: you break it, you get to pick up the pieces.

No hacking, this appears to be the default. Incase it was something odd on CentOS, I've tried it on an Ubuntu system, just doing: Download and unpack maildrop-2.0.3 ./configure --with-devel make make install-strip make install-man

as per the instructions. Both systems produce shared libs without any modifications at all.

I find that rather odd. Something must get triggered in libtool for those distribution only -- it does not happen on Fedora.

Do you have the libtool package installed? That is, libtool, libtool-ltld, and libtool-ltdl-devel packages?

I will see if I can build libunicode shared and see what happens.

No. It should be the other way around.