From: Steven Haigh <netwiz@crc.id.au>
To: xen-devel@lists.xen.org
Subject: Packaging Xen 4.2.0
Date: Wed, 19 Sep 2012 00:26:27 +1000 [thread overview]
Message-ID: <50588493.7080908@crc.id.au> (raw)
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
next reply other threads:[~2012-09-18 14:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-18 14:26 Steven Haigh [this message]
2012-09-18 14:33 ` Packaging Xen 4.2.0 Olaf Hering
2012-09-18 14:57 ` Steven Haigh
2012-09-18 15:05 ` Olaf Hering
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=50588493.7080908@crc.id.au \
--to=netwiz@crc.id.au \
--cc=xen-devel@lists.xen.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.