From: Ken Moffat <zarniwhoop@ntlworld.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: QEMU Developers <qemu-devel@nongnu.org>,
Anthony Liguori <aliguori@amazon.com>,
Patch Tracking <patches@linaro.org>
Subject: Re: [Qemu-devel] [PATCH for-1.7] configure: Explicitly set ARFLAGS so we can build with GNU Make 4.0
Date: Tue, 22 Oct 2013 18:35:47 +0100 [thread overview]
Message-ID: <20131022173547.GB14652@milliways> (raw)
In-Reply-To: <CAFEAcA_wwy1WbtwKV1g8kxu+87rctP8aPeu-EjRCmihF9iJOQQ@mail.gmail.com>
On Tue, Oct 22, 2013 at 09:24:46AM +0100, Peter Maydell wrote:
> On 21 October 2013 21:03, Peter Maydell <peter.maydell@linaro.org> wrote:
> > Ken: I think this should work (and it doesn't break building with
> > old makes), but I don't have a make 4.0 to hand; if you could
> > test it I'd appreciate it.
>
> Forwarding a message from Ken (whose mail client is apparently
> not very good :-):
>
No, it was operator error - I somehow fell into editing the
original mail (didn't even know that was an option for received
mails) and trashed the header. Anyway.
> Ken wrote:
> # I applied it to 1.6.1 - some fuzz and large offsets, but it
> # completed the default build (i.e. just ./configure so all targets)
> # and also a DESTDIR install.
>
> Ken -- any chance you could test git master? I think it would
> be more interesting to make sure that 1.7 works with Make 4.0:
> I don't know if anybody will care enough to backport this patch
> to 1.6.x.
>
> thanks
> -- PMM
Not sure how to. I cloned git://git.qemu.org/qemu.git which was at
commit fc8ead74674b7129e8f31c2595c76658e5622197
Merge: 3551643 7174e54
Author: Anthony Liguori <aliguori@amazon.com>
Date: Fri Oct 18 10:03:24 2013 -0700
Merge remote-tracking branch 'qemu-kvm/uq/master' into staging
Copied the non-dotfiles (cp -av *), applied the patch, got a
message from configure:
ERROR: DTC not present. Your options:
(1) Preferred: Install the DTC devel package
(2) Fetch the DTC submodule, using:
git submodule update --init dtc
So I went back to git, did the submodule update and copied afresh,
applied the patch, and still got the same error.
ĸen
--
das eine Mal als Tragödie, dieses Mal als Farce
next prev parent reply other threads:[~2013-10-22 17:35 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-21 20:03 [Qemu-devel] [PATCH for-1.7] configure: Explicitly set ARFLAGS so we can build with GNU Make 4.0 Peter Maydell
2013-10-22 8:24 ` Peter Maydell
2013-10-22 17:35 ` Ken Moffat [this message]
2013-10-22 18:09 ` Ken Moffat
2013-10-22 18:52 ` Ken Moffat
2013-10-22 18:10 ` Peter Maydell
2013-10-22 18:19 ` Ken Moffat
2013-10-23 7:54 ` Paolo Bonzini
2013-10-22 8:40 ` [Qemu-devel] [PATCH for-1.7] configure: Explicitly set ARFLAGS sowe can build with GNU Make 4.00 Alex Bennée
2013-11-05 18:04 ` [Qemu-devel] [PATCH for-1.7] configure: Explicitly set ARFLAGS so we can build with GNU Make 4.0 Peter Maydell
2013-11-05 18:45 ` Andreas Färber
-- strict thread matches above, loose matches on Subject: below --
2013-11-05 19:09 Peter Maydell
2013-11-05 19:31 ` Andreas Färber
2013-11-05 19:36 ` Peter Maydell
2013-12-04 0:33 ` Michael Roth
2013-12-04 0:38 ` Peter Maydell
2013-12-04 1:43 ` Michael Roth
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=20131022173547.GB14652@milliways \
--to=zarniwhoop@ntlworld.com \
--cc=aliguori@amazon.com \
--cc=patches@linaro.org \
--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 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).