From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] uboot.pbl - make 'include' issue
Date: Thu, 1 May 2014 00:39:10 +0200 [thread overview]
Message-ID: <20140430223910.GF3336@free.fr> (raw)
In-Reply-To: <OFB2294D5B.F4E5AC38-ON86257CCA.00752EA9-86257CCA.00753202@rockwellcollins.com>
Ryan, Thomas, All,
On 2014-04-30 16:20 -0500, Ryan Barnett spake thusly:
> I have recently been working on trying to get support for the u-boot.pbl
> image format into buildroot. I submitted an initial patch set back in
> October and was given feedback to break out the boot/uboot/uboot.mk into
> processor specific architectures. Thomas Petazzoni and I did some initial
> work to split these out and he provide an example. I have been trying to
> take this work that he did and submit an updated patch set. However, I
> have hit a roadblock for which I can't seem to debug or figure out what is
> going wrong.
>
> When I breakout defines and variables in boot/uboot/uboot.mk into separate
> files and add the following line:
>
> include boot/uboot/*/*.mk
>
> Once I add this to uboot.mk, the rules for uboot no longer work. Using any
> configuration, I can no longer do anything like this:
>
> make uboot
> make uboot-dirclean
>
> Running the above yields the following error:
>
> make[1]: *** No rule to make target `uboot'. Stop.
> make: *** [_all] Error 2
Yes, that's not so surprising:
- the $(eval $(generic-package)) use the $(pkgname) macro, which uses
the $(pkgdir) macro
- the $(pkgdir) macro is defined as thus:
pkgdir = $(dir $(lastword $(MAKEFILE_LIST)))
- and $(MAKEFILE_LIST) contains the _last_ Makefile that was parsed
- but the pkg-inra expects that the last Makefile parsed be the
current Makefile
Since you include other Makefiles from uboot.mk:
boot/uboot/ppc-freescale/uboot-ppc-freescale.mk
then $(MAKEFILE_LIST) will end up with that when you call the usual eval
above, from which the generic-package derives the $(pkgdir) to be
"boot/uboot/ppc-freescale", and thus the $(pkgname) to be
"ppc-freescale", and not the "uboot" you expect.
So I'm afraid this approach won't work.
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. |
'------------------------------^-------^------------------^--------------------'
next prev parent reply other threads:[~2014-04-30 22:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-30 21:20 [Buildroot] uboot.pbl - make 'include' issue Ryan Barnett
2014-04-30 22:39 ` Yann E. MORIN [this message]
2014-04-30 22:42 ` Yann E. MORIN
2014-04-30 22:47 ` Thomas Petazzoni
2014-04-30 23:02 ` Yann E. MORIN
2014-05-01 0:26 ` Thomas Petazzoni
2014-05-01 16:58 ` rjbarnet at rockwellcollins.com
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=20140430223910.GF3336@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