From Bugzilla Helper: User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4) Gecko/20030722 Galeon/1.3.8 Description of problem: During the configure process for floppy-0.12, there is an error reported due to a highly bogus path. checking for gtk-config... /asfd/jkl/bin/gtk-config checking for GTK - version >= 1.2.0... ./configure: line 1: /asfd/jkl/bin/gtk-config: No such file or directory ./configure: line 1: /asfd/jkl/bin/gtk-config: No such file or directory ./configure: line 1: /asfd/jkl/bin/gtk-config: No such file or directory ./configure: line 1: /asfd/jkl/bin/gtk-config: No such file or directory ./configure: line 1: /asfd/jkl/bin/gtk-config: No such file or directory no *** Could not run GTK test program, checking why... *** The test program failed to compile or link. See the file config.log for the *** exact error that occured. This usually means GTK was incorrectly installed *** or that you have moved GTK since it was installed. In the latter case, you *** may want to edit the gtk-config script: /asfd/jkl/bin/gtk-config No modifications have been made, and I obviously don't have a BS path like /asdf/jkl. Was this done on purpose? If so, could this be patched out? Version-Release number of selected component (if applicable): util-linux-2.11y-29 How reproducible: Always Steps to Reproduce: 1. see description 2. 3. Actual Results: You see the error in the configure process above. Expected Results: Should be corrected so that GTK support will be built *or* that part of the configure process should be patched out so that something that unclean would never appear. Additional info:
This intentional behaviour is the way I have chosen to disable GTK support. There's no apparent benefit to stripping GTK detection from configure altogether, and doing so would be a lot more complicated and harder to maintain, so I see no reason to change.