Re: weird problems on sparc with loading cyrus-imapd21 IMAP extension for cyradm perl script
Greg A. Woods <woods <at> weird.com>
2003-10-02 19:17:34 GMT
[ On Thursday, October 2, 2003 at 16:50:08 (+0200), Stoned Elipot wrote: ]
> Subject: Re: weird problems on sparc with loading cyrus-imapd21 IMAP extension for cyradm perl script
> On Wed, Oct 01, 2003 at 04:10:48PM -0400, Greg A. Woods wrote:
> > If this could be the issue then the problem may be with my libsasl2
> > libraries since at the moment I have only libsasl2.a. However on i386
> > where "cyradm" works I also have only the static-only libsasl2.a and it
> > was most definitely not compiled with '-fPIC'. Is '-fPIC' not
> > universally necessary on i386 for all objects in loadable modules?
> I believe so.
Hmmm... then why does it work?
And why does the dynamic loader on sparc produce such a content free
(and/or misleading) error message when it doesn't work?
> Why don't you have a shared libsasl2.a? Is that on
> purpose ?
As you may know I've got a hate-on for all things dynamic.
Now of course I'm willing to bend to accomodate certain things where
dynamic loading is the easier approach, and perl interpreter extensions
are examples such places (besides Makefile.aperl support is currently
quite broken on NetBSD, at least for pkgsrc modules, not to mention that
cyradm itself would need a minor bit more hacking to use the custom perl
interpreter containing the IMAP extensions).
Normally though I would build a full compliment of static and shared