On 2010-05-20 at 19:18:35 [+0200], Jorma Karvonen <karvonen.jorma@xxxxxxxxx> wrote: > 2010/5/20 Rene Gollent <anevilyak@xxxxxxxxx>: > > On Thu, May 20, 2010 at 12:56 PM, Jorma Karvonen > > <karvonen.jorma@xxxxxxxxx> wrote: > >> I wonder if this is really a bug or because I'm testing wrong this > >> application? Should I first create a VMware image about generated code > >> and run it and test patched application there? Or can I test it just > >> like now running r1alpha2 ? > > > > The problem is when you create it in the build system like that, it > > will link against the libs created by the build system, which may > > include newer functions (as is the case here) that aren't present in > > the system libs on your running system. You could work around this > > using the LIBRARY_PATH environment var to tell it where to find the > > libs (in this case they'll be somewhere in generated/objects depending > > on what lib you need). Alternatively you can keep a second partition > > around that you install the updated OS from the development dir to and > > test by booting into that. > > > > Regards, > > > > Rene > > > Thanks, > > it was just thinking about that (with the updated OS), but this > LIBRARY_PATH should be an easier way, I think. Note that when the libbe <-> app_server interface changes (like was recently the case), then this method will not work. Usually it works just fine, though, just something to keep in mind. Best regards, -Stephan