Lucio writes:

On 24/08/18 01:20, Sam Varshavchik wrote:
I looked into it – this is because at the time that the configure script ran, certtool was not found in your PATH, and was defaulted to this. You can adjust the script manually, but there was a problem with your PATH when you ran configure.

Can that PATH problem at configure time be the cause of the IMAP connection problems I'm experiencing now?

In other words, does it make sense to rebuild everything from scratch now that certtool is in the PATH, only hoping to fix the IMAP connection problems? Or should I just fix the script manually and look elsewhere for the IMAP connection problems?

You can't really predict the consequences of what happens if a software package does not get built correctly.

So, rather than to figure out how to fix every little problem that's caused by that, it makes more sense to properly uninstall the incorrectly built package, to whatever degree it's possible, and then rebuild it correctly.

This is why it's always recommended to use your Linux distribution's packaging platform to build and install software, instead of compiling and manually installing it. It makes it much easier to uninstall something.

Attachment: pgpx0E7opBw81.pgp
Description: PGP signature

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Courier-imap mailing list
Courier-imap@lists.sourceforge.net
Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-imap

Reply via email to