From: Stephen Warren <swarren@wwwdotorg.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] kbuild,tegra124: add dummy obj- for Kbuild
Date: Wed, 19 Feb 2014 13:44:43 -0700 [thread overview]
Message-ID: <530517BB.4070506@wwwdotorg.org> (raw)
In-Reply-To: <20140219204047.GF19081@bill-the-cat>
On 02/19/2014 01:40 PM, Tom Rini wrote:
> On Wed, Feb 19, 2014 at 09:36:14AM -0700, Stephen Warren wrote:
>> On 02/19/2014 07:46 AM, Albert ARIBAUD wrote:
>>> Hi Masahiro,
>>>
>>> On Wed, 19 Feb 2014 22:26:43 +0900, Masahiro Yamada
>>> <yamada.m@jp.panasonic.com> wrote:
>>>
>>>> In Kbuild, every makefile must have non-empty obj- or obj-y.
>>>> Otherwise, built-in.o will not be created and the link stage
>>>> will fail.
>> ...
>>>> diff --git a/arch/arm/cpu/armv7/tegra124/Makefile b/arch/arm/cpu/armv7/tegra124/Makefile
>> ...
>>>> +# necessary to create built-in.o
>>>> +obj- := __dummy__.o
>>
>> obj- or obj-y?
>>
>> Adding something to obj-, which presumably isn't used at all, seems very
>> odd.
>
> Why do we even need arch/arm/cpu/armv7/tegra124/Makefile ? I assume we
> need the config.mk because we can't stick CONFIG_ARCH_DEVICE_TREE into
> the config header?
At least with the current build system, if I delete it, the build fails:
> + make BUILD_DIR=/home/swarren/shared/git_wa/tegra-uboot-flasher/_build/venice2/u-boot -s -j9
> /home/swarren/shared/git_wa/tegra-uboot-flasher/u-boot/scripts/Makefile.build:11: Makefile: No such file or directory
> make[1]: *** No rule to make target `Makefile'. Stop.
> make: *** [/home/swarren/shared/git_wa/tegra-uboot-flasher/_build/venice2/u-boot/arch/arm/cpu/armv7/tegra124/built-in.o] Error 2
next prev parent reply other threads:[~2014-02-19 20:44 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-19 13:26 [U-Boot] [PATCH] kbuild,tegra124: add dummy obj- for Kbuild Masahiro Yamada
2014-02-19 14:46 ` Albert ARIBAUD
2014-02-19 16:36 ` Stephen Warren
2014-02-19 20:40 ` Tom Rini
2014-02-19 20:44 ` Stephen Warren [this message]
2014-02-20 8:35 ` Masahiro Yamada
2014-02-20 8:24 ` Masahiro Yamada
2014-02-20 16:15 ` Stephen Warren
2014-02-21 11:45 ` Masahiro Yamada
2014-02-21 16:33 ` Stephen Warren
2014-02-20 8:23 ` Masahiro Yamada
2014-02-20 9:06 ` Albert ARIBAUD
2014-02-19 20:51 ` Tom Rini
2014-02-20 8:22 ` Masahiro Yamada
2014-02-20 13:25 ` Tom Rini
2014-02-19 21:12 ` Tom Rini
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=530517BB.4070506@wwwdotorg.org \
--to=swarren@wwwdotorg.org \
--cc=u-boot@lists.denx.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