can´t compile cyradm
Ken, thank for the first answer to my fisrt problem with cyrus-imapd. But i already have the second stone in my way and the name is CYRADM. The problem is that i have installed cyrus-imap into /opt directory, the library are into /opt/lib/sasl2 and the include files are into /opt/include/sasl. Then, i´km trying to compile cyradm following the documentation and i can´t, the compiled proccess is getting this message. Note (probably harmless): Not found libsasl2 Can any one advice with this? Thank in advanced Danny
Re: can´t compile cyradm
Yes, i did it. My cyrus-imap was compiled with sasl support. Right now, i need to compile the perl scripts and cyradm administrative tool, and here is the the problem. I was looking for into Makefiel.PL and changind the SASL_INC and SASL_LIB values, the compile process finish OK, but executing cyradm i get this errors: [EMAIL PROTECTED] cyrus-imapd-2.2.1-BETA]# /usr/bin/cyradm Can't load '/usr/lib/perl5/site_perl/5.6.1/i386-linux/auto/Cyrus/IMAP/IMAP.so' for module Cyrus::IMAP: /usr/lib/perl5/site_perl/5.6.1/i386-linux/auto/Cyrus/IMAP/IMAP.so: undefined symbol: sasl_client_init at /usr/lib/perl5/5.6.1/i386-linux/DynaLoader.pm line 206. at /usr/lib/perl5/site_perl/5.6.1/i386-linux/Cyrus/IMAP/Admin.pm line 44 Compilation failed in require at /usr/lib/perl5/site_perl/5.6.1/i386-linux/Cyrus/IMAP/Admin.pm line 44. BEGIN failed--compilation aborted at /usr/lib/perl5/site_perl/5.6.1/i386-linux/Cyrus/IMAP/Admin.pm line 44. Compilation failed in require at /usr/lib/perl5/site_perl/5.6.1/i386-linux/Cyrus/IMAP/Shell.pm line 60. BEGIN failed--compilation aborted at /usr/lib/perl5/site_perl/5.6.1/i386-linux/Cyrus/IMAP/Shell.pm line 60. Compilation failed in require. BEGIN failed--compilation aborted. Any advice will be very appreciated Thanks Danny - Original Message - From: Etienne Goyer [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Monday, September 22, 2003 10:39 PM Subject: Re: can´t compile cyradm I guess you want to specify --with-sasl=/opt/include/sasl or something along that line to ./configure. Have you tried it ? On Mon, Sep 22, 2003 at 09:28:57PM +0200, Danny García Hernández wrote: Ken, thank for the first answer to my fisrt problem with cyrus-imapd. But i already have the second stone in my way and the name is CYRADM. The problem is that i have installed cyrus-imap into /opt directory, the library are into /opt/lib/sasl2 and the include files are into /opt/include/sasl. Then, i´km trying to compile cyradm following the documentation and i can´t, the compiled proccess is getting this message. Note (probably harmless): Not found libsasl2 Can any one advice with this? Thank in advanced Danny -- Etienne GoyerLinux Québec Technologies Inc. http://www.LinuxQuebec.com [EMAIL PROTECTED]
Re: can´t compile cyradm
ldd command show: [EMAIL PROTECTED] cyrus-imapd-2.2.1-BETA]$ ldd /usr/lib/perl5/site_perl/5.6.1/i386-linux/auto/Cyrus/IMAP/IMAP.so libssl.so.2 = /lib/libssl.so.2 (0x40018000) libcrypto.so.2 = /lib/libcrypto.so.2 (0x40046000) libc.so.6 = /lib/libc.so.6 (0x4010c000) libdl.so.2 = /lib/libdl.so.2 (0x40233000) /lib/ld-linux.so.2 = /lib/ld-linux.so.2 (0x8000) [EMAIL PROTECTED] cyrus-imapd-2.2.1-BETA]$ I think that i have to problems: 1- Why perl Makefile.PL can´t find my libsasl2 into /opt/lib ? 2- After fix Makefile.PL with the correct path to INCs and LIBs, why i can´t exceute cyradm? Thanks Danny - Original Message - From: Joakim Ryden [EMAIL PROTECTED] To: Danny García Hernández [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Sent: Monday, September 22, 2003 11:55 PM Subject: Re: can´t compile cyradm What does 'ldd /usr/lib/perl5/site_perl/5.6.1/i386-linux/auto/Cyrus/IMAP/IMAP.so' show? --Jo On Monday 22 September 2003 15:21, Danny García Hernández wrote: Yes, i did it. My cyrus-imap was compiled with sasl support. Right now, i need to compile the perl scripts and cyradm administrative tool, and here is the the problem. I was looking for into Makefiel.PL and changind the SASL_INC and SASL_LIB values, the compile process finish OK, but executing cyradm i get this errors: [EMAIL PROTECTED] cyrus-imapd-2.2.1-BETA]# /usr/bin/cyradm Can't load '/usr/lib/perl5/site_perl/5.6.1/i386-linux/auto/Cyrus/IMAP/IMAP.so' for module Cyrus::IMAP: /usr/lib/perl5/site_perl/5.6.1/i386-linux/auto/Cyrus/IMAP/IMAP.so: undefined symbol: sasl_client_init at /usr/lib/perl5/5.6.1/i386-linux/DynaLoader.pm line 206. at /usr/lib/perl5/site_perl/5.6.1/i386-linux/Cyrus/IMAP/Admin.pm line 44 Compilation failed in require at /usr/lib/perl5/site_perl/5.6.1/i386-linux/Cyrus/IMAP/Admin.pm line 44. BEGIN failed--compilation aborted at /usr/lib/perl5/site_perl/5.6.1/i386-linux/Cyrus/IMAP/Admin.pm line 44. Compilation failed in require at /usr/lib/perl5/site_perl/5.6.1/i386-linux/Cyrus/IMAP/Shell.pm line 60. BEGIN failed--compilation aborted at /usr/lib/perl5/site_perl/5.6.1/i386-linux/Cyrus/IMAP/Shell.pm line 60. Compilation failed in require. BEGIN failed--compilation aborted. Any advice will be very appreciated Thanks Danny - Original Message - From: Etienne Goyer [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Monday, September 22, 2003 10:39 PM Subject: Re: can´t compile cyradm I guess you want to specify --with-sasl=/opt/include/sasl or something along that line to ./configure. Have you tried it ? On Mon, Sep 22, 2003 at 09:28:57PM +0200, Danny García Hernández wrote: Ken, thank for the first answer to my fisrt problem with cyrus-imapd. But i already have the second stone in my way and the name is CYRADM. The problem is that i have installed cyrus-imap into /opt directory, the library are into /opt/lib/sasl2 and the include files are into /opt/include/sasl. Then, i´km trying to compile cyradm following the documentation and i can´t, the compiled proccess is getting this message. Note (probably harmless): Not found libsasl2 Can any one advice with this? Thank in advanced Danny -- Etienne GoyerLinux Québec Technologies Inc. http://www.LinuxQuebec.com [EMAIL PROTECTED] !DSPAM:3f6f6e31166561399114306!
Re: can´t compile cyradm
On Monday 22 September 2003 15:45, Danny García Hernández wrote: ldd command show: [EMAIL PROTECTED] cyrus-imapd-2.2.1-BETA]$ ldd /usr/lib/perl5/site_perl/5.6.1/i386-linux/auto/Cyrus/IMAP/IMAP.so libssl.so.2 = /lib/libssl.so.2 (0x40018000) libcrypto.so.2 = /lib/libcrypto.so.2 (0x40046000) libc.so.6 = /lib/libc.so.6 (0x4010c000) libdl.so.2 = /lib/libdl.so.2 (0x40233000) /lib/ld-linux.so.2 = /lib/ld-linux.so.2 (0x8000) [EMAIL PROTECTED] cyrus-imapd-2.2.1-BETA]$ I think that i have to problems: 1- Why perl Makefile.PL can´t find my libsasl2 into /opt/lib ? 2- After fix Makefile.PL with the correct path to INCs and LIBs, why i can´t exceute cyradm? I really don't know because I've never compiled cyradm standalone like that. Chances are if you fix #1 you will automagically fix #2 as well. --Jo
Re: can´t compile cyradm
But i already have the second stone in my way and the name is CYRADM. The problem is
that i have installed cyrus-imap into /opt directory, the library are into
/opt/lib/sasl2 and the include files are into /opt/include/sasl. Then, i´km trying
to compile cyradm following the documentation and i can´t, the compiled proccess is
getting this message.
Note (probably harmless): Not found libsasl2
---
For all of you who install packages into their own directories, under /opt, here is
some advice: *make symbolic links*.
I come from Tru64 UNIX and it inherits on long standing DEC's practice, which can be
summarized as follows:
- make a package (SETLD package in my case), determine which files belong in it
- separate files into subsets (these are RPM equivalents), one package can hold N
subsets
- for each subset separate files as follows:
+ /opt/${PKGNAME} should hold all files needed at startup
This accounts for startup files, kernel modules, etc...
+ /usr/opt/${PKGNAME} should hold all files that do not change during normal
operation
This is the bulk of the package, executables, shared and static libs, header files
configuration files, documentation, static data files,...
+ /var/opt/${PKGNAME} should hold all files that do change during normal operation
These would be spools, logs, databases, mailboxes,...
- for all files that are expected to be in some defined path, make symbolic links
This is handled automatically by the subset control helper routines, for all marked
files
Now, I know that Linux is built with only one /opt directory in mind and I don't
think we can change it now. What most packagers end up with, is treating /opt as
DEC's /usr/opt + /opt, while for /var/opt/${PKG} they create links to
/var/some dir.
So, create symbolic links. That will make your life substantially easier.
Nix.
