From: Ken Moffat <zarniwhoop@ntlworld.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] Build failure with make-4.0
Date: Sat, 19 Oct 2013 10:53:43 +0100 [thread overview]
Message-ID: <20131019095343.GA24209@milliways> (raw)
In-Reply-To: <CAFEAcA80i3PLOgzgd9fbrycOGStNc+1ijWWmpRcMeEvH=pp66A@mail.gmail.com>
On Sat, Oct 19, 2013 at 10:05:10AM +0100, Peter Maydell wrote:
> On 19 October 2013 00:36, Ken Moffat <zarniwhoop@ntlworld.com> wrote:
> > Seems I can just
> > $export ARFLAGS="rv"
> > before I configure, and it will build and install. Unless there is
> > some reason NOT to do that, please consider this closed.
>
> Well, the reason would be that nobody in practice will do
> that. Make should be setting ARFLAGS correctly (as per
> its documentation) unless you've somehow managed to
> set ARFLAGS to something incorrect in your environment.
> If you "unset ARFLAGS" does it work?
>
> -- PMM
I don't normally touch ARFLAGS. Here's a freshly-untarred qemu
tree.
ken@ac4tv /scratch/ken/tmp/qemu-1.6.1 $echo $ARFLAGS
ken@ac4tv /scratch/ken/tmp/qemu-1.6.1 $unset ARFLAGS
./configure --prefix=/usr --sysconfdir=/etc --target-list=x86_64-softmmu
make
AR libfdt/libfdt.a
ar: two different operation options specified
Makefile:234: recipe for target 'libfdt/libfdt.a' failed
make[1]: *** [libfdt/libfdt.a] Error 1
Makefile:153: recipe for target 'subdir-dtc' failed
make: *** [subdir-dtc] Error 2
ĸen
--
das eine Mal als Tragödie, dieses Mal als Farce
next prev parent reply other threads:[~2013-10-19 9:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-18 22:48 [Qemu-devel] Build failure with make-4.0 Ken Moffat
2013-10-18 23:36 ` Ken Moffat
2013-10-19 9:05 ` Peter Maydell
2013-10-19 9:53 ` Ken Moffat [this message]
2013-10-21 18:22 ` Ken Moffat
2013-10-21 19:37 ` 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=20131019095343.GA24209@milliways \
--to=zarniwhoop@ntlworld.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.