From mboxrd@z Thu Jan 1 00:00:00 1970 From: Thomas Petazzoni Subject: Re: Missing linker flags when statically linking Date: Sun, 10 Jul 2016 14:17:12 +0200 Message-ID: <20160710141712.72850dd0@free-electrons.com> References: <270aeb86-be05-03f0-0983-10e199083f56@debian.org> <11381031.WHaSpXZ8Zn@x2> <1593477.8QKBr1tzSR@x2> <8e8169d1-647f-4ff2-0003-29fe51fa8488@debian.org> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <8e8169d1-647f-4ff2-0003-29fe51fa8488@debian.org> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: linux-audit-bounces@redhat.com Errors-To: linux-audit-bounces@redhat.com To: Laurent Bigonville Cc: linux-audit@redhat.com List-Id: linux-audit@redhat.com Hello, On Sun, 10 Jul 2016 10:45:13 +0200, Laurent Bigonville wrote: > >> Also any reasons you are using Libs.private instead of Package.private? > > Libs.private is used to add flags for static linking. The dynamic linker > > shouldn't need a hint since libaudit its already linked to libcap-ng. > > I was talking about Package*.private* not package itself. > Package.private is the equivalent to Libs.private but for libs that also > have a .pc file Agreed. When possible, Package.private should be preferred over Libs.private. Thomas -- Thomas Petazzoni, CTO, Free Electrons Embedded Linux, Kernel and Android engineering http://free-electrons.com