Bug 32804 – %configure in spec file comment runs configure twice

Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.

Bug 32804 - %configure in spec file comment runs configure twice

Summary:	%configure in spec file comment runs configure twice

Status:	CLOSED RAWHIDE

Aliases:	None

Product:	Red Hat Raw Hide
Classification:	Retired
Component:	ntp (Show other bugs)
Sub Component:
Version:	1.0
Hardware:	i386 Linux

Priority	medium Severity medium
Target Milestone:	---
Target Release:	---
Assigned To:	Preston Brown
QA Contact:	Brian Brock
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2001-03-23 02:04 EST by kenneth_porter
Modified:	2007-04-18 12:32 EDT (History)
CC List:	0 users

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2001-03-25 18:30:19 EST
Type:	---
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Groups: None (edit)

Description kenneth_porter 2001-03-23 02:04:37 EST

RPM macros in spec files are expanded even when within a comment. In the spec file for ntp-4.0.99k-13, the line "#%configure" is expanded 
and the results are executed. This causes configure to run twice.

Comment 1 Brian Brock 2001-03-25 18:30:15 EST

I can verify that, and the package builds in spite of the bug in the spec file. 
However, #%configure is on a line by itself, and there are no other uses of the
%configure macro within that spec file:

# XXX work around for anal ntp configure
%define _target_platform        %{nil}
#%configure
CFLAGS="-g -DDEBUG" ./configure --prefix=/usr
%undefine       _target_platform

Comment 2 Preston Brown 2001-03-26 10:32:04 EST

fixed in 4.0.99k-14 and later.

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