Please do not reply directly to this email. All additional comments should be made in the comments box of this bug report. Summary: Review Request: prelude-lml - Prelude log analyzer https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=209222 ------- Additional Comments From mtasaka@xxxxxxxxxxxxxxxxxxx 2007-01-01 22:07 EST ------- (In reply to comment #7) > concerning the debuging thing I got the following information from upstream: > > >This is the way automake+libtool handle building the program. More > >specifically, this is related to the handling of pre-opened modules.> >You will notice similar behavior with prelude-manager, but this is all > >generated libtool code. Then? actually .libs/prelude-lmlS.o is used in prelude-lml as -------------------------------------------------- gcc -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector --param=ssp-buffer-size=4 -m32 -march=i386 -mtune=g eneric -fasynchronous-unwind-tables -Wstrict-prototypes -Wmissing-prototypes -Wmissing-declarations -Wbad-function-cast -Wcast-qual -Wcast-align -Wnested-externs -Wunused -o prelude-lml -pthread .libs/prelude-lmlS.o prelude-lml.o udp-server.o regex.o log-entry.o log-source.o log-plugins.o lml-options.o file-server.o lml-alert.o -Wl,--export-dynamic -L/usr/lib -lprelude -lgnutls -lgcrypt -lgpg-error -lrt -ldl -lpcre ../libmissing/.libs/libmissing.a -------------------------------------------------- and debugging prelude-lml actually needs prelude-lmlS.c, so prelude-lmlS.c should not be removed. > because of the missing .so symlink libraries in the -devel I got this: > > >The prelude-lml.h header provide the necessary API for contributor to > >write LML plugins. The function (*lml_log_entry_get_message, used in your > >example) is a public function available from the LML >core. Plugin loaded by > >LML have access to LML public symbols. Well, then what library actually provides *lml_log_entry_get_message? -- Configure bugmail: https://bugzilla.redhat.com/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug, or are watching the QA contact. _______________________________________________ Fedora-package-review mailing list Fedora-package-review@xxxxxxxxxx http://www.redhat.com/mailman/listinfo/fedora-package-review