Please stabilize =app-misc/recoll-1.17.3
* QA Notice: Files built without respecting LDFLAGS have been detected * Please include the following list of files in your report: * /usr/bin/recoll Sorry, we have also: CXXFLAGS="${CXXFLAGS} ${LDFLAGS}" Why you include LDFLAGS when he just compile without link?
Show me your emerge -pv recoll please. The same gcc flags are used for the compilation and the linking phase. gcc is smart enough to understand which flags to use where.
Please look at issue python3 https://bugs.gentoo.org/show_bug.cgi?id=425492 I dont know how to change status of my bug to show up in bug searches ...
(In reply to comment #3) > Please look at issue python3 > https://bugs.gentoo.org/show_bug.cgi?id=425492 > > I dont know how to change status of my bug to show up in bug searches ... Bugzilla has some problems since a couple of days ago. Thanks for pointing out this bug
(In reply to comment #2) > Show me your emerge -pv recoll please. [ebuild N ~] app-misc/recoll-1.17.3 USE="inotify qt4 session -audio -camelcase -chm -djvu -dvi -exif -fam -ics -info -lyx -msdoc -msppt -msxls -pdf -postscript -rtf -spell -tex -wordperfect -xattr -xml"
(In reply to comment #2) > gcc is smart enough to understand which flags to use where. Yeah, but it uses LDFLAGS in a not useful moment instead of when it should link: g++ -Wl,-O1 -o recoll .obj/advsearch_w.o .obj/confgui.o .obj/confguiindex.o .obj/crontool.o .obj/guiutils.o .obj/main.o .obj/preview_w.o .obj/rclhelp.o .obj/rclmain_w.o .obj/rclzg.o .obj/reslist.o .obj/restable.o .obj/rtitool.o .obj/searchclause_w.o .obj/spell_w.o .obj/ssearch_w.o .obj/uiprefs_w.o .obj/viewaction_w.o .obj/moc_advsearch_w.o .obj/moc_confgui.o .obj/moc_confguiindex.o .obj/moc_crontool.o .obj/moc_editdialog.o .obj/moc_firstidx.o .obj/moc_idxsched.o .obj/moc_listdialog.o .obj/moc_preview_w.o .obj/moc_rclhelp.o .obj/moc_restable.o .obj/moc_rtitool.o .obj/moc_searchclause_w.o .obj/moc_spell_w.o .obj/moc_ssearch_w.o .obj/moc_uiprefs_w.o .obj/moc_viewaction_w.o .obj/qrc_recoll.o -L/usr/lib64/qt4 ../lib/librcl.a -L/usr/lib64 -lxapian -lz -ldl -lX11 -lQtWebKit -lQtGui -L/usr/lib64/qt4 -L/usr/X11R6/lib -lQtCore -lgthread-2.0 -lrt -lglib-2.0 -lpthread And it calls g++ directly.
(In reply to comment #6) > (In reply to comment #2) > > gcc is smart enough to understand which flags to use where. > > Yeah, but it uses LDFLAGS in a not useful moment instead of when it should > link: > > g++ -Wl,-O1 -o recoll .obj/advsearch_w.o .obj/confgui.o .obj/confguiindex.o > .obj/crontool.o .obj/guiutils.o .obj/main.o .obj/preview_w.o .obj/rclhelp.o > .obj/rclmain_w.o .obj/rclzg.o .obj/reslist.o .obj/restable.o .obj/rtitool.o > .obj/searchclause_w.o .obj/spell_w.o .obj/ssearch_w.o .obj/uiprefs_w.o > .obj/viewaction_w.o .obj/moc_advsearch_w.o .obj/moc_confgui.o > .obj/moc_confguiindex.o .obj/moc_crontool.o .obj/moc_editdialog.o > .obj/moc_firstidx.o .obj/moc_idxsched.o .obj/moc_listdialog.o > .obj/moc_preview_w.o .obj/moc_rclhelp.o .obj/moc_restable.o > .obj/moc_rtitool.o .obj/moc_searchclause_w.o .obj/moc_spell_w.o > .obj/moc_ssearch_w.o .obj/moc_uiprefs_w.o .obj/moc_viewaction_w.o > .obj/qrc_recoll.o -L/usr/lib64/qt4 ../lib/librcl.a -L/usr/lib64 -lxapian > -lz -ldl -lX11 -lQtWebKit -lQtGui -L/usr/lib64/qt4 -L/usr/X11R6/lib -lQtCore > -lgthread-2.0 -lrt -lglib-2.0 -lpthread > > > And it calls g++ directly. The LDFLAGS is not an issue. For the g++ I need a separate bug as usual
(In reply to comment #7) > The LDFLAGS is not an issue. For the g++ I need a separate bug as usual Why you think this is not an issue?
reopen when it is ready
amd64 stable
x86 stable. Last arch, closing