On Mon, Oct 21, 2013 at 02:06:14PM -0400, Paul Smith wrote:
> On Mon, 2013-10-21 at 18:48 +0100, Ken Moffat wrote:
> > Thanks. Is it OK if I quote this whole reply to the qemu devs ?
>
> Of course. This mailing list is publicly archived; quote away.
>
> Or point them to the thread:
> http://lis
On Mon, 2013-10-21 at 18:48 +0100, Ken Moffat wrote:
> Thanks. Is it OK if I quote this whole reply to the qemu devs ?
Of course. This mailing list is publicly archived; quote away.
Or point them to the thread:
http://lists.gnu.org/archive/html/bug-make/2013-10/msg00151.html
On Mon, Oct 21, 2013 at 12:51:11PM -0400, Paul Smith wrote:
> On Mon, 2013-10-21 at 17:36 +0100, Ken Moffat wrote:
> > I haven't even figured out where quiet-command is located. I'm
> > only an integration monkey, checking that everything in our "distro"
> > (BLFS) will build with make-4.0. Will
On Mon, Oct 21, 2013 at 01:11:47PM -0400, Paul Smith wrote:
> On Mon, 2013-10-21 at 18:03 +0100, Ken Moffat wrote:
> > 2. Unfortunately, rules.mak *is* adding -rR to the MAKEFLAGS -
> >
> > # Don't use implicit rules or variables
> > # we have explicit rules for everything
> > MAKEFLAGS += -rR
>
On Mon, 2013-10-21 at 16:02 +0100, Ken Moffat wrote:
>
> # command line
> ARFLAGS =
So this tells us that the empty value is being set from the command
line.
> I then ran it in the directory where the build fails (dtc/) -
>
> # makefile (from 'Makefile', line 51)
> ARFLAGS = rc
This is not i
On Mon, 2013-10-21 at 18:03 +0100, Ken Moffat wrote:
> 2. Unfortunately, rules.mak *is* adding -rR to the MAKEFLAGS -
>
> # Don't use implicit rules or variables
> # we have explicit rules for everything
> MAKEFLAGS += -rR
> I'll attach rules.mak. Is this a qemu bug which just happened to
> wor
On Mon, Oct 21, 2013 at 05:36:24PM +0100, Ken Moffat wrote:
> On Mon, Oct 21, 2013 at 04:02:58PM +, Edward Welbourne wrote:
> > > It's the long one (subdir-dtc) where the problem exists.
> >
> > Obvious first step: configure quiet-command to actually show the
> > command, or remove this wrappi
On Mon, 2013-10-21 at 17:36 +0100, Ken Moffat wrote:
> I haven't even figured out where quiet-command is located. I'm
> only an integration monkey, checking that everything in our "distro"
> (BLFS) will build with make-4.0. Will take a look.
Please see my second email, from earlier today.
Base
On Mon, Oct 21, 2013 at 04:02:58PM +, Edward Welbourne wrote:
> > It's the long one (subdir-dtc) where the problem exists.
>
> Obvious first step: configure quiet-command to actually show the
> command, or remove this wrapping from the command, so that you can see
> what the sub-make actually
> It's the long one (subdir-dtc) where the problem exists.
Obvious first step: configure quiet-command to actually show the
command, or remove this wrapping from the command, so that you can see
what the sub-make actually gets invoked with. We can guess, but it may
help to be entirely clear ! On
On Mon, Oct 21, 2013 at 12:02:20AM -0400, Paul Smith wrote:
> On Mon, 2013-10-21 at 04:05 +0100, Ken Moffat wrote:
> > With GNU Make 4.0 on x86_64-unknown-linux-gnu I am unable to build
> > qemu 1.6.{0,1} because it fails with
> > AR libfdt/libfdt.a
> > ar: two different operation options
On Mon, 2013-10-21 at 04:05 +0100, Ken Moffat wrote:
> With GNU Make 4.0 on x86_64-unknown-linux-gnu I am unable to build
> qemu 1.6.{0,1} because it fails with
> AR libfdt/libfdt.a
> ar: two different operation options specified
> Makefile:234: recipe for target 'libfdt/libfdt.a' failed
12 matches
Mail list logo
