Mailinglist Archive: opensuse-buildservice (193 mails)

< Previous Next >
Re: [opensuse-buildservice] Valgrind-devel package on RHEL
  • From: Martin Koegler <martin.koegler@xxxxxxxxx>
  • Date: Tue, 14 Jan 2014 08:26:33 +0100
  • Message-id: <20140114072633.GA19471@mail.zuhause>
On Mon, Jan 13, 2014 at 10:57:38PM -0800, Greg Banks wrote:
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.

Looks like the build VMs are using a generic kernel.
Personally, I would patch configure to handle 3.X the same way as 2.6.

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

If you setup your own OBS instance, you can import, whatever you want.

Regards,
Martin
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@xxxxxxxxxxxx
To contact the owner, e-mail: opensuse-buildservice+owner@xxxxxxxxxxxx

< Previous Next >