Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Mohammed Amine SAYA <amine.saya@free.fr>
To: Using the OpenEmbedded metadata to build Linux Distributions
	<openembedded-devel@lists.openembedded.org>
Subject: Re: sysvinit-2.86 fails
Date: Sun, 27 Aug 2006 17:51:54 +0200	[thread overview]
Message-ID: <44F1BF9A.2010908@free.fr> (raw)
In-Reply-To: <74d0deb30608270048t1098d042ne95ed5df666fae7a@mail.gmail.com>

pHilipp Zabel wrote:
>> Hi all,
>>
>> As I said before, sysvinit don't build successfully so I replaced
>>
>> ln -s ../init.d/stop-bootlogd ${D}${sysconfdir}/rc$level.d/S99stop-bootlogd
>>
>> with
>>
>> ln -sf ../init.d/stop-bootlogd ${D}${sysconfdir}/rc$level.d/S99stop-bootlogd
>>
>>
>> But I am not sure that is the right way ? Any comment on this workaround please ?
>>     
>
> I think the problem lies here:
>
> NOTE: package sysvinit-2.86-r28: task do_install: started
> NOTE: package sysvinit-2.86-r28: task do_install: completed
> NOTE: package sysvinit-2.86-r28: task do_package: started
> ERROR: function do_install failed
>
> PACKAGEFUNCS in package.bbclass contains do_install as first element,
> so do_install is run twice. After removing do_install from
> PACKAGEFUNCS, installation works fine.
>   
Hi All, Hi Philipp,

Thanks a lot for your help, this actually solves all the problems I 
reported before.
busybox, sysvinit are now working fine without tweaking their bb files.

Do you have any doc on BITBAKE variables. I know that DEPENDS and RDEPENDS
functions have changed with the new bitbake version, can you point me to 
a link
where all these variables are explained ?


Thanks again.

Best regards,
Amine.



      reply	other threads:[~2006-08-27 14:47 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-26 15:35 sysvinit-2.86 fails Mohammed Amine SAYA
2006-08-26 20:20 ` Mohammed Amine SAYA
2006-08-27  7:48   ` pHilipp Zabel
2006-08-27 15:51     ` Mohammed Amine SAYA [this message]

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=44F1BF9A.2010908@free.fr \
    --to=amine.saya@free.fr \
    --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