autoconf

I am having trouble cross-compiling a library for my arm board using autconf. I am using this line: ./configure --target=arm-linux --host=arm-linux --prefix=/bla/bla/bla/linux_arm_tool CFLAGS='-m32' make make install When I do file to check it I get: libjpeg.so.8.4.0: ELF 32-bit LSB shared object, Intel 80386, version 1 (SYSV), dynamically linked, not stripped That doesn't seem right at all, but I tried using it anyway... and I get: /usr/lib/gcc/arm-linux-gnueabi/4.5.3/../../../../arm-linux-gnueabi/bin/ld: skipping incompatible /bla/bla/bla/bla/../linux_arm_tool/lib/libjpeg.so when searching

General question: If I use a cross compiler, how can I tell the value of the "--host" option I should give when I run configure? Specific: I'm using cross compiler for arm64 arch. What is the correct "--host" value to use? vinay hunachyal If I use a cross compiler, how can I tell the value of the --host option I should give when I run ./configure ? Three machines must be distinguished when discussing toolchain creation The build machine , where the toolchain is built. The host machine , where the toolchain will be executed. The target machine , where the binaries created by the toolchain are

The project that I am trying to build has default flags CFLAGS = -Wall -g -O2 CXXFLAGS = -g -O2 I need to append a flag -w to both these variables (to remove: 'consider all warnings as errors') I have a method to work it out, give make 'CFLAGS=-Wall -g -O2 -w'; 'CXXFLAGS=-g -O2 -w' OR Run ./configure and statically modify Makefile But I want to append my options with the existing options while running configure or make The post Where to add a CFLAG, such as -std=gnu99, into an autotools project conveniently uses a macro to achieve this. You almost have it right; why did you add the semicolon?

I am trying to setup my machine with pecl_http and memcache and in both cases, I get similar errors. This is on MAC OS X 10.7.3 (lion) and I also have XCODE installed on it. I also installed Zend Server community edition before running these commands and have CFLAGS='-arch i386 -arch x86_64' environment variables set. So please help with what I need to do bash-3.2# **sudo pecl install pecl_http-1.7.1** downloading pecl_http-1.7.1.tgz ... Starting to download pecl_http-1.7.1.tgz (174,098 bytes) .....................................done: 174,098 bytes 71 source files, building running: phpize

I understand that CFLAGS (or CXXFLAGS for C++) are for the compiler, whereas CPPFLAGS is used by the preprocessor. But I still don't understand the difference. I need to specify an include path for a header file that is included with #include -- because #include is a preprocessor directive, is the preprocessor (CPPFLAGS) the only thing I care about? Under what circumstances do I need to give the compiler an extra include path? In general, if the preprocessor finds and includes needed header files, why does it ever need to be told about extra include directories? What use is CFLAGS at all? (In