LibTiff Mailing List
TIFF and LibTiff Mailing List Archive
July 2012
Previous Thread
Next Thread
Previous by Thread
Next by Thread
Previous by Date
Next by Date
Contact
The TIFF Mailing List Homepage
This list is run by Frank Warmerdam
Archive maintained by AWare Systems
Thread
2012.07.05 14:32 "Re: cross compile libtiff", by Bob Friesenhahn
On Thu, 5 Jul 2012, K D wrote: > > I read the Autoconf doc you suggested and rerun configure and make as > this: > > $ ./configure --build=microblaze-unknown-linux-gnu > --host=i686-pc-linux-gnu I don't think that --build should/needs to be specified. > And by reading build.log file, I don't see any > microblaze-unknown-linux-gnu tool is called. I guess I still didn't use > ./configure options > correctly. > > Also from config.log, I find this line: > configure:3076: WARNING: using cross tools not prefixed with host triplet > > Is it causing the problem? If yes, how should I correct it? I think that the target architecture needs to be specified via --host and that the tools are then expected to be prefixed by that target architecture name. There is no need to specify the host architecture used to execute the build. For example, if you specified --host=ppc-unknown-linux-gnu then your tools would be named similar to ppc-unknown-linux-gnu-gcc If your tools are not named this way, you can add symbolic links so that they are accessible using the names that Autoconf looks for. All of the tools (e.g. as, ar, ld, objdump, cc) should use the same architecture prefix in their name. The config.log file should show that Autoconf is searching for (and finding) the tools you want it to use. Bob -- Bob Friesenhahn bfriesen@simple.dallas.tx.us, http://www.simplesystems.org/users/bfriesen/ GraphicsMagick Maintainer, http://www.GraphicsMagick.org/