Merge lp:~xnox/apparmor/bison-3.0 into lp:apparmor/2.12
Proposed by
Dimitri John Ledkov
Status: | Rejected |
---|---|
Rejected by: | Steve Beattie |
Proposed branch: | lp:~xnox/apparmor/bison-3.0 |
Merge into: | lp:apparmor/2.12 |
Diff against target: |
39 lines (+7/-5) 1 file modified
parser/libapparmor_re/parse.y (+7/-5) |
To merge this branch: | bzr merge lp:~xnox/apparmor/bison-3.0 |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Dimitri John Ledkov (community) | Disapprove | ||
AppArmor Developers | Pending | ||
Review via email: mp+200242@code.launchpad.net |
Description of the change
This is my attempt at fixing FTBFS with bison 3.x which is now in Trusty Tahr.
YYLEX_PARAM has been deprecated for a long time, but has been finally removed.
The semantics are different, as one no-longer can pass arbitrary expressions as parameter.
I've attempted to fix this, but in the process lost const qualifier, which I think is bad. Maybe someone who speaks better bison can come up with a better patch.
Also fixed %name-prefix call.
To post a comment you must log in.
Unmerged revisions
- 2294. By Dimitri John Ledkov
-
Fix FTBFS with Bison 3.0+
Thanks Dimitri - I've got a pending apparmor upload which cherry-picks the bison 3 FTBFS fix from upstream:
https:/ /launchpadlibra rian.net/ 160162431/ apparmor_ 2.8.0-0ubuntu36 .debdiff
The upload is going to be sponsored by jdstrand and it was in the process of receiving landing approval just before the holidays hit. I'm sure it'll go in early next week once everyone returns from vacation.
As a side note, I'm not familiar enough with bison to say whether or not your fix is better than what we have upstream. Maybe one of the other upstream apparmor devs can comment.