What does DBEnv_set_timeout() actually do in its source code? Graham
On 16 June 2011 01:43, Julen Ruiz Aizpuru <[email protected]> wrote: > az., 2011.eko ekaren 15a 15:24(e)an, Julen Ruiz Aizpuru(e)k idatzi zuen: >> >> az., 2011.eko ekaren 15a 13:30(e)an, Julen Ruiz Aizpuru(e)k idatzi zuen: >>> >>> az., 2011.eko ekaren 15a 13:03(e)an, Graham Dumpleton(e)k idatzi zuen: >>>> >>>> On 15 June 2011 18:58, Julen Ruiz Aizpuru<[email protected]> wrote: >>>>> >>>>> libdbxml is built on top of libdb, so when compiling DB-XML I also >>>>> compiled >>>>> libdb, libxqilla and libxerces. Those libraries were previously >>>>> installed on >>>>> the system (by some berkeley db package, I presume). The compiled >>>>> libraries >>>>> reside in /usr/local/lib/. >>>> >>>> For the ones that were installed previously, were there header files >>>> also installed. Any chance they are still on the box somewhere and >>>> they were picked up incorrectly when you built from source code? >>>> >>> >>> Actually I meant that the libraries were installed at compile time and >>> *nowadays they are* too. Sorry if it wasn't clear from the beginning. >>> >>> And yes, I can see -dev packages for libdb, libxqilla and libxerces, so >>> the header files are also installed. >>> >>> I'll try to recompile libdbxml by explicitely setting the library source >>> paths — the build script picks up all the sources for the mentioned >>> libraries from the downloaded tarball by default, so this may not have >>> any effects after all. I'll give it a shot anyway. >> >> Did a fresh compilation but no luck with this :/ Any more thoughts? >> >> By the way, I didn't say that I'm using virtualenv for this deployment. > > OK, I think I got it. > > As in the thread from this mailing list mentioned on my first post[1], there > was a function call that was messing things up. I got there by putting > prints throughout the code until I found the exact line that was failing. > DB-XML didn't like a query on my code that was working locally(!). > > As you see DB-XML is not very developer-friendly... maybe a note on the wiki > warning users about possible weird behaviours with this module should help > others in order to avoid headaches. > > Thanks again for your help and attention. > > [1] https://groups.google.com/forum/#!topic/modwsgi/0j4YrMIRe50 > > -- > You received this message because you are subscribed to the Google Groups > "modwsgi" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/modwsgi?hl=en. > > -- You received this message because you are subscribed to the Google Groups "modwsgi" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/modwsgi?hl=en.
