mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Alexander Aring <alex.aring@gmail.com>
To: Lucas Stach <l.stach@pengutronix.de>
Cc: barebox@lists.infradead.org
Subject: Re: [PATCH] Makefile: fix mixed implicit and normal rules
Date: Tue, 2 Jul 2013 14:31:11 +0200	[thread overview]
Message-ID: <20130702123109.GB27278@x61s.campuswlan.hs-rm.de> (raw)
In-Reply-To: <1372767660.4277.10.camel@weser.hi.pengutronix.de>

Hi,

On Tue, Jul 02, 2013 at 02:21:00PM +0200, Lucas Stach wrote:
> Am Dienstag, den 02.07.2013, 14:24 +0200 schrieb Alexander Aring:
> > Hi,
> > 
> > i am not a make expert but this is a common error with newer make
> > versions.
> > 
> > But I think this solution isn't correct. It's better to split in two
> > rules like:
> > 
> > images/%.s: barebox.bin FORCE
> >         $(Q)$(MAKE) $(build)=images $@
> > 
> > images: barebox.bin FORCE
> >         $(Q)$(MAKE) $(build)=images $@
> > 
> > Getting this information from:
> > http://www.linuxquestions.org/questions/linux-software-2/error-mixed-implicit-and-normal-rules-while-trying-to-build-busybox-826795/
> > 
> > Regards
> > Alex
> > 
> > 
> This is already fixed. See message
> 1372457390-20162-1-git-send-email-dev@lynxeye.de
> "[PATCH] Split Multimage Makefile rule in explicit and implicit parts"
> 

ah good to know. Thanks and sry for the noise. :-)

_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

      reply	other threads:[~2013-07-02 12:28 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-02 12:09 Alexander Aring
2013-07-02 12:24 ` Alexander Aring
2013-07-02 12:21   ` Lucas Stach
2013-07-02 12:31     ` Alexander Aring [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=20130702123109.GB27278@x61s.campuswlan.hs-rm.de \
    --to=alex.aring@gmail.com \
    --cc=barebox@lists.infradead.org \
    --cc=l.stach@pengutronix.de \
    /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