Bug 194360 - rpmbuild deliberately runs unasked %configure macro
Summary: rpmbuild deliberately runs unasked %configure macro
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: rpm
Version: 5
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Paul Nasrat
QA Contact: Mike McLean
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2006-06-07 14:44 UTC by Andrea Santilli
Modified: 2007-11-30 22:11 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2006-06-08 12:30:47 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
output of rpmbuild -ba specfile (49.93 KB, text/plain)
2006-06-07 14:44 UTC, Andrea Santilli
no flags Details

Description Andrea Santilli 2006-06-07 14:44:46 UTC
Description of problem:
I was writing a spec file and i put ./configure in it instead of %configure
because of buffer overflow issues in the application.
Then i noticed rpmbuild runs first %configure , then ./configure which should be
impossible because i never put the %configure line in the .spec file.

So I tried recompiling other rpms and it runs %configure twice!

I'm adding the output of rpmbuild (notice that i run aclocal and autoconf on
purpose). This is the %build section:

%build
aclocal --acdir=`sdl-config --prefix`/share/aclocal
autoconf
# I had some buffer overflow in zsnes having it configured by the %configure script
./configure
make %{?_smp_mflags}
### end of %build section ###

Version-Release number of selected component (if applicable):
4.4.2-15.2

How reproducible:
always

Steps to Reproduce:
1. add ./configure in the spec file instead of %configure
2. rpmbuild will runs %configure then ./configure

Comment 1 Andrea Santilli 2006-06-07 14:44:46 UTC
Created attachment 130682 [details]
output of rpmbuild -ba specfile

Comment 2 Jeff Johnson 2006-06-08 12:30:47 UTC
Macros are expanded everywhere, including comments.

Add a 2nd '%' escape to prevent expansion as in ' ... %%configure ...'


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