On 2020/05/16 7:51, Mike Hommey wrote:
On Sat, May 16, 2020 at 07:24:44AM +0900, ISHIKAWA,chiaki wrote:
I have --disable-libjpeg-turbo in my mozconfig for many years (I build TB
locally).
After an update of the local source tree this morning, it is no longer
recognized?
(The last update was several days ago.)
Has anyone also experienced this?
Traceback (most recent call last):
File "/NEW-SSD/NREF-COMM-CENTRAL/mozilla/configure.py", line 181, in
<module>
sys.exit(main(sys.argv))
File "/NEW-SSD/NREF-COMM-CENTRAL/mozilla/configure.py", line 52, in main
sandbox.run(os.path.join(os.path.dirname(__file__), 'moz.configure'))
File
"/NEW-SSD/NREF-COMM-CENTRAL/mozilla/python/mozbuild/mozbuild/configure/__init__.py",
line 494, in run
raise InvalidOptionError(msg)
mozbuild.configure.options.InvalidOptionError: Unknown option:
--disable-libjpeg-turbo
*** Fix above errors and then restart with\
"./mach build"
make: *** [client.mk:115: configure] Error 1
I removed it in bug 1638195, but it hasn't done anything since bug
1515852.
Mike
Thank you for the pointer.
Does this mean I can safely remove --disable-libjpeg-turbo?
[I am not sure why I have this. It has been there for years, and I
forgot about it.
Possibly YASM dependency issues mentioned in the bug under Debian
GNU/Linux.]
Or should I say explicitly --with-system-jpeg in mozconfig?
TIA
_______________________________________________
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
