On 10/25/2016 02:24 PM, Bipnesh, Abhinav (Abhinav) wrote:
Is there a way we can avoid pre-populating the Requires section of the generated RPM Spec from a recipe? I have not set any RDEPENDS or other such section but still the section get populated. Below is an example Requires: libcrypto.so.1.0.0(OPENSSL_1.0.2d) Requires: libdl.so.2 Requires: libuuid1 >= 2.26.2 Requires(pre): libgcc1 >= 4.9.2 Requires(pre): libssl1.0.0 >= 1.0.2h Requires(pre): libgcc_s.so.1(GCC_3.0) Requires(pre): libc.so.6(GLIBC_2.1) Requires(pre): /usr/bin/perl Requires(pre): libboost_system.so.1.58.0 Requires(pre): libstdc++.so.6(GLIBCXX_3.4.20) Requires(pre): libc.so.6(GLIBC_2.3)
You need to provide some context: why do you want to avoid that? These are all runtime library dependencies, and they get added automatically by inspecting the binaries that your recipe generates. This is generally seen as a Good Thing.
Alex -- _______________________________________________ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
