All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andre Przywara <andre.przywara@amd.com>
To: Ian Jackson <Ian.Jackson@eu.citrix.com>
Cc: xen-devel@lists.xensource.com
Subject: Re: [Patch] ioemu-remote: fix gcc4 build problem (?)
Date: Mon, 21 Jul 2008 13:35:27 +0200	[thread overview]
Message-ID: <4884747F.4080202@amd.com> (raw)
In-Reply-To: <18564.27621.920001.130068@mariner.uk.xensource.com>

Ian Jackson wrote:
> Andre Przywara writes ("[Patch] ioemu-remote: fix gcc4 build problem (?)"):
>> although I read that the gcc4 build problem should already be fixed, I 
>> cannot ack this for me: I just did
>> $ git clone http://xenbits.xensource.com/git-http/qemu-xen-unstable.git 
>> and "$ hg pull -u" in xen-staging and still configure stops with missing 
>> gcc3. In ioemu-remote "git log" says the latest patch was:
> 
> It's not clear to me in which directory you ran `git clone' in.
 > There are two sensible ways to use the new tree:
> 
> Automatically checked out tree:
>   ~:$ cd ~/work
>   ~/work:$ hg clone .../xen-unstable.hg
>   ~/work:$ cd xen-unstable.hg
>   ~/work/xen-unstable.hg:$ make -j4
>   [ build system runs hg clone ]
You mean git clone here, right?
> Then if you want to update ioemu-remote:
>   ~/work/xen-unstable.hg:$ cd tools/ioemu-remote
>   ~/work/xen-unstable.hg/tools/ioemu-remote:$ git pull
> or
>   ~/work/xen-unstable.hg/tools/ioemu-remote:$ git pull http://somewhere
I tried these both version. It says I am up-to-date.
Then I just cloned the git tree externally to make sure I am not fooled 
by some obsolete remote path, broken updates or wrong caching etc. When 
doing so I assume I get the latest and greatest. But the tree is 
essentially the same as in tools/ioemu-remote.
What were the latest changes you submitted? What changeset should fix this?

> Separate tree managed by you:
>   ~:$ cd ~/work
>   ~/work:$ hg clone .../xen-unstable.hg
>   ~/work:$ git clone .../qemu-xen-unstable.git
>   ~/work:$ cd xen-unstable.hg
>   ~/work/xen-unstable.hg:$ CONFIG_QEMU=$HOME/work/qemu-xen-unstable make -j4 
>   ...
> 
> Simply running
>   git clone http://xenbits.xensource.com/git-http/qemu-xen-unstable.git 
> isn't really going to help, no matter where you run it.  That will
> create a directory qemu-xen-unstable but you also need to make sure
> the build system will use that directory.
Sure. This was just a check to be sure.

Regards,
Andre.

BTW: What were the reasons to use git here? Isn't that making the whole 
building process more complicated (let alone forgotten updates due to a 
separate repository)?

-- 
Andre Przywara
AMD-Operating System Research Center (OSRC), Dresden, Germany
Tel: +49 351 277-84917
----to satisfy European Law for business letters:
AMD Saxony Limited Liability Company & Co. KG,
Wilschdorfer Landstr. 101, 01109 Dresden, Germany
Register Court Dresden: HRA 4896, General Partner authorized
to represent: AMD Saxony LLC (Wilmington, Delaware, US)
General Manager of AMD Saxony LLC: Dr. Hans-R. Deppe, Thomas McCoy

  parent reply	other threads:[~2008-07-21 11:35 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-20 13:29 [Patch] ioemu-remote: fix gcc4 build problem (?) Andre Przywara
2008-07-21 10:58 ` Ian Jackson
2008-07-21 10:59   ` Ian Jackson
2008-07-21 11:35   ` Andre Przywara [this message]
2008-07-21 13:10     ` Ian Jackson
2008-07-21 15:41       ` Andre Przywara
2008-07-22 15:30         ` Ian Jackson

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=4884747F.4080202@amd.com \
    --to=andre.przywara@amd.com \
    --cc=Ian.Jackson@eu.citrix.com \
    --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 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.