From mboxrd@z Thu Jan  1 00:00:00 1970
From: Steven Haigh <netwiz@crc.id.au>
Subject: Packaging Xen 4.2.0
Date: Wed, 19 Sep 2012 00:26:27 +1000
Message-ID: <50588493.7080908@crc.id.au>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Content-Transfer-Encoding: 7bit
Return-path: <xen-devel-bounces@lists.xen.org>
List-Unsubscribe: <http://lists.xen.org/cgi-bin/mailman/options/xen-devel>,
	<mailto:xen-devel-request@lists.xen.org?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xen.org>
List-Help: <mailto:xen-devel-request@lists.xen.org?subject=help>
List-Subscribe: <http://lists.xen.org/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xen.org?subject=subscribe>
Sender: xen-devel-bounces@lists.xen.org
Errors-To: xen-devel-bounces@lists.xen.org
To: xen-devel@lists.xen.org
List-Id: xen-devel@lists.xenproject.org

Hi all,

I'm trying to update my RPMs of 4.1.3 to work with 4.2.0, but I'm having 
some interesting problems with the packaging side of things.

in 4.1.3, xenpaging was being built as /usr/sbin/xenpaging, however in 
4.2.0 it is being built as /usr/lib/xen/bin/xenpaging.

I'm currently using the following configure options in my .spec:
./configure --libdir=/%{_libdir} --prefix=/usr --bindir=/%{_bindir} 
--sbindir=/%{_sbindir}

This is expanding to:
./configure --libdir=/usr/lib64 --prefix=/usr --bindir=/usr/bin 
--sbindir=/usr/sbin

So, I'm wondering how xenpaging is getting that path info - however I do 
see a lot of what seem to be hard coded references to 
/usr/lib/xen/bin/xenpaging with a quick grep around the source.

A penny for peoples thoughts?

-- 
Steven Haigh

Email: netwiz@crc.id.au
Web: http://www.crc.id.au
Phone: (03) 9001 6090 - 0412 935 897
Fax: (03) 8338 0299