All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Richard Purdie" <richard.purdie@linuxfoundation.org>
To: Ashish <ashish.emailaddress@gmail.com>, poky@lists.yoctoproject.org
Subject: Re: [poky] Bitbake fails to create SDK meanwhile can create image
Date: Tue, 07 Jan 2020 10:21:49 +0000	[thread overview]
Message-ID: <b6945ce213eb80bf2d9cc3fd752d6ab53969fd8c.camel@linuxfoundation.org> (raw)
In-Reply-To: <WQx6.1577962852433588681.umzP@lists.yoctoproject.org>

On Thu, 2020-01-02 at 03:00 -0800, Ashish wrote:
> Hi All , 
> 
> bitbake -c populate_sdk  <IMAGE> fails with below error :
> | checking target system type... Invalid configuration `x86_64-build-
> config-policy-basicsdk-linux': more than four components
> | configure: error: /bin/sh ../config.sub x86_64-build-config-policy-
> basicsdk-linux failed
> 
> But for same setup i am able to generate an working image using
> bitbake -k <IMAGE>
> Here IMAGE = images/armour-whiplash-image.bb  & DISTRO
> = conf/distro/build-config-policy-basic.conf
> ( both derived from qemux86-64 )
> 
> 1) Can member please provide any pointer / debug step as why the
> binutils-crosssdk fails to compile 
>     when SDK is created but compiles fine when image is created. 
> 2) I even tried with cleanall option with binutils , but same
> behaviour .

I think the issue is you're using a DISTRO name with dashes in (build-
config-policy-basic) which is confusing autotools.

Try using something without dashes.

Cheers,

Richard




  parent reply	other threads:[~2020-01-07 10:21 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-02 11:00 Bitbake fails to create SDK meanwhile can create image Ashish
2020-01-06 10:11 ` Ashish
2020-01-06 16:54   ` [poky] " Khem Raj
2020-01-07  6:30     ` Ashish
2020-01-07 10:21 ` Richard Purdie [this message]
2020-01-07 10:57   ` Ashish

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=b6945ce213eb80bf2d9cc3fd752d6ab53969fd8c.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --cc=ashish.emailaddress@gmail.com \
    --cc=poky@lists.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.