I've been a linux sys admin for years and have managed to avoid having to build my own rpms. That all changes today. I'm trying to teach myself rpm building through google, but the documentation is falling short. Extremely short. How is it that documentation for such a fundamental part of the packaging system (being able to build packages) of one of the more popular distros (Redhat) be so difficult to find? Am I not looking in the right places?
Anyway, I've been able to discern what is happening to my spec file when I type rpmbuild -ba perl.spec. A shell script gets built in a tmp directory. Right now that shell script is getting created and then executed and is failing at the ./configure command. And for good reason... Perl's configure command is ./Configure (with a capital C).
Where the hell is the ./configure options being determined? I thought it was apart of the %configure macro so I commented that out. That didn't work. Then I thought it was a part of the %build macro. That didn't work either. What the hell?
The following code block contains the configure options that are somehow getting magically added to my that tmp shell script. I mean, geez, those are a lot of options to assume.
Code:
./configure --host=x86_64-unknown-linux-gnu --build=x86_64-unknown-linux-gnu \
--program-prefix= \
--prefix=/usr \
--exec-prefix=/usr \
--bindir=/usr/bin \
--sbindir=/usr/sbin \
--sysconfdir=/etc \
--datadir=/usr/share \
--includedir=/usr/include \
--libdir=/usr/lib64 \
--libexecdir=/usr/libexec \
--localstatedir=/var \
--sharedstatedir=/var/lib \
--mandir=/usr/share/man \
--infodir=/usr/share/info
I simply want it to be
Is that so much to ask?