From mboxrd@z Thu Jan  1 00:00:00 1970
From: Albert ARIBAUD <albert.u.boot@aribaud.net>
Date: Wed, 19 Feb 2014 15:46:59 +0100
Subject: [U-Boot] [PATCH] kbuild,tegra124: add dummy obj- for Kbuild
In-Reply-To: <1392816403-9101-1-git-send-email-yamada.m@jp.panasonic.com>
References: <1392816403-9101-1-git-send-email-yamada.m@jp.panasonic.com>
Message-ID: <20140219154659.5f1ba763@lilith>
List-Id: <u-boot.lists.denx.de>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
To: u-boot@lists.denx.de

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.
> 
> Signed-off-by: Masahiro Yamada <yamada.m@jp.panasonic.com>
> ---
> 
> Tom,
> Please apply this along with the Kbuild series.
> 
> 
> 
>  arch/arm/cpu/armv7/tegra124/Makefile | 3 +++
>  1 file changed, 3 insertions(+)
> 
> diff --git a/arch/arm/cpu/armv7/tegra124/Makefile b/arch/arm/cpu/armv7/tegra124/Makefile
> index 7f127b1..9478d44 100644
> --- a/arch/arm/cpu/armv7/tegra124/Makefile
> +++ b/arch/arm/cpu/armv7/tegra124/Makefile
> @@ -4,3 +4,6 @@
>  #
>  # SPDX-License-Identifier:     GPL-2.0+
>  #
> +
> +# necessary to create built-in.o
> +obj- := __dummy__.o

Is there really no other way than to specify an unexisting __dummy__.o
in order to build a useless built-in.o?

Amicalement,
-- 
Albert.