On Mon, Sep 18, 2017 at 12:30 PM, Mark Hatle <[email protected]> wrote: > > Because of this, there is no way (with a default configuration) to build > meta-toolchain.... > > Investigating further, ldconfig support moved from "USE_LDCONFIG" to a > distribution configuration. It does this via the "DISTRO_FEATURES_BACKFILL" > (introduced in commit: a905df2dd8f43a2febffa64a39b6e508510326a0)
The intention of that commit was only to change the way support for running ldconfig on the target is controlled (ie changed from an ad-hoc bitbake variable to a distro config option). It's enabled by default now, but it was enabled by default before that commit as well. Did meta-toolchain work previously? If so, was USE_LDCONFIG being forced to 0 somewhere? > If I add to my configuration: > > DISTRO_FEATURES_BACKFILL_CONSIDERED_append = " ldconfig" > > This works around the issue... but doesn't resolve the default issue.... > > So my question is, is this behavior (the failure case) really acceptable > without > telling the user what is happening? Or do we need to add something to the > system that says meta-toolchain can't be used with this DISTRO_FEATURE? or... > > --Mark > -- -- _______________________________________________ Openembedded-core mailing list [email protected] http://lists.openembedded.org/mailman/listinfo/openembedded-core
