Merge ~dbungert/casper:frame-pointer into casper:main
Proposed by
Dan Bungert
| Status: | Merged |
|---|---|
| Merged at revision: | ceeae71bbcddf2f3a4a142b6a09a47b46c15880f |
| Proposed branch: | ~dbungert/casper:frame-pointer |
| Merge into: | casper:main |
| Diff against target: |
48 lines (+15/-1) 3 files modified
casper-md5check/Makefile (+4/-1) debian/changelog (+6/-0) debian/rules (+5/-0) |
| Related bugs: |
| Reviewer | Review Type | Date Requested | Status |
|---|---|---|---|
| Steve Langasek | Approve | ||
|
Review via email:
|
|||
Commit message
md5check: use dpkg buildflags.mk
The driving force on this change is to pick up frame pointer support.
Using dpkg-buildflags to automatically pick up future interesting
changes.
Also intentionally drops -g -O2, as we should be getting reasonable
values there from buildflags.
To post a comment you must log in.

Ok yes, sorry, some of the variables being set here are things like 'CFLAGS', which would not be exported by dpkg-buildpackage but are expected to be picked up in a manner specific to the upstream build system in use by dh (or debian/rules more generally).
So there's probably another way to do this by permuting dh to know what build system to use that would cause it to automatically export the flags variables, rather than having to list them explicitly in debian/rules; but this is enough to be getting on with.