xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: "Duncan X. Simpson" <virtualdxs@gmail.com>
To: Anthony PERARD <anthony.perard@citrix.com>
Cc: "xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org>
Subject: Re: Can't ./configure latest git
Date: Tue, 04 Apr 2017 17:32:01 +0000	[thread overview]
Message-ID: <CAB8Qo2SzpW0azB-C2esx1bKjyAf2SCWUpkV8sMmM3T2=98Om-A@mail.gmail.com> (raw)
In-Reply-To: <20170404153032.GD1710@perard.uk.xensource.com>


[-- Attachment #1.1: Type: text/plain, Size: 711 bytes --]

I just realized I misread the error message. I fixed the environment and
got it working.

On Tue, Apr 4, 2017 at 8:30 AM Anthony PERARD <anthony.perard@citrix.com>
wrote:

On Tue, Apr 04, 2017 at 03:09:48PM +0000, Duncan X. Simpson wrote:
> Ah, that makes more sense. Another problem I had when trying to compile
was
> I got a permission denied error on xen-setup, which I fixed by making as
> root (in a chroot of course). Was there a better way to do that?

This sound like an weird issue in your environnement. And I don't see
how been root would affect permission of xen-setup. Is this
tools/qemu-xen-traditional-dir/xen-setup ?

What is the error message?

--
Anthony PERARD

-- 

Duncan X. Simpson, K7DXS

[-- Attachment #1.2: Type: text/html, Size: 1497 bytes --]

[-- Attachment #2: Type: text/plain, Size: 127 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel

      reply	other threads:[~2017-04-04 17:32 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-04  2:18 Can't ./configure latest git Duncan X. Simpson
2017-04-04  2:25 ` Duncan X. Simpson
2017-04-04  2:49   ` Duncan X. Simpson
2017-04-04 15:06   ` Anthony PERARD
2017-04-04 15:09     ` Duncan X. Simpson
2017-04-04 15:30       ` Anthony PERARD
2017-04-04 17:32         ` Duncan X. Simpson [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='CAB8Qo2SzpW0azB-C2esx1bKjyAf2SCWUpkV8sMmM3T2=98Om-A@mail.gmail.com' \
    --to=virtualdxs@gmail.com \
    --cc=anthony.perard@citrix.com \
    --cc=xen-devel@lists.xenproject.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 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).