Macro %configure contains "./configure" hardwired, which makes it unusable for non-in-tree builds. Some projects recommend out-of-tree builds (also called VPATH builds, or "srcdir != builddir"), and the in-tree builds are not debugged well in those projects. Reported and explained in fedora-devel, see http://thread.gmane.org/gmane.linux.redhat.fedora.devel/87358 Version-Release number of selected component (if applicable): rpm-4.5.90.git8461, and git as of 20008-08-11
Created attachment 313936 [details] proposed path
I think I'll rather have %_configure ./configure %configure \ .... %{_configure} --host=... So if you want something special, you just override %_configure.
I'd rather have something along the lines of ./configure %configureargs with %configure defaulting to ./configure %configureargs
Sure the %configure macro can be further broken up into separate args and flags to permit for that too. No big deal.
Is building out of the source tree really that interesting for packaging? It is usually done to avoid mixing builds for different archs in the same source tree, and packaging is by definition cleaning up everything before starting. Having said that if the purists like to build outside the source tree then it's quite easily done with mkdir mybuild cd mybuild ln -s ../configure . %configure ... Just a one-liner more that will ensure that the package also builds under older rpms including RHEL and friends. So for the sake of portability, please DONTFIX :)
(In reply to comment #5) > So for the sake of portability, please DONTFIX :) ROTFL ... the only portable solution is not to use %configure
(In reply to comment #6) > (In reply to comment #5) > > > So for the sake of portability, please DONTFIX :) > ROTFL ... the only portable solution is not to use %configure Well, I was referring to the Red Hat family of OS, Suse, Mandriva etc may have different definitions to start with. So let me rephrase: For the sake of not making it even less portable and even break compatibility between the RHEL subfamily and Fedora on the specfile level. But I'm sure you already knew that. ;)
This bug appears to have been reported against 'rawhide' during the Fedora 10 development cycle. Changing version to '10'. More information and reason for this action is here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
This message is a reminder that Fedora 10 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 10. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '10'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 10's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 10 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Fedora 10 changed to end-of-life (EOL) status on 2009-12-17. Fedora 10 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed.