On Thu, 25 Apr 2024 at 07:52, leimaohui via lists.openembedded.org <[email protected]> wrote: > - After oe_multilib_header on cdefs.h, the path of cdefs-64.h and cdefs-32.h > in cdefs.h need to be corrected. Please reference to > https://man.archlinux.org/man/libbsd.7 for details.
I looked at this in a local build, and I actually don't think they need to be corrected. Without the sed command, there is #include <bsd/sys/cdefs-32.h>, which is fine, as it's relative to /usr/include, and unambigious. After the sed command, there is #include <sys/cdefs-32.h> which requires special non-default arrangements in the build system, specifically, using libbsd in overlay mode with special compiler flags as described in the man page you refer to. But that's not the only way to use libbsd, and the other way won't work. So what is the issue that happens if there is no sed, and only oe_multilib_header? Alex
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#198696): https://lists.openembedded.org/g/openembedded-core/message/198696 Mute This Topic: https://lists.openembedded.org/mt/105725841/21656 Group Owner: [email protected] Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
