| Summary: | libtool library files broken | ||
|---|---|---|---|
| Product: | [Build System, Metadata & Runtime] OE-Core | Reporter: | Wolfgang Denk <wd> |
| Component: | devtools / tool chain | Assignee: | Nitin Kamble <nitin.a.kamble> |
| Status: | RESOLVED NOTABUG | QA Contact: | |
| Severity: | major | ||
| Priority: | Undecided | CC: | agust, jessica.zhang, mark.hatle, meta.mr.watcher, meta.watcher |
| Version: | 1.2 | ||
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | Multiple | ||
| Whiteboard: | |||
| OS type for building Yocto: | --- | Type of Regression: | --- |
| Verified: | Documentation change: | --- | |
|
Description
Wolfgang Denk
2012-04-19 10:23:46 UTC
The libtool archive files themselves appear to be correct based on your grep. Something is wrong with the libtool on the target. The "=" syntax is correct, the target libtool for some reason is not evaluating it. Two possibilities come to mind. The first is you are compiling something on the target that included libtool preinstalled. If that is the case, you need to run libtoolize --copy --force to ensure that the correct version of libtool is used. The other option is that libtool on the target only evaluates the "=" syntax when a --sysroot is passed? If so, it seems like it would be reasonable to set it to "/" if no --sysroot= is set. Please look at Mark's comments regarding running libtoolize. We expect people to use libtool that support sysroot. The source package didn't contain libtool preinstalled, but ltmain.sh, so the generated libtool didn't evaluate this "=" syntax. Running autoreconf --force --install (which runs 'libtoolize --copy --force' among other things) fixes the issue. Thanks! |