Mailinglist Archive: opensuse-buildservice (193 mails)

< Previous Next >
Re: [opensuse-buildservice] Valgrind-devel package on RHEL
  • From: Greg Banks <gnb@xxxxxxxx>
  • Date: Mon, 13 Jan 2014 22:57:38 -0800
  • Message-id: <CAFLzV7yOFni6K7sbD42njDF4XiPwkzK_yLSUfevw=SHx9Xfg4g@mail.gmail.com>
G'day Martin,

On 13 January 2014 13:58, Martin Koegler <martin.koegler@xxxxxxxxx> wrote:
On Mon, Jan 13, 2014 at 01:10:56PM -0800, Greg Banks wrote:
I have a project
https://build.opensuse.org/project/show/home:gnb:novaprova which I'm
trying to make available on as many distros as possible. To build it
needs to include the valgrind.h header file from Valgrind (and before
you ask, no this is not optional). When building for RHEL, OBS can't
find the valgrind-devel RPM which contains this header. I think this
is because RH shipped that RPM on the "optional" media, and that OBS
doesn't know how to find the RPMs from that media.

So what's the best way to convince OBS to actually find those RPMs so
I can build?

Import the source rpm in your project, limit the built the necessary
distribution, disable publishing and
enable use-for-build flag.

That seemed pretty sensible, so I tried it.

Unfortunately it seems that the valgrind source RPM from RHEL6 won't
build in OBS's RHEL6 VM. The problem seems to be that the VM is
running a much newer kernel than RHEL is supposed to be running. From
the build log

[ 46s] checking for a supported OS... ok (linux-gnu)
[ 46s] checking for the kernel version... unsupported (3.11.6-4-default) <---
[ 46s] configure: error: Valgrind works on kernels 2.4, 2.6
[ 46s] error: Bad exit status from /var/tmp/rpm-tmp.Qzy4DK (%build)

the VM is running 3.11.6, but according to

https://access.redhat.com/site/articles/3078

the most recent supported kernel for RHEL6 is 2.6.32.

So is there a way to get the real binary valgrind-devel RPM from the
RHEL media installed into the VM?


--
Greg.
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@xxxxxxxxxxxx
To contact the owner, e-mail: opensuse-buildservice+owner@xxxxxxxxxxxx

< Previous Next >
Follow Ups