All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jaap de Jong <jaap.dejong@nedap.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: opkg-make-index not found
Date: Tue, 19 Feb 2013 16:07:59 +0100	[thread overview]
Message-ID: <5123954F.1000306@nedap.com> (raw)
In-Reply-To: <CAPESJy6xoZS3hGLwiFY2d7NRsH438hPDgK+=gJXFZd0Q1Cxd6w@mail.gmail.com>


On 02/19/2013 03:33 PM, Takeshi Hamasaki wrote:
> Then I recommend to look into log files. For my case, after executing commands:
>
> $ bitbake package-index -c cleansstate
> $ bitbake -D -D package-index > bitbake-d-d.package-index 2> errlog
>
> I have at least four log files.
> 1. bitbake-d-d.package-index in current dir
> 2. errlog   in current dir
> 3. run.do_package_index.* in
> build/tmp-angstrom_v2012_05-eglibc/work/armv5te-angstrom-linux-gnueabi/package-index-1.0-r0
> 4. log.do_package_index.* in
> build/tmp-angstrom_v2012_05-eglibc/work/armv5te-angstrom-linux-gnueabi/package-index-1.0-r0
>
> (Actually, I skipped to generate 2., my build succeed.)
> I guess you can find some clue looking into 4., 3., and maybe 1.
>
> I attach mine to this mail, and hope they might be some help for you.
Thanks for all your help!
I've been comparing the run.do_package_index file from myself and from 
the buildserver.
If I look at it the only real difference (besides paths etc) are in the 
SHELL
 > export SHELL="/usr/local/bin/bash-wrapper"
< export SHELL="/bin/bash"
I will ask my administrator to change it and will retry.





  reply	other threads:[~2013-02-19 15:24 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-15 13:25 opkg-make-index not found Jaap de Jong
2013-02-16  6:51 ` Takeshi Hamasaki
2013-02-18  9:19   ` Jaap de Jong
2013-02-18 15:19     ` Takeshi Hamasaki
2013-02-19 13:46       ` Jaap de Jong
2013-02-19 14:33         ` Takeshi Hamasaki
2013-02-19 15:07           ` Jaap de Jong [this message]
2013-02-20 14:38             ` Jaap de Jong

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=5123954F.1000306@nedap.com \
    --to=jaap.dejong@nedap.com \
    --cc=openembedded-devel@lists.openembedded.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.