From: Keir Fraser <keir.fraser@eu.citrix.com>
To: M A Young <m.a.young@durham.ac.uk>,
"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: Minor bug in 4.0.0-rc2
Date: Thu, 04 Feb 2010 09:01:29 +0000 [thread overview]
Message-ID: <C7903D69.8FB2%keir.fraser@eu.citrix.com> (raw)
In-Reply-To: <alpine.LFD.2.00.1002032144580.13414@vega4.dur.ac.uk>
Thanks. Actually a trailing slash was appended in quite a few places, so I
will fix them all at the same time.
-- Keir
On 03/02/2010 21:55, "M A Young" <m.a.young@durham.ac.uk> wrote:
> I have been trying to put 4.0.0-rc2 into an RPM, and I got the error
> "canonicalization unexpectedly shrank by one character" when it was
> creating files for the debuginfo package. This is because this bit of rpm
> doesn't like // in paths to file names, and the // comes from the makefile
> xen-4.0.0/tools/blktap2/drivers/Makefile which sets XEN_ROOT=../../../ and
> then uses it like $(XEN_ROOT)/tools/libaio/src . XEN_ROOT=../../../ be
> replaced by XEN_ROOT=../../.. to keep rpm happy please (eg. with the
> following patch)?
>
> Michael Young
>
> --- xen-4.0.0/tools/blktap2/drivers/Makefile.orig 2010-02-02
> 20:43:00.000000000 +0000
> +++ xen-4.0.0/tools/blktap2/drivers/Makefile 2010-02-03 20:55:14.000000000
> +0000
> @@ -1,4 +1,4 @@
> -XEN_ROOT=../../../
> +XEN_ROOT=../../..
> BLKTAP_ROOT= ..
> include $(XEN_ROOT)/tools/Rules.mk
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
prev parent reply other threads:[~2010-02-04 9:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-03 21:55 Minor bug in 4.0.0-rc2 M A Young
2010-02-03 22:06 ` Pasi Kärkkäinen
2010-02-03 22:29 ` M A Young
2010-02-04 1:10 ` M A Young
[not found] ` <alpine.LFD.2.00.1002162259110.9452@vega3.dur.ac.uk>
2010-02-20 13:22 ` 4.0.0-rc4 srpm Pasi Kärkkäinen
2010-02-03 22:13 ` Minor bug in 4.0.0-rc2 Daniel Stodden
2010-02-04 9:01 ` Keir Fraser [this message]
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=C7903D69.8FB2%keir.fraser@eu.citrix.com \
--to=keir.fraser@eu.citrix.com \
--cc=m.a.young@durham.ac.uk \
--cc=xen-devel@lists.xensource.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).