perl-bignum package is required to build core-image-minimal with qemux86 machine but is not a required package in quick start guide. Host OS is Fedora23 64 bit. Expected behavior ------------------ Follow quick start guide and image builds. Observed behavior ----------------- Follow quick start guide and build fails as follows ERROR: The perl module 'bignum' was not found but this is required to build openssl. Please install this module (often packaged as perl-bignum) and re-run bitbake.
The Fedora package list in the 2.1 quick start guide already include perl-bignum - were you perhaps looking at the "current" manual link before that got updated (just yesterday, a bit later than it should have been)?
I was looking at http://www.yoctoproject.org/docs/2.0.1/yocto-project-qs/yocto-project-qs.html, thus the 2.0.x version tag. There is not 2.0.1 tag, but I guess that's a different defect :-)
As I recall this package only appeared in F23 and F23 wasn't supported by 2.0 - Ross is that right?
(Though one would assume we would look to support it in the next 2.0 point release, so I'm not really questioning the validity of the report)
Yeah its a F23 specific package from what I can remember.
Scott, can we add a note to the 2.0 documentation? Something along the lines that the 2.0 isn't supported under F23 but if you want to use it then the user has to install perl-bignum too.
Ross and Paul, I am not quite sure where we are in the latest 2.0.x release. I have a 2.0.2 version of the manuals and I placed this note here about not supporting F23 and if you want to use it you need that package. It is a pain in the ass but I could fix the 2.0 and 2.0.1 versions of the QS to have the note as well. However, only the HTML version on the YP site would have the fix. I can't do a commit since 2.0, 2.0.1, and 2.0.2 are all on the same 'jethro' branch. Is that good enough? Here is the new note: http://www.yoctoproject.org/docs/2.0.2/yocto-project-qs/yocto-project-qs.html#packages Scott
Please review this change and let me know if we can RESOLVE it in the status. Thanks, Scott
this aspect at least is RESOLVED
Tim, Thanks - I set the doc flag to "done." Scott