| Summary: | Wrong cryptsetup package include files location | ||
|---|---|---|---|
| Product: | buildroot | Reporter: | Jean-pierre Cartal <jpcartal> |
| Component: | Other | Assignee: | unassigned |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | buildroot |
| Priority: | P5 | ||
| Version: | 2016.08 | ||
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Host: | Target: | ||
| Build: | |||
|
Description
Jean-pierre Cartal
2017-03-02 15:45:51 UTC
*** Bug 9696 has been marked as a duplicate of this bug. *** We just need to add CRYPTSETUP_INSTALL_STAGING = YES in cryptsetup.mk. Just curious, what other package might use this header file provided by crypsetup? Thanks for your quick answer. Adding CRYPTSETUP_INSTALL_STAGING = YES does indeed solves the issue Regarding which package would use this header, it's an internal C package that uses libcryptsetup to mount encrypted partitions. I thought it might be of interest for others, but if you think that this is a corner case, I'll understand. Regards Patch submitted at https://patchwork.ozlabs.org/patch/735450/. |