Just as a FYI, I finally found some confirmation on behavior on Linux of the test suite and LLD_LIBRARY_PATH.
To quote one source: "> Why not just use setenv()/putenv() to alter LD_LIBRARY_PATH within > your program before calling dlopen? I have not tested this, but suspect that this would be entirely pointless: both Linux and Solaris runtime loaders evaluate LD_* environment variables once (very early in process startup). After that, you can modify LD_LIBRARY_PATH all you want, and will not change anything." So that is exactly what I had suspected. The runtime loaders evaluate LD_LIBRARY_PATH very early when the interpreter is starting up. Then, when I augment the path after the ooTest framework starts executing, it is too late and has no effect. -- Mark Miesfeld ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
