From 54014d9c2a41905b7b766057af6728834da64b59 Mon Sep 17 00:00:00 2001 From: DRC Date: Sat, 20 Jun 2015 16:27:51 +0000 Subject: [PATCH] The Linux build machine has been upgraded to autoconf 2.69, automake 1.15, m4 1.4.17, and libtool 2.4.6, so it is no longer necessary to recommend running autoreconf prior to building the source. git-svn-id: svn+ssh://svn.code.sf.net/p/libjpeg-turbo/code/trunk@1573 632fc199-4ca6-4c93-a231-07263d6284db --- BUILDING.txt | 10 ---------- 1 file changed, 10 deletions(-) diff --git a/BUILDING.txt b/BUILDING.txt index c40fc7c..485cfbe 100644 --- a/BUILDING.txt +++ b/BUILDING.txt @@ -81,14 +81,10 @@ Solaris/x86 systems (on Solaris, this generates a 32-bit library. See below for 64-bit build instructions.) cd {source_directory} - autoreconf -fiv cd {build_directory} sh {source_directory}/configure [additional configure flags] make -NOTE: Running autoreconf in the source directory is usually only necessary if -building libjpeg-turbo from the SVN repository. - This will generate the following files under .libs/ libjpeg.a @@ -422,12 +418,6 @@ the SDK. Once built, lipo can be used to combine the ARMv6, v7, v7s, and/or v8 variants into a universal library. -NOTE: If you are building libjpeg-turbo from the "official" project tarball, -then it is highly likely that you will need to run 'autoreconf -fiv' in the -source tree prior to building ARMv7, v7s, or v8 iOS binaries using the -techniques described above. Otherwise, you may get a libtool error such as -"unable to infer tagged configuration." - Building libjpeg-turbo for Android ---------------------------------- -- 2.40.0