Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] prevent recursion in %_defconfig rules
Date: Fri, 17 Jan 2014 20:54:05 +0100	[thread overview]
Message-ID: <20140117195405.GC3982@free.fr> (raw)
In-Reply-To: <20140117180935.GB3982@free.fr>

J?r?my, All,

On 2014-01-17 19:09 +0100, Yann E. MORIN spake thusly:
> On 2014-01-17 18:52 +0100, Yann E. MORIN spake thusly:
> > On 2014-01-07 17:22 +0100, J?r?my Rosen spake thusly:
> > > Signed-off-by: J?r?my Rosen <jeremy.rosen@openwide.fr>
> > > 
> > > ---
> > > The following command, run from a clean buildroot checkout
> > > 
> > > make O=.. BR2_EXTERNAL=.. raspberrypi_defconfig
> > > 
> > > cause the following output, and makes stop :
> > > 
> > > 
> > > make: *** Pas de r?gle pour fabriquer la cible ? /home/rosen/tmp/buildroot/
> > > configs/../configs/../configs/../configs/<lots more >/../configs/
> > > raspberrypi_defconfig ?, n?cessaire pour ? /home/rosen/tmp/buildroot/
> > > configs/../configs/../configs/<lots more>/../configs/
> > > raspberrypi_defconfig ?. Arr?t.
> > > 
> > > The problem is that the buildroot makefile has two rules to generate
> > > %_defconfig: One that depends on $(TOPDIR)/configs/%_defconfig and the
> > > other one that depends on $(BR2_EXTERNAL)/configs/%_defconfig.
> > > 
> > > When one rule checks for the file, the other rule becomes an implicit rule
> > > for the dependancy causing an infinite cross-recursion.
> > > 
> > > By overriding the implicit rule, we prevent the infinite recursion.
> > 
> > This breaks defconfigs from BR2_EXTERNAL when used with an out-of-tree
> > build:
> > 
> >     make -C /path/to/buildroot              \
> >          O=/path/to/build                   \
> >          BR2_EXTERNAL=/path/to/br2.external \
> >          yem_defconfig
> >     [--SNIP--]
> >     *** Can't find default configuration "/home/ymorin/dev/buildroot/buildroot/configs/yem_defconfig"!
> 
> It even breaks BR2_EXTERNAL for in-tree builds.
> 
> Reverting that patch fixes both issues, and does not exhibit the
> reported problem.
> 
> Peter, can we just revert that patch (cset 94dd02f) for now, please?
> 
> J?r?my, can you describe your setup, so we can try to reproduce it, and
> find a proper fix?

Out of curiosity, I just installed a make-4.0 to make sure that was not
due to some idiocy of make-4.0 (since it hs changed quite a few
behaviours that were relied on from previous versions, such as the
ordering of files in $(wildcard ...) ).

But no, it works as expected, with make-3.81 and make-4.0 alike.

Regards,
Yann E. MORIN.

-- 
.-----------------.--------------------.------------------.--------------------.
|  Yann E. MORIN  | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software  Designer | \ / CAMPAIGN     |  ___               |
| +33 223 225 172 `------------.-------:  X  AGAINST      |  \e/  There is no  |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL    |   v   conspiracy.  |
'------------------------------^-------^------------------^--------------------'

  reply	other threads:[~2014-01-17 19:54 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-07 16:22 [Buildroot] [PATCH] prevent recursion in %_defconfig rules Jérémy Rosen
2014-01-13  8:52 ` Jeremy Rosen
2014-01-13  8:59   ` Peter Korsgaard
2014-01-17 17:52 ` Yann E. MORIN
2014-01-17 18:09   ` Yann E. MORIN
2014-01-17 19:54     ` Yann E. MORIN [this message]
2014-01-20  8:03       ` Jeremy Rosen
2014-01-20  8:13         ` Jeremy Rosen
2014-01-20 18:31           ` Yann E. MORIN
2014-01-20 22:58           ` Romain Naour
2014-01-20 23:58             ` Yann E. MORIN
2014-01-21  8:44               ` Jeremy Rosen
2014-01-21 18:38                 ` Yann E. MORIN
2014-01-22 14:16                   ` Jeremy Rosen

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=20140117195405.GC3982@free.fr \
    --to=yann.morin.1998@free.fr \
    --cc=buildroot@busybox.net \
    /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