[07:30:22] <jeremy_carroll_> question. How would I build PIL against mozjpeg? I tried setting JPEG_ROOT to the path where I build the .so modules for mozjpeg. It's just not respecting that path while creating _imaging.so
[16:56:07] <wiredfool> jeremy_carroll_: Not totally sure -- it's a murky part of the setup as to which of two possible matching libraries it will use if they're both found in the include/linking path.
[16:56:52] <jeremy_carroll_> wiredfool: Thanks for the response. I was playing around this morning. Found out that JPEG_ROOT really did not matter. It was using the OS ld.so.cache to find libjpeg. So basically I added mozjpeg to the ldconfig. Then it found it.
[16:57:00] <wiredfool> It's possible that you could prefix the include/link pathby using the CFLAGS and LDFLAGS environment variables, and
[17:02:27] <wiredfool> as the last question on mozjpeg was from someone who was using shared hosting and it was installed in /opt or something.
[17:02:59] <jeremy_carroll_> Yeah. Exactly. Then you would need something to add it to the path. The issue I had was even with JPEG_ROOT, the original libjpeg.so.62 was in the system path. It was being preferred over mozjpeg.
[17:03:23] <jeremy_carroll_> So when you `ldd ./build/lib.linux-x86_64-2.7/_imaging.so`, it was using the local system libjpeg provided by libtool.
[17:03:46] <jeremy_carroll_> Could not find a way around it
[17:04:01] <wiredfool> that's where LDFLAGS would come in, I think