From adfac408591ecc184e1e7599a784c1a306edeb2e Mon Sep 17 00:00:00 2001 From: DRC Date: Mon, 11 Feb 2013 03:38:53 +0000 Subject: [PATCH] Trying to build ARM v7/v7s iOS binaries from the "official" libjpeg-turbo tarball (generated on RHEL4/autoconf 2.59/automake 1.9.2/libtool 1.5.6) using either Xcode 3.2.x or 4.5.x produces an error: "libtool: compile: unable to infer tagged configuration". Further study is warranted, but the most expedient way around it at the moment is to re-run autoconf on the OS X machine that is being used to generate the iOS binaries. git-svn-id: svn+ssh://svn.code.sf.net/p/libjpeg-turbo/code/trunk@928 632fc199-4ca6-4c93-a231-07263d6284db --- BUILDING.txt | 10 ++++++++-- 1 file changed, 8 insertions(+), 2 deletions(-) diff --git a/BUILDING.txt b/BUILDING.txt index 1528fce2..1976f2bc 100644 --- a/BUILDING.txt +++ b/BUILDING.txt @@ -71,8 +71,8 @@ for 64-bit build instructions.) sh {source_directory}/configure [additional configure flags] make -NOTE: Running autoreconf in the source directory is only necessary if building -libjpeg-turbo from the SVN repository. +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/ @@ -355,6 +355,12 @@ to the configure command line. Once built, lipo can be used to combine the ARM v6, v7, and/or v7s 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 ARM v7 or v7s iOS binaries using the techniques +described above. Otherwise, you may get a libtool error such as "unable to +infer tagged configuration." + ******************************************************************************* ** Building on Windows (Visual C++ or MinGW)