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: Mon, 18 Feb 2013 10:19:32 +0100	[thread overview]
Message-ID: <5121F224.4080906@nedap.com> (raw)
In-Reply-To: <CAPESJy6N4oTvAz9GBLN29UBZ=i1CgfKJ5DOQv3R6BS18AABe1Q@mail.gmail.com>


On 02/16/2013 07:51 AM, Takeshi Hamasaki wrote:

>> if I do
>>
>>      bitbake package-index
>>
>> it crashes with the message
>>
>>      | /bin/bash: opkg-make-index: command not found
>>
>> This is on a 64 debian machine, possibly the wrong path is searched?
>> (there is a opkg-make-index under sysroots/x86_64-linux/usr/bin)
>>
>>

> If you doubt the PATH setting, you should check the output from:
> $ bitbake -e | grep '^export PATH'
>

Well opkg-make-index is in the path.

Something strange is happening here.
If I edit package-index.bb and add a call to opkg-make-index

    do_package_index() {
         set -ex
    opkg-make-index   ### ADDED CODE
         ${PACKAGEINDEXES}
         set +ex
    }


it shows an error message when invoking bitbake package-index showing 
that opkg-make-index is actualy working...

    ///
    .../build/tmp-angstrom_v2012_05-eglibc/sysroots/x86_64-linux/usr/bin/opkg-make-index
    [-h] [-s] [-m] [-l Packages.filelist] [-p Packages] [-r
    Packages.old] [-L localesdir] [-v] packagesdir
    NOTE: package package-index-1.0-r0: task do_package_index: Failed
    ///

Any idea?





  reply	other threads:[~2013-02-18  9:35 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 [this message]
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
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=5121F224.4080906@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.