With the current order of external libraries in the kraft.yaml file, the app won't build because _LIBCPP_BEGIN_NAMESPACE_STD is not defined. This is caused because plat/kvm/x86/time.c includes stdlib.h and since libcxx is placed before musl, the header is included from libcxx's origin code. This causes a problem because, when trying to compile time.c source, it will use the stdlib.h header from libcxx and not define the macro. Later on, when trying to parse the next header file that uses that define, it will stop the build process.
This PR reorders the external libraries in the correct order.
With the current order of external libraries in the
kraft.yamlfile, the app won't build because_LIBCPP_BEGIN_NAMESPACE_STDis not defined. This is caused becauseplat/kvm/x86/time.cincludesstdlib.hand sincelibcxxis placed beforemusl, the header is included from libcxx's origin code. This causes a problem because, when trying to compiletime.csource, it will use thestdlib.hheader fromlibcxxand not define the macro. Later on, when trying to parse the next header file that uses that define, it will stop the build process. This PR reorders the external libraries in the correct order.Signed-off-by: Florin Postolache florin.postolache80@gmail.com