On 12/21/2018 02:55 PM, Ken Moffat via blfs-dev wrote:
On Thu, Dec 20, 2018 at 11:41:19PM -0600, Bruce Dubbs via blfs-dev wrote:
On 12/20/2018 10:29 PM, Xi Ruoyao via blfs-dev wrote:
On 2018-12-20 10:45 -0600, Bruce Dubbs via blfs-dev wrote:
On 12/20/2018 06:44 AM, Xi Ruoyao via blfs-dev wrote:
So upstream says it is false by default. I suppose it is for backward
compatibility. I think for now we should leave it out until we get a
package that complains.
But we *were* using the non-default --with-jpeg8 back in the old autoconf
times (before r20329). Before r10952 BLFS actually used libjpeg v8d. So
I think we should kept using v8 ABI.
I understand we were using it, but where is it being used now?
Maybe I've misunderstood your question, but everything which uses
(system) libjpeg uses it. And we didn't have issues in recent times
when that was v8. ISTR I had a local issue in firefox when v8 first
came out, but that was years ago.
My question is: If we do not use --with-jpeg8 (or equivalent), what breaks?
-- Bruce
--
http://lists.linuxfromscratch.org/listinfo/blfs-dev
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
