| Summary: | [Bitbake : 2.4.3RC2] Bitbake Devshell is failed in x86_64 | ||
|---|---|---|---|
| Product: | [Build System, Metadata & Runtime] BitBake | Reporter: | pankaj yadav <pankaj-y> |
| Component: | bitbake | Assignee: | Joshua Watt <JPEWhacker> |
| Status: | RESOLVED NOTABUG | QA Contact: | |
| Severity: | normal | ||
| Priority: | Medium | CC: | poky.bs.watcher, poky.watcher, randy.macleod |
| Version: | 2.4.3 | ||
| Target Milestone: | 2.6 | ||
| Hardware: | x86 | ||
| OS: | Multiple | ||
| Whiteboard: | |||
| OS type for building Yocto: | --- | Type of Regression: | --- |
| Verified: | Documentation change: | No (bug/feature does not impact docs) | |
|
Description
pankaj yadav
2018-06-04 09:10:30 UTC
It is unlikely that a simple './configure' step is going to be successful in devshell. It should be possible to run the configure step in devshell, but you will likely need some additional command line arguments. Particularly, I'm guessing you need additional arguments like --build, --host and --target to instruct autotools that you mean to cross compile. You should be able to determine what additional arguments are passed to by looking at the recipe environment using "bitbake -e". The two variables of interest are CONFIGUREOPTS and EXTRA_OECONF. Both of these are passed to the configure script. You can see more detailed information by looking in meta/classes/autotools.bbclass, more specifically at the oe_runconf() function |