Trying to rebuild rawhide cyrus-imapd (2.2.10-11.2.fc4) src rpm on x86_64 FC3 box and I'm getting this:
=-=-=-= md:iadonisi:526) rpmbuild --rebuild /data/va/data/fedora-3+/SRPMS/SRPMS/cyrus-imapd-2.2.10-3.fc3.src.rpm Installing /data/va/data/fedora-3+/SRPMS/SRPMS/cyrus-imapd-2.2.10-3.fc3.src.rpm Executing(%prep): /bin/sh -e /home/iadonisi/rpmbuild/tmp/rpm-tmp.47173 + umask 022 + cd /home/iadonisi/rpmbuild/BUILD + cd /home/iadonisi/rpmbuild/BUILD + rm -rf cyrus-imapd-2.2.10 + /usr/bin/gzip -dc /home/iadonisi/rpmbuild/cyrus-imapd-2.2.10/cyrus-imapd-2.2.10.tar.gz + tar -xf - + STATUS=0 + '[' 0 -ne 0 ']' + cd cyrus-imapd-2.2.10 ++ /usr/bin/id -u + '[' 500 = 0 ']' ++ /usr/bin/id -u + '[' 500 = 0 ']' + /bin/chmod -Rf a+rX,u+w,g-w,o-w .
[snipage]
+ ./configure --host=x86_64-redhat-linux-gnu --build=x86_64-redhat-linux-gnu --target=x86_64-redhat-linux --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=/usr/com --mandir=/usr/share/man --infodir=/usr/share/info --enable-netscapehack --enable-listext --enable-murder --enable-nntp --without-snmp --with-perl=/usr/bin/perl --with-cyrus-prefix=/usr/lib64/cyrus-imapd --with-service-path=/usr/lib64/cyrus-imapd --with-auth=unix --with-bdb-incdir=/usr/include/db4 --with-extraident=Invoca-RPM-2.2.10-3.fc3 --with-syslogfacility=MAIL checking build system type... Invalid configuration `x86_64-redhat-linux-gnu': machine `x86_64-redhat' not recognized configure: error: /bin/sh ./config.sub x86_64-redhat-linux-gnu failed error: Bad exit status from /home/iadonisi/rpmbuild/tmp/rpm-tmp.47173 (%build)
RPM build errors: Bad exit status from /home/iadonisi/rpmbuild/tmp/rpm-tmp.47173 (%build)
-=-=-=-=
I get the same result with the FC3-updates version (2.2.10-3.fc3). I also have a chroot with Nahant (RHEL4 beta 2) and get the same results there with cyrus-imapd-2.2.10-1.RHEL4.1.src.rpm from the RHEL4 released sources. Methinks there is a rogue macro set somewhere on the Red Hat-internal build machine(s) that's not in redhat-rpm-config (which I do have installed, btw). Anyone know what macro I need set/change to get this build?
Bugzilla: https://bugzilla.redhat.com/beta/show_bug.cgi?id=149140
On Sat, 19 Feb 2005, Paul Iadonisi wrote:
Trying to rebuild rawhide cyrus-imapd (2.2.10-11.2.fc4) src rpm on x86_64 FC3 box and I'm getting this:
Methinks there is a rogue macro set somewhere on the Red Hat-internal build machine(s) that's not in redhat-rpm-config (which I do have installed, btw). Anyone know what macro I need set/change to get this build?
Bugzilla: https://bugzilla.redhat.com/beta/show_bug.cgi?id=149140
Hi, Paul
In your build chroot, is there any output from: rpm -qa | grep rpmdb (that is, is a package like: redhat-rpmdb installed?) -- As I recall, there is some Distribution tag information derived from a file in that package.
-- Russ Herrold
On Sat, 2005-02-19 at 01:02 -0500, R P Herrold wrote:
Hi, Paul
In your build chroot, is there any output from: rpm -qa | grep rpmdb
Yup: md:root:521)# rpm -q rpmdb-redhat rpmdb-redhat-3.95-0.20041027
Same goes for my FC3 x86_64 installation: md:iadonisi:496) rpm -q rpmdb-fedora rpmdb-fedora-3-0.20041103
(that is, is a package like: redhat-rpmdb installed?) -- As I recall, there is some Distribution tag information derived from a file in that package.
I thought that was only used for the --redhat-provides option to rpm and for the 'suggested resolutions' functionality of rpm. Are you sure you're not referring to redhat-rpm-config? Because I have that installed as well.
On Sat, 19 Feb 2005, Paul Iadonisi wrote:
I thought that was only used for the --redhat-provides option to rpm and for the 'suggested resolutions' functionality of rpm. Are you sure you're not referring to redhat-rpm-config? Because I have that installed as well.
You are right, of course, as to redhat-rpm-config; stale memories.
I'll dink on it a bit.
-- Russ
I would think it has to be a macro on our build machines, the spec file invokes %{configure}, and it successully builds on x86_64, I just checked. I'm guessing its a different definition of %{configure} between our build machines and yours. At the moment I can't tell you what that difference might be.
-- John Dennis jdennis@redhat.com
On Sat, 2005-02-19 at 02:12 -0500, John Dennis wrote:
I would think it has to be a macro on our build machines, the spec file invokes %{configure}, and it successully builds on x86_64, I just checked. I'm guessing its a different definition of %{configure} between our build machines and yours. At the moment I can't tell you what that difference might be.
Argh! I found the problem. I blame Mike Harris whose ~/.rpmrc and ~/.rpmmacros files I'm using ;-). My fault for having local config files that override the macros search path. I'll close the bug.
-
John Dennis -
Paul Iadonisi -
R P Herrold