On Thu, Jun 30, 2016 at 08:46:54PM +0100, Simon McVittie wrote:
> On Thu, 30 Jun 2016 at 16:31:43 +0100, Jose M Calhariz wrote:
> > On Thu, Jun 30, 2016 at 02:59:39PM +, Niels Thykier wrote:
> > > Please verify that the CPPFLAGS are passed to the compiler (a lot of
> > > build systems fail to p
On Thu, 30 Jun 2016 at 16:31:43 +0100, Jose M Calhariz wrote:
> On Thu, Jun 30, 2016 at 02:59:39PM +, Niels Thykier wrote:
> > Please verify that the CPPFLAGS are passed to the compiler (a lot of
> > build systems fail to pass exactly CPPFLAGS on).
What Niels said. This appears to be exactly t
On Thu, Jun 30, 2016 at 02:59:39PM +, Niels Thykier wrote:
> Jose M Calhariz:
> > Hi,
> >
> > I am investigating why I can turn off the lintian information
> > hardening-no-fortify-functions. In the beginning of my debian/rules I
> > have:
> >
> > export DEB_BUILD_MAINT_OPTIONS=hardening=+al
Jose M Calhariz:
> Hi,
>
> I am investigating why I can turn off the lintian information
> hardening-no-fortify-functions. In the beginning of my debian/rules I
> have:
>
> export DEB_BUILD_MAINT_OPTIONS=hardening=+all
>
> What I am doing wrong?
> How can I debug if the hardening is really on t
Hi,
I am investigating why I can turn off the lintian information
hardening-no-fortify-functions. In the beginning of my debian/rules I
have:
export DEB_BUILD_MAINT_OPTIONS=hardening=+all
What I am doing wrong?
How can I debug if the hardening is really on the binaries?
The complete lintian me
5 matches
Mail list logo
