Re: PHP7 issue [was PHP7 + Synth issue]

2016-02-17 Thread Jim Ohlstein
Hello, On 2/17/16 8:59 AM, John Marino wrote: On 2/17/2016 2:44 PM, Martin Wilke wrote: Hi, The long term solution will be switching to mysqli or pdo_mysql which is provided by php70 (and php55/56), I am working right now on cleaning up the pecl ports, after that I'll go and check which port

Re: PHP7 + Synth issue

2016-02-17 Thread John Marino
Matt wrote: > I'll search bugzilla to see if there are any bug reports for this and if > not I'll raise one then. > > I know php70 is very new so I was expecting problems. Synth is pretty > new as well though so I thought I would let people know in case they > were not aware of this type of

Re: PHP7 + Synth issue

2016-02-17 Thread Matt Smith
On Feb 17 15:05, Kurt Jaeger wrote: Hi! > The long term solution will be switching to mysqli or pdo_mysql which is > provided by php70 (and php55/56), I am working right now on cleaning up > the pecl ports, after that I'll go and check which port can switch already. The problem with that

Re: PHP7 + Synth issue

2016-02-17 Thread Kurt Jaeger
Hi! > > The long term solution will be switching to mysqli or pdo_mysql which is > > provided by php70 (and php55/56), I am working right now on cleaning up > > the pecl ports, after that I'll go and check which port can switch already. > The problem with that approach is that his tree is

Re: PHP7 + Synth issue

2016-02-17 Thread John Marino
On 2/17/2016 2:44 PM, Martin Wilke wrote: > Hi, > > The long term solution will be switching to mysqli or pdo_mysql which is > provided by php70 (and php55/56), I am working right now on cleaning up > the pecl ports, after that I'll go and check which port can switch already. > The problem

Re: PHP7 + Synth issue

2016-02-17 Thread Martin Wilke
Hi, The long term solution will be switching to mysqli or pdo_mysql which is provided by php70 (and php55/56), I am working right now on cleaning up the pecl ports, after that I'll go and check which port can switch already. - Martin On Wed, Feb 17, 2016 at 9:27 PM, John Marino

Re: PHP7 + Synth issue

2016-02-17 Thread John Marino
On 2/17/2016 2:24 PM, Matt Smith wrote: > The problem is that it isn't just that port. I've also seen it on > databases/mysqldumper for example. It's going to affect all ports which > have USE_PHP=mysql within them of which I suspect there are quite a > lot. It might be impractical to do what you

Re: PHP7 + Synth issue

2016-02-17 Thread Matt Smith
On Feb 17 14:16, John Marino wrote: It seems like a problem with comms/atslog to me. You can work around it now by removing MYSQL as a default option for that port (either modifying the port itself or adding something in -make.conf to change it) atslog is not maintained. Another option is

Re: PHP7 + Synth issue

2016-02-17 Thread John Marino
On 2/17/2016 2:10 PM, Matt Smith wrote: > Hi guys, I'm using the ports-mgmt/synth package builder to build my > packages. I just tried to build all of the packages for PHP7 from the > new ports and came across an issue. If I set php=7.0 in DEFAULT_VERSIONS > in the LiveSystem-make.conf

PHP7 + Synth issue

2016-02-17 Thread Matt Smith
Hi guys, I'm using the ports-mgmt/synth package builder to build my packages. I just tried to build all of the packages for PHP7 from the new ports and came across an issue. If I set php=7.0 in DEFAULT_VERSIONS in the LiveSystem-make.conf (make.conf) then Synth bails out and refuses to build