[OPENBMC] Bitbake error:Nothing RPROVIDES'virtual=p9-vcs-workaround'

Solon Fan Solon.Fan at flex.com
Thu Jun 11 17:59:23 AEST 2020


Hi,Joel!



Thanks for your tips.



I modified below file, the build error not occurs again.-[ERROR: Nothing RPROVIDES 'virtual-p9-vcs-workaround'],for your reference.



~/meta-romulus-prime/recipes-phosphor/host/p9-host-start.bbappend



Change

RDEPENDS_${PN}remove_romulus = "p9-vcs-workaround"

to

RDEPENDS${PN}remove_romulus-prime = "p9-vcs-workaround"




Kind Regards
[cid:image001.png at 01D64009.428E1760]
Solon Fan
CCS Design BMC

4F, Bldg. 10, No. 3000 Longdong Ave.,
Pudong New District, Shanghai 201203, China
direct: +86 021 20821600 Ext 1402
mobile: +86 18606220885

[cid:image002.png at 01D64009.428E1760]<http://www.flex.com/>    [cid:image003.png at 01D64009.428E1760] <https://www.linkedin.com/company/flexintl/>     [cid:image004.png at 01D64009.428E1760] <https://twitter.com/Flexintl>     [cid:image005.png at 01D64009.428E1760] <https://www.facebook.com/FlexCorporate/>     [cid:image006.png at 01D64009.428E1760] <https://www.youtube.com/c/flexintl>



-----Original Message-----
From: Joel Stanley <joel at jms.id.au>
Sent: 2020年6月11日 10:31
To: Solon Fan <Solon.Fan at flex.com>
Cc: openbmc at lists.ozlabs.org
Subject: Re: [OPENBMC] Bitbake error:Nothing RPROVIDES'virtual=p9-vcs-workaround'



On Thu, 11 Jun 2020 at 01:52, Solon Fan <Solon.Fan at flex.com<mailto:Solon.Fan at flex.com>> wrote:

>

> Hi,All!

>

>

>

> I tried to add a new system followed by the below link guide.

>

>

>

> https://urldefense.com/v3/__https://github.com/openbmc/docs/blob/maste<https://urldefense.com/v3/__https:/github.com/openbmc/docs/blob/maste>

> r/development/add-new-system.md__;!!HSntlCg!Fjt_aBUqNL7urn_JztiPPvQG6J

> w7hpIfiwiRD802cg1unBcvBFKKVdNktHYGZqI$

>

>

>

> But I meet the below error,I am new to yocto,have you meet the same error?Any suggestions could be shared?



meta-openpower/recipes-phosphor/host/p9-vcs-workaround.bb was removed in 389a7046dffd "openpower: Remove VCS workaround service".



I suggest rebasing your changes on the latest master, or at least a commit after 389a7046dffd.



Cheers,



Joel



>

>

>

> solon at solon-Precision-WorkStation-T5500:~/work/OPENBMC/openbmc$

> bitbake obmc-phosphor-image Loading cache: 100%

> |#############################################################| Time: 0:00:01 Loaded 3901 entries from dependency cache.

> Parsing recipes: 100%

> |###########################################################| Time: 0:00:04 Parsing of 2591 .bb files complete (2590 cached, 1 parsed). 3902 targets, 355 skipped, 0 masked, 0 errors.

> NOTE: Resolving any missing task queue dependencies

> ERROR: Nothing RPROVIDES 'virtual-p9-vcs-workaround' (but

> /home/solon/work/OPENBMC/openbmc/meta-openpower/recipes-phosphor/host/

> p9-vcs-workaround.bb RDEPENDS on or otherwise requires it)

> NOTE: Runtime target 'virtual-p9-vcs-workaround' is unbuildable, removing...

> Missing or unbuildable dependency chain was:

> ['virtual-p9-vcs-workaround']

> NOTE: Runtime target 'p9-vcs-workaround' is unbuildable, removing...

> Missing or unbuildable dependency chain was: ['p9-vcs-workaround',

> 'virtual-p9-vcs-workaround']

> NOTE: Runtime target 'virtual-obmc-host-ctl' is unbuildable, removing...

> Missing or unbuildable dependency chain was: ['virtual-obmc-host-ctl',

> 'p9-vcs-workaround', 'virtual-p9-vcs-workaround']

> ERROR: Required build target 'obmc-phosphor-image' has no buildable providers.

> Missing or unbuildable dependency chain was: ['obmc-phosphor-image',

> 'virtual-obmc-host-ctl', 'p9-vcs-workaround',

> 'virtual-p9-vcs-workaround']

>

> Summary: There were 2 ERROR messages shown, returning a non-zero exit code.

>

>

>

> Kind Regards

>

>

> Solon Fan

> CCS Design BMC

>

> 4F, Bldg. 10, No. 3000 Longdong Ave.,

> Pudong New District, Shanghai 201203, China

> direct: +86 021 20821600 Ext 1402

> mobile: +86 18606220885

>

>

>

>

>

> Legal Disclaimer :

> The information contained in this message may be privileged and confidential.

> It is intended to be read only by the individual or entity to whom it

> is addressed or by their designee. If the reader of this message is

> not the intended recipient, you are on notice that any distribution of

> this message, in any form, is strictly prohibited. If you have

> received this message in error, please immediately notify the sender and delete or destroy any copy of this message!
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ozlabs.org/pipermail/openbmc/attachments/20200611/7a7b6a61/attachment-0001.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 3303 bytes
Desc: image001.png
URL: <http://lists.ozlabs.org/pipermail/openbmc/attachments/20200611/7a7b6a61/attachment-0006.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image002.png
Type: image/png
Size: 910 bytes
Desc: image002.png
URL: <http://lists.ozlabs.org/pipermail/openbmc/attachments/20200611/7a7b6a61/attachment-0007.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image003.png
Type: image/png
Size: 320 bytes
Desc: image003.png
URL: <http://lists.ozlabs.org/pipermail/openbmc/attachments/20200611/7a7b6a61/attachment-0008.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image004.png
Type: image/png
Size: 766 bytes
Desc: image004.png
URL: <http://lists.ozlabs.org/pipermail/openbmc/attachments/20200611/7a7b6a61/attachment-0009.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image005.png
Type: image/png
Size: 577 bytes
Desc: image005.png
URL: <http://lists.ozlabs.org/pipermail/openbmc/attachments/20200611/7a7b6a61/attachment-0010.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image006.png
Type: image/png
Size: 562 bytes
Desc: image006.png
URL: <http://lists.ozlabs.org/pipermail/openbmc/attachments/20200611/7a7b6a61/attachment-0011.png>


More information about the openbmc mailing list