Mailinglist Archive: opensuse-buildservice (193 mails)

< Previous Next >
Re: [opensuse-buildservice] Strange Behavior in Project "CrossToolchain:sh4"
  • From: Martin Mohring <martin.mohring@xxxxxxxxx>
  • Date: Tue, 17 Apr 2007 23:13:53 +0200
  • Message-id: <46253891.6000604@xxxxxxxxx>
Robert Schiele wrote:
On Tue, Apr 17, 2007 at 03:59:21PM +0200, Martin Mohring wrote:
After some work, I now managed to bootstrap a
linux cross toolchain for sh4 from scratch
without binaries here:
http://build.opensuse.org/project/show?project=CrossToolchain%3Ash4

It uses binutiles, kernel headers, gcc and glibc
from openSUSE:Factory sources.

But now I have run into some strange behavior of
the buildservice:

- All packages build fine for openSUSE 10.2 and
 openSUSE Factory targets
- on SUSE 10.0 and SUSE 10.1, I get some strange
 expansion errors:

have choice for libgcc_s.so.1 needed by db:
libgcc cross-sh4-gcc, have choice for libgcc_s.so.1(GCC_3.0)
needed by db: libgcc cross-sh4-gcc, have choice for libstdc++.so.6
needed by db: libstdc++ cross-sh4-gcc, have choice for
libstdc++.so.6(CXXABI_1.3) needed by db: libstdc++ cross-sh4-gcc,
have choice for libstdc++.so.6(GLIBCXX_3.4) needed by db: libstdc++ cross-sh4-gcc,
have choice for libgcc_s.so.1 needed by gettext: libgcc cross-sh4-gcc, have choice for
libgcc_s.so.1(GCC_3.0) needed by gettext: libgcc cross-sh4-gcc, have choice for libstdc++.so.6
needed by gettext: libstdc++ cross-sh4-gcc, have choice for libstdc++.so.6(CXXABI_1.3)
needed by gettext: libstdc++ cross-sh4-gcc, have choice for libstdc++.so.6(GLIBCXX_3.4)
needed by gettext: libstdc++ cross-sh4-gcc

Can anybody explain what this means in my context? What can I do to fix this (can I?)?

This means that your packages contain a C++ runtime library which was either
built for the host platform instead of the target platform or RPM has added
provides for libraries of the target platform.  In the first case you have to
make sure to build the library for the target platform and in the second case
you should prevent RPM from adding those provides (for example by disabling
automatic generation of provides).

I think, the second is the case. How can I tell RPM not to do this? It looks like this happens only
on SUSE 10.0 and SUSE 10.1, and only on i586 buildhost here. Strange.

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?

Martin

---------------------------------------------------------------------
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse-buildservice+help@xxxxxxxxxxxx

< Previous Next >