Mailinglist Archive: opensuse-buildservice (216 mails)

< Previous Next >
Re: [opensuse-buildservice] fedora's mock and opensuse's build
  • From: Stephen Shaw <sshaw@xxxxxxxxxxxxx>
  • Date: Thu, 18 Mar 2010 08:27:24 -0600
  • Message-id: <bae3a6311003180727i4bfd7ee9p8d55ad41467fd649@xxxxxxxxxxxxxx>
On Wed, Mar 17, 2010 at 13:51, Robert Xu <robxu9@xxxxxxxxx> wrote:
On Wed, Mar 17, 2010 at 09:16, Michal Vyskocil <mvyskocil@xxxxxxx> wrote:
On Monday 15 March 2010 07:41:26 pm Robert Xu wrote:
On Thu, Mar 11, 2010 at 12:50, Marcus Rueckert <darix@xxxxxxxxx> wrote:
On 2010-03-11 11:34:06 -0500, Robert Xu wrote:
What is the difference between fedora's mock and opensuse's build? I
know that they both build RPMs, and they're written in different
But how come I can build my bzip2 spec file on mock and not build?
Does build do something different that might have caused this?

if you could tell us the problem you see, we might tell you why.


Sorry for the late reply.

For example, I can build a Fedora 12 gcc SRPM with mock for Fedora 12
i686, but I can't do the same with build. And also, it seems that the
obs cannot resolve dependencies that have file paths, like it'll say
something's broken if the dependency is /bin/someprog.

And for which distribution you build the gcc? If for openSUSE it's not a big
surprise it does not work. Can you cut&paste the command and an error output?


checking for correct version of CLooG... yes
configure: error: GNAT is required to build ada
error: Bad exit status from /var/tmp/rpm-tmp.MOfqJN (%build)


expansion error:
nothing provides glibc(x86-32), nothing provides glibc-devel(x86-32)

Michal Vyskocil

Cya Later,
Robert Xu
Ever tried Linux? :)

Something that I've noticed is that fedora seems to pull in gcc-c++
automatically whether its in the BuildRequires: or not. When I've
taken a fedora spec and brought it over to openSUSE I've usually had
to add gcc-c++

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

< Previous Next >
Follow Ups