I don't think you want or need to include the version or architecture in
your path. And I think you want a space after the I. So try:
x) exec perl -MCyrus::IMAP::Shell -I /usr/lib/perl5/site_perl -e shell -- ${1+"$@"} ;;
And frankly, that path is already probably in your include path (try perl
On Fri, 28 May 2004, Kent L. Nasveschuk wrote:
> This is what I added but I get the same db_version error :(
> I have yet to get this to run, very frustrating. It obviously works
> people use it. I'm so close on this...
>
>
> case "x$BASH_VERSION" in
> x) exec perl -MCyrus::IMAP::Shell
> -I/usr/
On Fri, 28 May 2004, Kent L. Nasveschuk wrote:
> This is what I added but I get the same db_version error :( I have yet
> to get this to run, very frustrating. It obviously works people use it.
> I'm so close on this...
Yes, when you said "path problem", I assumed that it was the same as
mine.
This is what I added but I get the same db_version error :(
I have yet to get this to run, very frustrating. It obviously works
people use it. I'm so close on this...
case "x$BASH_VERSION" in
x) exec perl -MCyrus::IMAP::Shell
-I/usr/lib/perl5/site_perl/5.8.0/i486-linux -e shell -- ${1+"$@"} ;;
*)
On Fri, 28 May 2004, Kent Nasveschuk wrote:
> Hello,
> You had a perl path problem back in April in cyradm (Cyrus IMAP) that it
> seems many people had. I was just wondering if you solved it and exactly
> what you did to solve it. I have Cyrus 2.2.4 installed and working on a
> test machine with e
Hello,
You had a perl path problem back in April in cyradm (Cyrus IMAP) that it
seems many people had. I was just wondering if you solved it and exactly
what you did to solve it. I have Cyrus 2.2.4 installed and working on a
test machine with exception of cyradm. Any help would be appreciated,
> On Tue, 20 Apr 2004, Joe Rhett wrote:
> > But if you will accept a patch that modifies the makemaker stuff, I'll hack
> > one out over the next week or so, just so that we can stop getting the same
> > FAQ from everyone ;-)
On Tue, Apr 20, 2004 at 03:37:02PM -0400, Rob Siemborski wrote:
> Yes.
On Tue, 20 Apr 2004, Joe Rhett wrote:
> > On Tue, 20 Apr 2004, Joe Rhett wrote:
> > > But if you will accept a patch that modifies the makemaker stuff, I'll hack
> > > one out over the next week or so, just so that we can stop getting the same
> > > FAQ from everyone ;-)
>
> On Tue, Apr 20, 2004 a
On Tue, 20 Apr 2004, Joe Rhett wrote:
> No, mostly because I'm not that good with makemaker. When I wrote the
> original I was hoping to inspire someone to Do The Right Thing. But after
> looking at the layout, I'm not sure what you gain -- you'll have to add the
> Makemaker stuff to the autocon
There's nothing like coming back to your own words a while later to make
you realize what a wining b-otch you sounded like when you said: (more below)
> On Thu, 15 Apr 2004, Joe Rhett wrote:
> > This has been an ongoing bug that is indecently easy to fix, but Rob won't
> > accept any patches on it
On Thu, 15 Apr 2004, Joe Rhett wrote:
> This has been an ongoing bug that is indecently easy to fix, but Rob won't
> accept any patches on it. He evidently thinks that installing modules into
> the sitewide perl installation is the right idea. I believe that it's
> plain wrong, and want to use t
cyradm and really any script you run that fails because of the error you
listed. And yes, the lines that execute perl.
On Fri, Apr 16, 2004 at 09:29:03AM +0100, Neil Marjoram X 663711 wrote:
> Joe,
>
> Thanks for this, can you tell me which files I need to change. I assume
> that you mean cyradm
Joe,
Thanks for this, can you tell me which files I need to change. I assume
that you mean cyradm and to change the lines that execute the perl
command.
Thanks,
Neil.
On Thu, 2004-04-15 at 15:55, Joe Rhett wrote:
> Neil, open the files in question and modify the four real lines of the
> script
Neil, open the files in question and modify the four real lines of the
script so that you have -I/install/location/lib to where the perl modules are.
This has been an ongoing bug that is indecently easy to fix, but Rob won't
accept any patches on it. He evidently thinks that installing modules in
Some further information :
Cyrus was configured with :
./configure --with-openssl=/usr/local/ssl --with-libwrap=/usr/local
--with-sasl=/usr/local
I had to move the sasl header files into the imap source tree under
sasl/ otherwise it complained they were not present.
The configure complained a
Thanks for that, I have now recompiled SASL and imap in the default
location, it seems the PREFIX is set in the Perl makefile for imap, and
thus it loads in the Cyrus tree instead of the Perl tree. My recompile
used default locations and now all is installed where I think it should
be. How ever it
On Thursday 15 April 2004 12:37, Neil Marjoram X 663711 wrote:
> I have found the Cyrus Perl module located in the directory I installed
> cyrus in : /opt/cyrus/lib/perl5/site_perl/5.8.0/sun4-solaris/. How do I
> get it installed in the Perl tree?
Did you install cyrus imap from a precompiled pack
17 matches
Mail list logo
