Re: The future of i486 arch in Th

2014-12-30 Thread Tomasz Pala
On Tue, Dec 30, 2014 at 20:22:01 +0100, Jan Rękorajski wrote: > If we have i686 arch we need to support i686 CPUs, not a random subset. We don't "need" to do anything. SSE2 is 13 years old now (and available for 11 years in AMD), I haven't seen unsupported CPUs in years. Hardware produced in tha

Re: PostgreSQL and uuid-ossp

2014-12-30 Thread Jan Rękorajski
On Mon, 29 Dec 2014, Andrzej Zawadzki wrote: > Hi! > > I need help: what configure option should I use according to: > www.postgresql.org/docs/9.4/static/uuid-ossp.html > > > With --with-uuid=ossp > > configure: WARNING: uuid.h: accepted by the compiler, rejected by the > preprocessor! > con

Re: The future of i486 arch in Th

2014-12-30 Thread Jan Rękorajski
On Tue, 30 Dec 2014, Tomasz Pala wrote: > +1 to abandoning i486 in current state (keeping last packages on FTP). > > On Mon, Dec 15, 2014 at 21:48:03 +0100, Jan Rękorajski wrote: > > >> Specifically: > >>Can RPM assume sse2 instructions and optimize digests/crypto to use > >> sse2? > > > >

Re: The future of i486 arch in Th

2014-12-30 Thread Tomasz Pala
+1 to abandoning i486 in current state (keeping last packages on FTP). On Mon, Dec 15, 2014 at 21:48:03 +0100, Jan Rękorajski wrote: >> Specifically: >> Can RPM assume sse2 instructions and optimize digests/crypto to use >> sse2? > > No 32bit AMD CPU has this. So, no, you can't do it uncon