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
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
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
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel