Re: Default compilation flags for binary pkgs

To: Swift Griggs <swiftgriggs%gmail.com@localhost>
Subject: Re: Default compilation flags for binary pkgs
From: coypu%sdf.org@localhost
Date: Mon, 7 Aug 2017 22:38:07 +0000

On Mon, Aug 07, 2017 at 03:28:00PM -0600, Swift Griggs wrote:
> 
> Are these on for the pkgsrc build servers? Ie.. will my stuff fetched via
> pkgin have these protections?
> 
> PKGSRC_USE_SSP=yes
> PKGSRC_USE_FORTIFY=yes
> 
> I'm just curious.

They were made the default on pkgsrc-current after the pkgsrc-2017Q2
branch. If you are referring to netbsd pkgsrc packages, they are usually
of the stable branch and do not include them yet. 2017Q3 will.

We are using a per-OS whitelist, grep -R OPSYS_SUPPORTS_ pkgsrc/mk/platform

References:
- Default compilation flags for binary pkgs
  - From: Swift Griggs

Prev by Date: Default compilation flags for binary pkgs
Next by Date: Re: __stack_chk_fail_local pkgsrc with gcc4.8 (was Re: minimum gcc to compile pkgsrc?
Previous by Thread: Default compilation flags for binary pkgs
Indexes:

Home | Main Index | Thread Index | Old Index