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 4:06:22 am
List:net.sourceforge.lists.courier-maildrop

David Hartburn writes:

No joy I'm afraid. I've tried copying libunicode.a and libunicode.la to /usr/local/lib, then compiling with -lunicode. I have also tried pointing directly at that directory: $ gcc -o mdtest -L/usr/local/src/maildrop-2.0.3/unicode/.libs -lunicode -lrfc2045 -lrfc822 mdtest.c /usr/lib/gcc/i386-redhat-linux/3.4.6/../../../librfc822.so: undefined reference to `unicode_convert_fromchset'

If you built these as shared libraries, libunicode should also be built as a shared library.

Any other suggestions?

Yes. You need to undertstand the differences between static and shared libraries, and how they work. This is not something that can be explained in one or two sentences. Read the man pages.

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.