"Stephen Williams" <1mc9i5i02@sneakemail.com> writes:
Andreas Jaeger aj-at-suse.de |suse-amd64| wrote:
"Stephen Williams" <1mc9i5i02@sneakemail.com> writes:
This is actually a distribution problem and not an AMD64 problem, but it is an AMD64 distribution, ...
Anyhow, my source rpms for Icarus Verilog cause lots of warnings when I use "rpm --rebuild iverilog-0.7.20030815-0.src.rpm" to rebuild the package. Warnings like: That package seems not to use BUILD_ROOT. Without BUILD_ROOT set, a normal user might not be able to build the package. So, I would call it a bug in the source RPM.
First of all, the verilog.spec most certainly *does* use the RPM_BUILD_ROOT variable. For example:
%install %ifarch x86_64 make prefix=$RPM_BUILD_ROOT/usr libdir=$RPM_BUILD_ROOT/usr/lib64 install %else make prefix=$RPM_BUILD_ROOT/usr install %endif
Does it also set it? E.g. is there something like this: BuildRoot: %{_tmppath}/%{name}-%{version}-build
(BTW is this how the lib64 directory is intended to be used on x86_64 systems?)
No, use: libdir=%{_libdir} This will be either /usr/lib or /usr/lib64
Second, those commands that are generating the warnings are things like the brp-compress and the Check programs, which are not paying attention to the RPM_BUILD_ROOT variable.
Those are paying attention. But I guess that variable is not set.
Third, this exact same package rebuilds with rpm --rebuild on on my RedHat 7.2/alpha system just fine.
Interesting... Andreas -- Andreas Jaeger, aj@suse.de, http://www.suse.de/~aj SuSE Linux AG, Deutschherrnstr. 15-19, 90429 Nürnberg, Germany GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126