← Back to team overview

touch-packages team mailing list archive

[Bug 1385947] Re: specifying -O to parser causes the parser to not consider cache files

 

So this is working as designed, when you explicitly override the
Optimization flags it is assumed that you will not want the old compile.

There are a couple of ways to properly fix this
1. Store the compile options used with the cache, and  compare them at the start of a compile, to determine whether or not to skip using the cache.

2. add a new flag to indicate that the implied skip cache shouldn't be
used. This is easier but some what hacky.

A third option is open to Ubuntu, to use a distro patch (I don't think
this will be taken upstream, at least not with out discussion) to remove
forcing optimization options to skip the cache. This is the easiest and
the patch to do so is attached



** Patch added: "foo.diff"
   https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1385947/+attachment/4245817/+files/foo.diff

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
https://bugs.launchpad.net/bugs/1385947

Title:
  specifying -O to parser causes the parser to not consider cache files

Status in AppArmor Linux application security framework:
  Confirmed
Status in “apparmor” package in Ubuntu:
  Confirmed
Status in “apparmor” package in Ubuntu RTM:
  Confirmed

Bug description:
  If the cache files are up to date and I specify:
  /sbin/apparmor_parser --write-cache --replace --cache-loc=/var/cache/apparmor -- profile1 profile2 ...

  then the cache files in /var/cache/apparmor are used (good).

  However, if the cache files are up to date and I specify:
  /sbin/apparmor_parser --write-cache --replace --cache-loc=/var/cache/apparmor -O no-expr-simplify -- profile1 profile2 ...

  then the cache files in /var/cache/apparmor are all regenerated (not
  good).  This needs to be fixed in order to use '-O no-expr-simplify'
  to fix bug #1383858.

To manage notifications about this bug go to:
https://bugs.launchpad.net/apparmor/+bug/1385947/+subscriptions


References