All of lore.kernel.org
 help / color / mirror / Atom feed
From: Uwe Geuder <jrswdnan22@snkmail.com>
To: yocto@yoctoproject.org
Subject: Busybox_1.23.2 fails at do_compile on Poky-Sumo
Date: Sun, 04 Nov 2018 14:41:44 +0200	[thread overview]
Message-ID: <877ehtj9pz.fsf@linux.suse> (raw)
In-Reply-To: <CAKPYHZ4VV_+PpwJE_=EVq2HNxfU4PuCjg-2T+AueB+9Jv1eG9A@mail.gmail.com>

On Thu, Oct 18, 2018 at 11:03 AM Dhanush K.S dhanush.ks-at-gmail.com wrote:
>
> Hello Yocto,
>
> I'm currently building an image with the busybox_1.23.2.bb recipe
> included, using Yocto Sumo 2.5 with the Bitbake version 1.37.0. It is
> running on a CentOS host building images for the target ARM
> cortexa8. This busybox recipe is placed in another custom
> layer. Though this recipe compiles without errors in Poky-Fido, in
> Poky-Sumo I get compilation errors due to missing header files. I have
> pasted a part of the log.do.compile file with the error.

Well, Fido sounds very old, long before I started to use Yocto :) It was
probably before recipe-specific sysroots so a lot has changed.  On the
other hand byteswap.h, which it complains about, comes from glibc and
that you should have.  Maybe it's complicated in your case by a platform
specific implmentation I don't happen to have here right now.

Do you have a reason to build such an old busybox recipe? I get version
1.27.2 from meta (i.e. oe-core) and it builds.

Also your bitbake 1.37.0 indicates that you are not running the latest
Sumo 2.5.1 which has bitbake 1.38.0. Although I don't really expect that
it would solve your issue here, updating to 2.5.1 should be painless if
you are on 2.5 already.

Uwe Geuder
Neuro Event Labs Oy
Tampere, Finland
uwe.gexder at neuroeventlabs.com (Bot check: fix one obvious typo)


  parent reply	other threads:[~2018-11-04 12:41 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-18  8:02 Busybox_1.23.2 fails at do_compile on Poky-Sumo Dhanush K.S
2018-10-18 15:49 ` Khem Raj
2018-10-19  9:31   ` Dhanush K.S
2018-11-04 12:41 ` Uwe Geuder [this message]
2018-10-19 13:58 Dhanush K.S
2018-10-23  9:58 Dhanush K.S
2018-10-23 19:35 ` Andre McCurdy

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=877ehtj9pz.fsf@linux.suse \
    --to=jrswdnan22@snkmail.com \
    --cc=yocto@yoctoproject.org \
    /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.