All of lore.kernel.org
 help / color / mirror / Atom feed
From: Laszlo Ersek <lersek@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: Gerhard Wiesinger <lists@wiesinger.com>,
	"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] Compile error on FC17
Date: Sun, 10 Mar 2013 19:52:56 +0100	[thread overview]
Message-ID: <513CD688.1060400@redhat.com> (raw)
In-Reply-To: <CAFEAcA-J9eUVap=GJnAOiPAb=sw1AVWxiNXE2WjnHg_ANF3n_w@mail.gmail.com>

On 03/10/13 18:04, Peter Maydell wrote:
> On 10 March 2013 15:15, Gerhard Wiesinger <lists@wiesinger.com> wrote:
>> Tried make clean and make distclean already before I reported the issue.
>>
>> If I'm suppressing "warning as errors" I'm still getting errors:
>>
>> hw/usb/hcd-xhci.c: In function ‘xhci_set_ep_dequeue’:
>> hw/usb/hcd-xhci.c:1471:5: error: too many arguments to function
>> ‘trace_usb_xhci_ep_set_dequeue’
>> In file included from hw/usb/hcd-xhci.c:27:0:
>> ./trace.h:1052:58: note: declared here
> 
>> BTW: Isn't a new issue (around 2 month) but was very busy.
> 
> Oh, right. Tracing functions moved from trace.h to the files
> in the trace/ subdirectory. This means that if you didn't do
> a make clean or distclean before doing the git update then
> the new makefile knows nothing about the old trace.h file and
> so won't delete it, but the compiler may still pull it in anyhow.
> However this happened a long time back which is why I didn't
> mention it as a possibility (it was discussed on the list at
> the time as a number of people including me ran into it).
> If you remove all the files:
> trace.c trace.h trace.c-timestamp trace.h-timestamp
> this should resolve the problem.
> 
> This is an example of a longstanding problem we have, where
> the makefile's dependency rules aren't able to cope with
> changes to the project source file structure, and so clean,
> distclean and incremental build sometimes breaks across a
> git update. I think this is pretty intractable as a problem
> to solve; you can mitigate it by doing all your builds in
> a build directory rather than in the source tree itself,
> since then you can always just delete the whole build tree
> to get a definite from-scratch build.

There's also
$ git reset --hard
$ git clean -fdx
$ ./configure ...

Laszlo

  reply	other threads:[~2013-03-10 18:51 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-10 12:28 [Qemu-devel] Compile error on FC17 Gerhard Wiesinger
2013-03-10 13:20 ` Peter Maydell
2013-03-10 15:15   ` Gerhard Wiesinger
2013-03-10 17:04     ` Peter Maydell
2013-03-10 18:52       ` Laszlo Ersek [this message]
2013-03-10 19:36       ` Gerhard Wiesinger
2013-03-10 19:47         ` Peter Maydell

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=513CD688.1060400@redhat.com \
    --to=lersek@redhat.com \
    --cc=lists@wiesinger.com \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.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 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.