All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marek Vasut <marex@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] tools: mxsboot: Use more portable cpu_to_le32()
Date: Mon, 25 Jan 2016 04:47:55 +0100	[thread overview]
Message-ID: <201601250447.55611.marex@denx.de> (raw)
In-Reply-To: <1453693112-15575-1-git-send-email-bmeng.cn@gmail.com>

On Monday, January 25, 2016 at 04:38:32 AM, Bin Meng wrote:
> Currently when building mxsboot on certain machines it reports:
> 
>   HOSTCC  tools/mxsboot
>   tools/mxsboot.c: In function 'mx28_create_sd_image':
>   tools/mxsboot.c:560: warning: implicit declaration of function 'htole32'
>   /tmp/cchLIV6q.o: In function 'main':
>   mxsboot.c:(.text+0x6d8): undefined reference to 'htole32'
>   mxsboot.c:(.text+0x6e7): undefined reference to 'htole32'
>   mxsboot.c:(.text+0x6f6): undefined reference to 'htole32'
>   mxsboot.c:(.text+0x705): undefined reference to 'htole32'
>   mxsboot.c:(.text+0x711): undefined reference to 'htole32'
>   /tmp/cchLIV6q.o:mxsboot.c:(.text+0x71d): more undefined references to
>   'htole32' follow
>   collect2: ld returned 1 exit status
>   make[1]: *** [tools/mxsboot] Error 1
>   make: *** [tools] Error 2
> 
> The solution is to use cpu_to_le32() instead which is more portable,
> just like other U-Boot tools [1] do.
> 
> [1] http://lists.denx.de/pipermail/u-boot/2014-October/192919.html
> 
> Suggested-by: Marek Vasut <marex@denx.de>
> Signed-off-by: Bin Meng <bmeng.cn@gmail.com>

Acked-by: Marek Vasut <marex@denx.de>

Thanks!

Best regards,
Marek Vasut

  reply	other threads:[~2016-01-25  3:47 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-25  3:38 [U-Boot] [PATCH] tools: mxsboot: Use more portable cpu_to_le32() Bin Meng
2016-01-25  3:47 ` Marek Vasut [this message]
2016-02-02 20:02 ` Stefano Babic

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=201601250447.55611.marex@denx.de \
    --to=marex@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.