public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
To: Baruch Even <baruch-6P1Dz+XQpLLYtjvyW6yDsg@public.gmane.org>
Cc: KVM <kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>
Subject: Re: Versioning of KVM
Date: Wed, 15 Nov 2006 10:00:29 +0200	[thread overview]
Message-ID: <455AC91D.4050704@qumranet.com> (raw)
In-Reply-To: <20061115075647.GP28027-xGn4Jn0woyz+OtfAA3OxFg@public.gmane.org>

Baruch Even wrote:

 

>> My current tree has fixes for most of the problems.  I'll look at the clean targets (why are they necessary for 
>> packaging?)
>>     
>
> Some of the packages are being built by other computers, I'm building on
> my machine only the i386 version and the amd64 is built by an
> auto-builder. The clean target is needed since otherwise there are the
> .d files which have absolute paths for my machine and my build
> environment, this will kill the auto builder. In my case I build for
> Debian testing on my machine and then use a chroot to do a clean build
> for Debian unstable, the .d files killed the chroot build as well.
>
> The Debian build process does a clean before it starts the build to make
> sure we do a pristine build every time to avoid such problems. It
> doesn't always work when upstream clean target doesn't really clean.
> Normally there is a clean target and distclean to really clean the
> package back to distribution state.
>
>   

I don't understand.  If you start from an empty directory and unpack the 
archive there, you shouldn't have any problems.  I don't see how .d 
files can move from your machine to the autobuilder unless you added 
them to the archive.

-- 
error compiling committee.c: too many arguments to function


-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV

  parent reply	other threads:[~2006-11-15  8:00 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-15  7:12 Versioning of KVM Baruch Even
     [not found] ` <20061115071251.GN28027-xGn4Jn0woyz+OtfAA3OxFg@public.gmane.org>
2006-11-15  7:50   ` Avi Kivity
     [not found]     ` <455AC6D7.4060906-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2006-11-15  7:56       ` Baruch Even
     [not found]         ` <20061115075647.GP28027-xGn4Jn0woyz+OtfAA3OxFg@public.gmane.org>
2006-11-15  8:00           ` Avi Kivity [this message]
     [not found]             ` <455AC91D.4050704-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2006-11-15  8:19               ` Baruch Even

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=455AC91D.4050704@qumranet.com \
    --to=avi-atkuwr5tajbwk0htik3j/w@public.gmane.org \
    --cc=baruch-6P1Dz+XQpLLYtjvyW6yDsg@public.gmane.org \
    --cc=kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.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