On Tue, Apr 17, 2007 at 11:13:53PM +0200, Martin Mohring wrote:
I think, the second is the case. How can I tell RPM not to do this? It
Just add autoprov: no to your spec file.
looks like this happens only on SUSE 10.0 and SUSE 10.1, and only on i586 buildhost here. Strange.
This is not really strange since x86_64 libraries have a different naming convention for their libraries to prevent conflicts with 32 bit libraries. Although I wonder why it does not conflict with the 32 bit compat package there.
And I have now deactivated the build target for the potential cause of the error. I get now the same error for some packages not related to glibc at all. Is there some "caching" effect?
I don't really understand what you mean here. This problem is completely unrelated to glibc, it listed libstdc++, didn't it? Robert -- Robert Schiele Dipl.-Wirtsch.informatiker mailto:rschiele@gmail.com "Quidquid latine dictum sit, altum sonatur."