I noticed that with texmaker when I had prestripped files: $ cat foo.pro TEMPLATE = app LANGUAGE = C++ TARGET = foo SOURCES += main.cpp DEFINES += PREFIX=\\\"$${PREFIX}\\\" target.path = $${PREFIX}/bin INSTALLS = target $ qmake foo.pro $ grep strip Makefile -strip "$(INSTALL_ROOT)/bin/$(QMAKE_TARGET)" Imho eqmake4 should take care of this if that's the way qmake is meant to be. I dont remember seeing that with older qt versions though.
*** Bug 225203 has been marked as a duplicate of this bug. ***
*** Bug 251870 has been marked as a duplicate of this bug. ***
*** Bug 252043 has been marked as a duplicate of this bug. ***
Created attachment 177687 [details, diff] Patch for /usr/portage/eclass/qt4.eclass This should fix the problem by replacing strip commands with harmless echo commands. More information is available here: http://doc.trolltech.com/4.2/qmake-running.html#makefile-mode-options http://doc.trolltech.com/qtextended4.4/qbuild/qb-var-mkspec-strip-2.html
Created attachment 177856 [details, diff] qt4.eclass.diff Seems that running "echo" is not required and this is enough
(In reply to comment #5) > Created an attachment (id=177856) [edit] > qt4.eclass.diff > > Seems that running "echo" is not required and this is enough > Yeah! This is also much better than running sed on the generated Makefile, as I proposed in bug #244692. It's not good to see once again that qmake is so badly documented.
This bug can now close I fixed the qt4.eclass Thanks for reporting