[apparmor] [patch 01/13] parser - build against in-tree libapparmor

John Johansen john.johansen at canonical.com
Tue Oct 15 00:46:30 UTC 2013


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 aren't installed, and is thus
> painful for bootstrapping in a new environment.
> 
> Instead, the parser, like pam_apparmor and mod_apparmor, should build
> against the in-tree libapparmor header and library. This patch does
> that and adjusts the tests to point LD_LIBRARY_PATH at the location
> of the built library as well.
> 
> Signed-off-by: Steve Beattie <steve at nxnw.org>

So with my previous objection dropped as a manage my own patch queue
better issue.

Acked-by: John Johansen <john.johansen at canonical.com>

But my other question still stands, do we not want libapparmor and
libstdc++ being statically linked in. And yes I realize that I uh
messed both those up and should be on the hook for the patch.




More information about the AppArmor mailing list