On Wed, 03 Apr 2002 23:28:52 +0200 Nandan Joshi <[EMAIL PROTECTED]> wrote:
NJ> And then it start giving out errors and warnings. And well, the path NJ> given for NJ> Openssl is correct. I have the Openssl 0.9.6b-34, as installed with main NJ> Installation of SuSE 7.3 linux. But still I'm not sure whether I've done NJ> chosing the path for openssl as /usr/lib to /usr/local/ssl. Well, but in NJ> configure it showed no problems, the include folder for openssl was detected NJ> and -lopenssl and -lcrypt gave positive results. But still I can't NJ> understand NJ> where might be the problem. Well, do you need ssl support at all? If not, the best would be to disable ssl support. If you want to debug linking problem, please use "nm" on your libraries to find where missing symbols are hiding. NJ> And one more problem, during configure it doesn't detect python. I have NJ> python2.1 . But why doesn't it get detected when --with-python option is NJ> added. Python is still not very usable, you are not missing a lot without Python support for now. Regards, Nerijus _______________________________________________ Mahogany-Users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/mahogany-users
