Re: Ports options in make.conf vs. GSSIAPI

2017-01-16 Thread Stefan Bethke
> Am 13.01.2017 um 14:12 schrieb Stefan Bethke : > > >> Am 13.01.2017 um 13:30 schrieb Stefan Bethke : >> >> For example, with dns/bind99, without options for that port in make.conf, I >> can run make showconfig and other build commands without issue. As

Re: Ports options in make.conf vs. GSSIAPI

2017-01-13 Thread Stefan Bethke
> Am 13.01.2017 um 13:30 schrieb Stefan Bethke : > > For example, with dns/bind99, without options for that port in make.conf, I > can run make showconfig and other build commands without issue. As soon as I > add either of these: > #OPTIONS_UNSET+= GSSAPI_BASE >

Re: Ports options in make.conf vs. GSSIAPI

2017-01-13 Thread Franco Fichtner
> On 13 Jan 2017, at 1:40 PM, Stefan Bethke wrote: > >> >> Am 13.01.2017 um 13:36 schrieb Franco Fichtner : >> >> Hi Stefan, >> >>> On 13 Jan 2017, at 1:30 PM, Stefan Bethke wrote: >>> >>> For example, with dns/bind99, without options

Re: Ports options in make.conf vs. GSSIAPI

2017-01-13 Thread Stefan Bethke
> Am 13.01.2017 um 13:36 schrieb Franco Fichtner : > > Hi Stefan, > >> On 13 Jan 2017, at 1:30 PM, Stefan Bethke wrote: >> >> For example, with dns/bind99, without options for that port in make.conf, I >> can run make showconfig and other build commands

Re: Ports options in make.conf vs. GSSIAPI

2017-01-13 Thread Franco Fichtner
Hi Stefan, > On 13 Jan 2017, at 1:30 PM, Stefan Bethke wrote: > > For example, with dns/bind99, without options for that port in make.conf, I > can run make showconfig and other build commands without issue. As soon as I > add either of these: > #OPTIONS_UNSET+= GSSAPI_BASE

Ports options in make.conf vs. GSSIAPI

2017-01-13 Thread Stefan Bethke
I’m having trouble selecting options for ports through make.conf. For most ports, this works fine. I have set NO_DIALOG=yes so I can run ports commands from scripts and cron without being stuck in a dialog; for those few ports where I do need custom options, I set appropriate _SET and _UNSET