On Thu, Nov 10, 2011 at 10:13:04PM +0100, Niels Thykier wrote:
[1] Strictly speaking the CFLAGS/LDFLAGS from should overrule the
upstream ones if there are conflicts. Fixing that is left as an
exercise to the reader. ;)
Can’t think of a way of doing that without patching the
On 2011-11-11 11:22, Andrea Bolognani wrote:
On Thu, Nov 10, 2011 at 10:13:04PM +0100, Niels Thykier wrote:
Hi
[...]
If you are going to send a patch upstream anyway, you might as well make
it possible to insert user *FLAGS after the upstream flags. ;)
I ended up doing just that: I’ve
On Sat, Nov 12, 2011 at 12:19:16AM +0100, Niels Thykier wrote:
I’ve also noticed that the makefile snippet exporting the hardening build
flags takes care of enabling optimization and handling
DEB_BUILD_OPTIONS=noopt itself, which is nice.
Indeed, unfortunately it comes at the price of a
On 2011-11-12 01:16, Andrea Bolognani wrote:
On Sat, Nov 12, 2011 at 12:19:16AM +0100, Niels Thykier wrote:
I’ve also noticed that the makefile snippet exporting the hardening build
flags takes care of enabling optimization and handling
DEB_BUILD_OPTIONS=noopt itself, which is nice.
On 2011-11-10 17:08, Andrea Bolognani wrote:
On Thu, Nov 10, 2011 at 12:56:57PM +0100, Niels Thykier wrote:
Hi,
As the subject suggests I am willing to sponsor the package. :)
I’m glad to hear that!
Hi,
But
before I do; have you considered enabling hardning flags in your
package?
2011/11/10 Niels Thykier ni...@thykier.net
On 2011-11-10 17:08, Andrea Bolognani wrote:
On Thu, Nov 10, 2011 at 12:56:57PM +0100, Niels Thykier wrote:
Hi,
As the subject suggests I am willing to sponsor the package. :)
I’m glad to hear that!
Hi,
But
before I do; have you
6 matches
Mail list logo
