Stas Bekman <[EMAIL PROTECTED]> writes: > Marcin Kasperski wrote: > >>In short: I tried different compilation methods with two possible > >>outcomes: > >>a) apache and modperl compile succesfully but I get coredump while the > >> application is starting (in all cases SEGVs, in some cases core's > >> confused the debugger, in other I managed to notice __at_fork in > >> backtrace) > >> b) everything seem to compile succesfully but I get dlopen: > >> /tools/apache/libexec/mod_perl.so: symbol > >> "PL_perl_destruct_level" unresolved > > >> while the application is starting > > Maybe it is worth noting, that I happened to get b) also when I > > > compiled perl with shared perl library (in contrary to suggestion > > found in modperl docs that building perl with shared library should > > help). > > 2 years ago, there was a similar struggle as you can see from this > thread: http://marc.theaimsgroup.com/?t=97442230600001&r=1&w=2 May > be those participants are still using True64 and can give you some > hints?
It seems to me, they had problem with the '-Wl,-rpath' issue which I found to be minor and easily patched (by the way: maybe someone would want to correct it in distribution?). And all they wanted was to get statically linked modperl. This is the thing I already have. Maybe I will post a question to tru64-managers... -- ( Marcin Kasperski | (...) the only completion criterion for the Analysis ) ( http://www.mk.w.pl | and Design phases is - the date. (Martin) ) (----------------------------------------------------------------------------) ( Nie gub zgłoszeń błędów: http://www.mk.w.pl/narzedzia/narzedzia_bugewid )
