Re: jpeg-turbo 6.2 and ppc G3

2016-07-07 Thread Riccardo Mottola
Hi, Lennart Sorensen wrote: On Thu, Jul 07, 2016 at 01:43:12PM +0200, Gabriel Paubert wrote: >You don't always configure/compile on the machine you run. Especially >the people who build distributions. True, but you would still be configuring and compiling against the target libc, so configure

Transporte de Carga - Alquiler de Maquinaria de Construcción y Grúas

2016-07-07 Thread Logisven - Coordinación Logística y Alquiler de Grúas
  estimados srs.  queremos presentarle nuestra organización y tener la posibilidad de convertirnos en proveedores de logística de su empresa. nuestros principales servicios son: coordinación logística a nivel nacional e internacional coordinación de carga suelta en gandolas contenedo

Re: jpeg-turbo 6.2 and ppc G3

2016-07-07 Thread Lennart Sorensen
On Thu, Jul 07, 2016 at 01:43:12PM +0200, Gabriel Paubert wrote: > You don't always configure/compile on the machine you run. Especially > the people who build distributions. True, but you would still be configuring and compiling against the target libc, so configure would do the right thing. --

Re: jpeg-turbo 6.2 and ppc G3

2016-07-07 Thread Lennart Sorensen
On Thu, Jul 07, 2016 at 10:52:01AM +0200, Riccardo Mottola wrote: > I wonder if you can have different cores? e.g. how is a Cell processor seen > in cpuinfo? Just out of curiosity. I don't think it is, since it needs special handling to dispatch jobs. As long as any core in cpuinfo has altivec, it

Re: jpeg-turbo 6.2 and ppc G3

2016-07-07 Thread Riccardo Mottola
Hi, Gabriel Paubert wrote: Anyway, I think the best of two worlds would be to use getauxval() >when available (most probably any currently supported OS) and fall >back to cpuinfo if not. A configure test I suppose is quite simple. You don't always configure/compile on the machine you run. Espec

Re: jpeg-turbo 6.2 and ppc G3

2016-07-07 Thread Gabriel Paubert
On Thu, Jul 07, 2016 at 10:52:01AM +0200, Riccardo Mottola wrote: > Hi, > > Gabriel Paubert wrote: > >>That is garbage in my opinion, given there exists a proper interface > >>>for getting that info. > >Seconded, getauxval (not getauxvec!) is simpler, officially supported > >for a long time, and w

Re: jpeg-turbo 6.2 and ppc G3

2016-07-07 Thread Riccardo Mottola
Hi, Gabriel Paubert wrote: That is garbage in my opinion, given there exists a proper interface >for getting that info. Seconded, getauxval (not getauxvec!) is simpler, officially supported for a long time, and while the intent is not to modify the format of /proc/cpuinfo in a way that would br

Re: jpeg-turbo 6.2 and ppc G3

2016-07-07 Thread Gabriel Paubert
On Wed, Jul 06, 2016 at 04:54:01PM -0400, Lennart Sorensen wrote: > On Wed, Jul 06, 2016 at 09:54:02PM +0200, Riccardo Mottola wrote: > > "upstream" replied with this: > > > > https://github.com/libjpeg-turbo/libjpeg-turbo/commit/6c0b7613b4d48dd35e54fc968f4a808d495f2fef > > That is garbage in my