> There is another option. You can link it statically by adding the > --enable-static --enable-shared=no parameters. Additionally you would need > to add the list of modules that you would like to get compiled within the > main library. For instance: > > --enable-static-module=file,fcgi,proxy > > or, in case you wanted to statically compile the whole thing: > --enable-static-module=all.
Okay, let's see. This is what I got: 1) Installing last stable cherokee from lenny repositories (0.7.2) works perfectly. 2) Compiling everything statically (with --enable-static-module=all), as Alvaro said, it works fine. I don't get 'dlopen' errors anymore. But I had not python installed and it just silently gave 503 errors. When I enabled -x option, I was getting '/usr/bin/env: python: No such file or directory' errors. I installed python and everything seems to run fine. At last! :) Thank you very much, Gunnar and Alvaro :) Now I am thinking about what happened... If you remember I was saying this: > I tried to copy all the files cherokee wasn't finding to where it could > find them... and it gave no more errors, but the admin interface was > not loading. I didn't try -x parameter at that time, but I am sure that was the problem. So to sum up: it looks like there is a problem with the paths where cherokee finds these files. If you build cherokee so it doesn't have to search libraries in the system, everything goes fine. Or if you build it normally, but fix the location of the files... _______________________________________________ Cherokee mailing list [email protected] http://lists.octality.com/listinfo/cherokee
