From: Mike Westerhof <mike@mwester.net>
To: openembedded-devel@lists.openembedded.org
Subject: Re: postinst scripts and opkg configure
Date: Fri, 09 Apr 2010 09:26:40 -0500 [thread overview]
Message-ID: <4BBF3920.1000702@mwester.net> (raw)
In-Reply-To: <q2r48239d391004090658m577b6d71vcde72629078be670@mail.gmail.com>
Sergey Lapin wrote:
>> Actually, update-rc.d scripts should work on build host (that "$OPT" in script
>> is exactly for that purpose) and so are update-alternatives (thanks to
>> OPKG_OFFLINE_ROOT magic), so there might be something wrong with your setup.
> I found the reason for that error - update-rc.d is not being staged,
> so scripts fail.
Same problem encountered here - this commit fixed it for SlugOS (which
has its own initscripts which explicitly invoke update-rc.d, thus
causing an obvious build failure): c906fd7faa8517ca565faba90887d10ebb90e092
Basically, adding RDEPENDS="update-rc.d" and
DEPENDS="update-rc.d-native" resolved the issue.
(I glanced at the other initscripts BB files, and didn't change those
because there wasn't an obvious reference to update-rc.d in the recipes
-- I didn't consider the use case you described or I would have fixed
those recipes as well.)
> bitbake update-rc.d update-rc.d-native -c rebuild doesn't help either.
> Can't see why, because copying it from workdir to staging bin fixes
> this problem.
> Any ideas?
>
> S.
-Mike (mwester)
next prev parent reply other threads:[~2010-04-09 14:37 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-09 10:26 postinst scripts and opkg configure Sergey Lapin
2010-04-09 10:39 ` Roman I Khimov
2010-04-09 10:53 ` Sergey Lapin
2010-04-09 11:26 ` Roman I Khimov
2010-04-09 13:58 ` Sergey Lapin
2010-04-09 14:26 ` Mike Westerhof [this message]
2010-04-09 14:52 ` [PATCH] update-rc.d.bbclass: add dependency on update-rc.d-native Roman I Khimov
2010-04-09 11:19 ` [PATCH] rootfs_ipk.bbclass: run preinst/postinst scripts with "-e" Roman I Khimov
2010-04-09 15:48 ` Chris Larson
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=4BBF3920.1000702@mwester.net \
--to=mike@mwester.net \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox