Bug 489942 - Allow specification of path to configure script
Allow specification of path to configure script
Product: Fedora
Classification: Fedora
Component: redhat-rpm-config (Show other bugs)
All Linux
low Severity medium
: ---
: ---
Assigned To: Jon Masters
Fedora Extras Quality Assurance
Depends On:
Blocks: 607705 849168
  Show dependency treegraph
Reported: 2009-03-12 12:19 EDT by Orion Poplawski
Modified: 2012-08-17 10:42 EDT (History)
5 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
: 607705 849168 (view as bug list)
Last Closed: 2009-11-23 18:17:54 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Orion Poplawski 2009-03-12 12:19:22 EDT
Description of problem:

This would allow out of tree builds:

%configure \
  %{_configure} ...

/var/lib/rpm/macros already defines _configure to ./configure.

Would then allow:

%define _configure ../configure
cd build
%configure --enable-other-stuff

in spec files

Version-Release number of selected component (if applicable):
Comment 1 Adam Williamson 2009-03-12 13:32:14 EDT
This bug has been triaged. And I endorse this product and/or service!

Fedora Bugzappers volunteer triage team
Comment 2 Richard W.M. Jones 2009-03-12 13:37:19 EDT
(As mentioned on the mailing list)

We recently changed the %{_mingw32_configure} macro so that it
automatically looks for ./configure and ../configure in that order.

It now looks like this:

%_mingw32_configure %{_mingw32_env} ; \
  __mingw32_topdir=.; if ! test -x configure; then __mingw32_topdir=..; fi; \\\
  $__mingw32_topdir/configure --cache-file=%{_mingw32_cache} \\\

Comment 3 Adam Williamson 2009-03-12 13:52:48 EDT
An open-ended definition is better, there are cases where it's stuck in a subdirectory or something. Coders do the funniest things.

Fedora Bugzappers volunteer triage team
Comment 4 Bug Zapper 2009-11-18 06:20:18 EST
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: 
Comment 5 Orion Poplawski 2009-11-18 10:32:55 EST
Any more thoughts?  Seems simple...
Comment 6 Panu Matilainen 2009-11-19 05:16:03 EST
One possibility would be removing %configure override from redhat-rpm-config...
Comment 7 Orion Poplawski 2009-11-19 10:38:54 EST
Here is the current differences:

-  FFLAGS="${FFLAGS:-%optflags}" ; export FFLAGS ; \
-  %{_configure} --host=%{_host} --build=%{_build} \\\
+  FFLAGS="${FFLAGS:-%optflags -I%_fmoddir}" ; export FFLAGS ; \
+  ./configure --build=%{_build} --host=%{_host} 

So we are also overriding FFLAGS as well.  If no one object, I'm going to add %{_configure} to redhat-rpm-config's definition.
Comment 8 Orion Poplawski 2009-11-23 18:17:54 EST
Fixed in 9.0.3-19.fc13

Note You need to log in before you can comment on or make changes to this bug.