On 10/15/2013 11:50 AM, Steve Beattie wrote:
> On Tue, Oct 15, 2013 at 09:12:26AM -0700, John Johansen wrote:
>>> There are two ways that I can see to link libapparmor in statically,
>>> while not linking the entire binary statically:
>>>
>>> - link directly against ../library/libapparmor/src/.li
On Tue, Oct 15, 2013 at 09:12:26AM -0700, John Johansen wrote:
> > There are two ways that I can see to link libapparmor in statically,
> > while not linking the entire binary statically:
> >
> > - link directly against ../library/libapparmor/src/.libs/libapparmor.a
> > - play some loader game
On 10/15/2013 08:20 AM, Steve Beattie wrote:
> On Mon, Oct 14, 2013 at 06:35:39PM -0700, John Johansen wrote:
>> On 10/14/2013 05:46 PM, John Johansen wrote:
>>> On 10/10/2013 01:46 PM, Steve Beattie wrote:
With trunk commit 2205 "use libapparmor's find mountpoint fn",
the parser now buil
On Mon, Oct 14, 2013 at 06:35:39PM -0700, John Johansen wrote:
> On 10/14/2013 05:46 PM, John Johansen wrote:
> > On 10/10/2013 01:46 PM, Steve Beattie wrote:
> >> With trunk commit 2205 "use libapparmor's find mountpoint fn",
> >> the parser now builds against and uses libapparmor at runtime. Howe
On 10/14/2013 05:46 PM, John Johansen wrote:
> On 10/10/2013 01:46 PM, Steve Beattie wrote:
>> With trunk commit 2205 "use libapparmor's find mountpoint fn",
>> the parser now builds against and uses libapparmor at runtime. However,
>> it currently builds against the system installed libapparmor li
On 10/10/2013 01:46 PM, Steve Beattie wrote:
> With trunk commit 2205 "use libapparmor's find mountpoint fn",
> the parser now builds against and uses libapparmor at runtime. However,
> it currently builds against the system installed libapparmor library and
> header files, which fails if either ar
On 10/11/2013 06:34 PM, John Johansen wrote:
> On 10/10/2013 06:25 PM, Steve Beattie wrote:
>> On Thu, Oct 10, 2013 at 03:33:19PM -0700, John Johansen wrote:
>>> On 10/10/2013 01:46 PM, Steve Beattie wrote:
With trunk commit 2205 "use libapparmor's find mountpoint fn",
the parser now buil
On 10/10/2013 06:25 PM, Steve Beattie wrote:
> On Thu, Oct 10, 2013 at 03:33:19PM -0700, John Johansen wrote:
>> On 10/10/2013 01:46 PM, Steve Beattie wrote:
>>> With trunk commit 2205 "use libapparmor's find mountpoint fn",
>>> the parser now builds against and uses libapparmor at runtime. However
On Thu, Oct 10, 2013 at 03:33:19PM -0700, John Johansen wrote:
> On 10/10/2013 01:46 PM, Steve Beattie wrote:
> > With trunk commit 2205 "use libapparmor's find mountpoint fn",
> > the parser now builds against and uses libapparmor at runtime. However,
> > it currently builds against the system ins
On 10/10/2013 01:46 PM, Steve Beattie wrote:
> With trunk commit 2205 "use libapparmor's find mountpoint fn",
> the parser now builds against and uses libapparmor at runtime. However,
> it currently builds against the system installed libapparmor library and
> header files, which fails if either ar
With trunk commit 2205 "use libapparmor's find mountpoint fn",
the parser now builds against and uses libapparmor at runtime. However,
it currently builds against the system installed libapparmor library and
header files, which fails if either aren't installed, and is thus
painful for bootstrapping
11 matches
Mail list logo
