Re: update print/poppler, please hit me with the cluestick

2017-03-23 Thread Matthias Kilian
Hi, On Wed, Mar 22, 2017 at 11:57:12PM +0100, Jeremie Courreges-Anglas wrote: > > the newest poppler uses --std=c++11 even for the base libpoppler, > > so I tried to set MODULES+=gcc4 and MODGCC_LANGS=c++ (see diff > > below). However, it still just uses c++, and lang/gcc/4.9 doesn't > > even sho

Re: update print/poppler, please hit me with the cluestick

2017-03-22 Thread Jeremie Courreges-Anglas
Matthias Kilian writes: > Hi, > > the newest poppler uses --std=c++11 even for the base libpoppler, > so I tried to set MODULES+=gcc4 and MODGCC_LANGS=c++ (see diff > below). However, it still just uses c++, and lang/gcc/4.9 doesn't > even show up in make show=BUILD_DEPENDS or make dump-vars. >

Re: update print/poppler, please hit me with the cluestick

2017-03-22 Thread Antoine Jacoutot
On March 22, 2017 11:04:56 PM GMT+01:00, Matthias Kilian wrote: >Hi, > >the newest poppler uses --std=c++11 even for the base libpoppler, >so I tried to set MODULES+=gcc4 and MODGCC_LANGS=c++ (see diff >below). However, it still just uses c++, and lang/gcc/4.9 doesn't >even show up in make show=

update print/poppler, please hit me with the cluestick

2017-03-22 Thread Matthias Kilian
Hi, the newest poppler uses --std=c++11 even for the base libpoppler, so I tried to set MODULES+=gcc4 and MODGCC_LANGS=c++ (see diff below). However, it still just uses c++, and lang/gcc/4.9 doesn't even show up in make show=BUILD_DEPENDS or make dump-vars. Probably a stupid PEBKAC. Any ideas?