On 10 June 2014 15:30, Paul Eggleton <paul.eggle...@linux.intel.com> wrote: > Hi Patrick, > > On Tuesday 10 June 2014 10:23:04 Patrick Doyle wrote: >> I started getting the warning mentioned above when I updated to a >> newer release of an open source package (Aravis). I asked the google >> how I should address that issue, and it was no help, so now I'll ask >> the list :-) >> >> Any suggestions as to what I should do about this? The (autotools >> generated) Makefiles do, in fact, generate symlinks. Do I care? > > FYI there's a new section in the work-in-progress manual for 1.7 which > documents QA warnings including this one:
One situation that happens disappointingly often and causes problems is when people build runtime loadable modules but don't use the right libtool flags. These look like libraries and have a .so extension, but without the right flags they'll be installed with versions and .so symlinks, all of which are pointless and the .so symlinks are required in the main package. If this is the situation you can either package the symlinks in the right place and silence the warning with INSANE_SKIP, or fix the build system (http://www.gnu.org/software/libtool/manual/html_node/Building-modules.html should help). Ross -- _______________________________________________ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
