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: gprolog - GNU Prolog is a free Prolog compiler https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=187266 ------- Additional Comments From gemi@xxxxxxxxxx 2006-05-10 16:28 EST ------- Output of rpmlint gprolog: W: gprolog devel-file-in-non-devel-package /usr/lib/gprolog-1.2.19/lib/libengine_fd.a W: gprolog devel-file-in-non-devel-package /usr/lib/gprolog-1.2.19/lib/libbips_pl.a W: gprolog devel-file-in-non-devel-package /usr/lib/gprolog-1.2.19/lib/libbips_fd.a W: gprolog devel-file-in-non-devel-package /usr/lib/gprolog-1.2.19/include/gprolog.h W: gprolog devel-file-in-non-devel-package /usr/lib/gprolog-1.2.19/lib/libengine_pl.a W: gprolog devel-file-in-non-devel-package /usr/lib/gprolog-1.2.19/lib/liblinedit.a W: gprolog devel-file-in-non-devel-package /usr/lib/gprolog-1.2.19/include/fd_to_c.h Would it make sense to split off the prolog to c compiler into an extra package. This would contains these object files and the compiler programs gplc, ma2asm, etc... rpmlint of gprolog src rpm: E: gprolog configure-without-libdir-spec Will adding --libdir=%{_libdir} to the configure command line break the build? Note, that on x86_64, %{_libdir} will be /usr/lib64. -- 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