mxnet-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Per da Silva <>
Subject libjpegturbo
Date Tue, 12 Feb 2019 07:46:30 GMT
Hello everyone,

I was wondering if there was any particular reason why we are building and
testing mxnet with USE_LIBJPEG_TURBO=0. I noticed that we are shipping it
with USE_LIBJPEG_TURBO=1 (eg. make/pip/

I ran into issues trying to compile mxnet with the libjpegturbo flag on
Ubuntu 16.04 (I was wondering if this was the reason). This came from an
issue with libturbojpeg-dev package. There is a fix described on [1]. I've
applied it in a PR, which I'm currently testing [2].




  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message