public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Lukasz Majewski <lukma@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] spl: dfu: compilation fixes for spl-dfu
Date: Tue, 18 Apr 2017 16:44:33 +0200	[thread overview]
Message-ID: <20170418164433.4644c46c@jawa> (raw)
In-Reply-To: <1492525535-28091-1-git-send-email-ravibabu@ti.com>

Hi Ravi,

> This patch fixes the compilation error
> common/cli_hush.c:3349: undefined reference to 'realloc_simple'
> 
> The dfu uses run_command(), it is part of cli_hush.c
> but defining CONFIG_HUSH_PARSER for spl-dfu causes
> this compilation error.
> 
> Signed-off-by: Ravi Babu <ravibabu@ti.com>
> ---
>  common/cli.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/common/cli.c b/common/cli.c
> index a433ef2..5e0869b 100644
> --- a/common/cli.c
> +++ b/common/cli.c
> @@ -28,7 +28,7 @@ DECLARE_GLOBAL_DATA_PTR;
>   */
>  int run_command(const char *cmd, int flag)
>  {
> -#ifndef CONFIG_HUSH_PARSER
> +#if defined(CONFIG_SPL_DFU_SUPPORT) || !defined(CONFIG_HUSH_PARSER)

I must admit that this seems odd to me....since we should avoided adding
(SPL DFU) dependency to common parser code.

Maybe some kconfig tweaks would help?

>  	/*
>  	 * cli_run_command can return 0 or 1 for success, so clean up
>  	 * its result.




Best regards,

Lukasz Majewski

--

DENX Software Engineering GmbH,      Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de

  reply	other threads:[~2017-04-18 14:44 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-18 14:25 [U-Boot] [PATCH] spl: dfu: compilation fixes for spl-dfu Ravi Babu
2017-04-18 14:44 ` Lukasz Majewski [this message]
2017-04-19  7:19   ` B, Ravi
     [not found] <1492589976-11595-1-git-send-email-ravibabu@ti.com>
2017-04-19 10:53 ` Lukasz Majewski
2017-04-19 11:00   ` B, Ravi
2017-04-20 12:49   ` B, Ravi

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=20170418164433.4644c46c@jawa \
    --to=lukma@denx.de \
    --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