qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Paul Bolle <pebolle@tiscali.nl>
To: Juan Quintela <quintela@trasno.org>
Cc: qemu-devel@nongnu.org
Subject: [Qemu-devel] Re: [PATCH] Fix *-user build error
Date: Tue, 13 Oct 2009 17:58:38 +0200	[thread overview]
Message-ID: <1255449518.1679.17.camel@localhost.localdomain> (raw)
In-Reply-To: <m3aazv1jox.fsf@neno.mitica>

On Tue, 2009-10-13 at 15:56 +0200, Juan Quintela wrote:
> Paul Bolle <pebolle@tiscali.nl> wrote:
> > On Tue, 2009-10-13 at 13:01 +0200, Juan Quintela wrote:
> >> Paul Bolle <pebolle@tiscali.nl> wrote:
> > Why doesn't "make clean" do what one expects it to do? Can't it be made
> > to behave properly?
> 
> Not trivial.
> foo-softmmu/config.h got renamed foo-softmmu/config-target.h
> now a new config.h got created at toplevel directory, that includes
> config-target.h (and more things, that is the whore reason why it was
> created).
> 
> Adding removal of foo-softmmu/config.h to the Makefile is an option, but
> this is a "once" affair, i.e. it is only needed if you have ever
> compiled in that directory.  Both options are bad:
> - add a removal of foo-softmmu/config.h that is not generated at all
> - require users to removal config.h once
> 
> 2nd one was adopted, both have disadvantages, just different ones.
> The other option was to rename config.h to something different, but that
> was a BIIIIIIIG patch for no gain either :(

I see. All that basically happened was that this rename etc. took place
in a repository in which I had previously built qemu and I should not
run into this issue anymore. Thanks.


Paul

      parent reply	other threads:[~2009-10-13 15:58 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-13  9:32 [Qemu-devel] [PATCH] Fix *-user build error Paul Bolle
     [not found] ` <m3tyy336d2.fsf@neno.mitica>
2009-10-13 11:22   ` [Qemu-devel] " Paul Bolle
     [not found]     ` <m3aazv1jox.fsf@neno.mitica>
2009-10-13 15:58       ` Paul Bolle [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=1255449518.1679.17.camel@localhost.localdomain \
    --to=pebolle@tiscali.nl \
    --cc=qemu-devel@nongnu.org \
    --cc=quintela@trasno.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).