mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Russell Haley <russ.haley@gmail.com>
To: Sascha Hauer <s.hauer@pengutronix.de>
Cc: barebox@lists.infradead.org
Subject: Re: Building on PC-BSD 10.3
Date: Wed, 27 Apr 2016 09:09:00 -0700	[thread overview]
Message-ID: <CABx9NuQUz+cb4K5LDuBgoVQTHW-=bv0M-Ko_S05hUHh0dSd_gA@mail.gmail.com> (raw)
In-Reply-To: <20160427091405.GS7860@pengutronix.de>

On Wed, Apr 27, 2016 at 2:14 AM, Sascha Hauer <s.hauer@pengutronix.de> wrote:
> Hi Russell,
>
> On Tue, Apr 26, 2016 at 09:59:10PM -0700, Russell Haley wrote:
>> Hello,
>>
>> Just for a hoot I thought I'd build barebox on PC-BSD 10.3. I followed
>> these directions:
>>
>> https://github.com/jcobham/i.MX53-kernel-images/wiki/How-To:-Build-Barebox-for-IMX53
>>
>> and replaced "make" with "gmake". Here is the output:
>>
>> http://pastebin.com/AawYq4bR
>>
>> It seems to be missing endian.h?
>
> Yes, seems so. From "man 3 endian" on Linux:
>
>> These functions are nonstandard.  Similar functions are present on
>> the BSDs, where the required header file is <sys/endian.h> instead of
>> <endian.h>.  Unfortunately, NetBSD, FreeBSD, and glibc haven't
>> followed the original OpenBSD naming convention for these functions,
>> whereby the nn component always appears at the end of the function
>> name (thus, for example, in NetBSD, FreeBSD, and glibc, the
>> equivalent of OpenBSDs "betoh32" is "be32toh").
>
> We now have scripts/include/tools/endian.h from the Linux kernel. Does
> the change below help? (The same change may be needed elsewhere in
> /scripts/)
>
> Sascha
>
> ------------------------8<-------------------------------
>
> diff --git a/scripts/imx/imx-image.c b/scripts/imx/imx-image.c
> index 16f086a..c8fe5bf 100644
> --- a/scripts/imx/imx-image.c
> +++ b/scripts/imx/imx-image.c
> @@ -26,7 +26,7 @@
>  #include <sys/types.h>
>  #include <sys/stat.h>
>  #include <fcntl.h>
> -#include <endian.h>
> +#include <tools/endian.h>
>  #include <linux/kernel.h>
>  #include <sys/file.h>
>
>
> --
> Pengutronix e.K.                           |                             |
> Industrial Linux Solutions                 | http://www.pengutronix.de/  |
> Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0    |
> Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |

Awesome, thanks so much. I'll try that tonight!

Russ

_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

  reply	other threads:[~2016-04-27 16:09 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-27  4:59 Russell Haley
2016-04-27  9:14 ` Sascha Hauer
2016-04-27 16:09   ` Russell Haley [this message]
2016-04-30  9:40 ` DU HUANPENG
2016-05-01  5:56   ` Russell Haley

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='CABx9NuQUz+cb4K5LDuBgoVQTHW-=bv0M-Ko_S05hUHh0dSd_gA@mail.gmail.com' \
    --to=russ.haley@gmail.com \
    --cc=barebox@lists.infradead.org \
    --cc=s.hauer@pengutronix.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