After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 588291 - Error on 'make clean' in Debian Gnu/Linux
Error on 'make clean' in Debian Gnu/Linux
Status: RESOLVED FIXED
Product: doxygen
Classification: Other
Component: build
1.5.8-SVN
Other Linux
: Normal normal
: ---
Assigned To: Dimitri van Heesch
Dimitri van Heesch
Depends on:
Blocks:
 
 
Reported: 2009-07-11 00:38 UTC by Joenio Costa
Modified: 2009-08-20 10:12 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Joenio Costa 2009-07-11 00:38:44 UTC 
'make clean' try to use qmake in a invalid PATH:

/bin/qmake doxywizard.pro -o Makefile.doxywizard
make[1]: /bin/qmake: Command not found
make[1]: ** [Makefile.doxywizard] Error 127

My environment:

Linux 2.6.29-1-686
QMake version 2.01a
GNU Make 3.81
gcc version 4.3.3 (Debian 4.3.3-11)

Proposal to fix:

diff --git a/addon/doxywizard/Makefile.in b/addon/doxywizard/Makefile.in
index fa459c2..75a3a6d 100644
--- a/addon/doxywizard/Makefile.in
+++ b/addon/doxywizard/Makefile.in
@@ -10,16 +10,16 @@
 # See the GNU General Public License for more details.
 # 
 
-QMAKE = qmake
+QMAKE=qmake
 
 all: Makefile.doxywizard  
 	$(MAKE) -f Makefile.doxywizard 
 
 Makefile.doxywizard: doxywizard.pro
-	$(QTDIR)/bin/qmake doxywizard.pro -o Makefile.doxywizard
+	$(QMAKE) doxywizard.pro -o Makefile.doxywizard
 
 qmake: 
-	$(QTDIR)/bin/qmake doxywizard.pro -o Makefile.doxywizard
+	$(QMAKE) doxywizard.pro -o Makefile.doxywizard
 
 clean: Makefile.doxywizard 
 	$(MAKE) -f Makefile.doxywizard clean
Comment 1 Dimitri van Heesch 2009-07-13 20:10:35 UTC 
Thanks, I'll include the patch in the next subversion update.
Comment 2 Dimitri van Heesch 2009-08-20 10:12:48 UTC 
This bug was previously marked ASSIGNED, which means it should be fixed in
doxygen version 1.6.0. Please verify if this is indeed the case and reopen the
bug if you think it is not fixed (include any additional information that you
think can be relevant).