search for: iquote

...cpp normal i386 c++ com.apple.compilers.gcc.4_0 cd llvm /Developer/usr/bin/gcc-4.0 -x c++ -arch i386 -fmessage-length=0 - pipe -Wno-trigraphs -fpascal-strings -fasm-blocks -O0 -isysroot / Developer/SDKs/MacOSX10.4u.sdk -fvisibility-inlines-hidden -mmacosx- version-min=10.4 -gdwarf-2 -iquote /build/codegen.build/codegen- generated-files.hmap -I/llvm/build/codegen.build/codegen-own-target- headers.hmap -I/codegen.build/codegen-all-target-headers.hmap -iquote / build/codegen.build/codegen-project-headers.hmap -Wmost -Wno-four-char- constants -Wno-unknown-pragmas -F/build/Development...

...om.apple.compilers.gcc.4_0 > cd llvm > /Developer/usr/bin/gcc-4.0 -x c++ -arch i386 -fmessage-length=0 - > pipe -Wno-trigraphs -fpascal-strings -fasm-blocks -O0 -isysroot / > Developer/SDKs/MacOSX10.4u.sdk -fvisibility-inlines-hidden -mmacosx- > version-min=10.4 -gdwarf-2 -iquote /build/codegen.build/codegen- > generated-files.hmap -I/llvm/build/codegen.build/codegen-own-target- > headers.hmap -I/codegen.build/codegen-all-target-headers.hmap - > iquote /build/codegen.build/codegen-project-headers.hmap -Wmost -Wno- > four-char-constants -Wno-unknown-pragmas -...

Hi, For the record, adding UNIVERSAL_SDK_PATH=/Developer/SDKs/MacOSX10.4u.sdk/ was insufficient to restrict the .a/.o files to link against the 10.4 sdk, but env MACOSX_DEPLOYMENT_TARGET=10.4 make did the trick. Thanks! On Jan 14, 2009, at 1:29 PM, Jean-Daniel Dupas wrote: > > Le 14 janv. 09 à 21:48, Chris Lattner a écrit : > >> >> On Jan 14, 2009, at 12:44 PM,

Le 14 janv. 09 à 21:48, Chris Lattner a écrit : > > On Jan 14, 2009, at 12:44 PM, Graham Wakefield wrote: > >> Sorry if this is a newb q... I'm developing an application on a >> 10.5 machine but want to target the 10.4 SDK. Is there a magic >> incantation for the llvm configure script to set the sysroot path, >> equivalent to e.g. --with-sysroot

...clude each other's headers using <>! I'm not sure how much you care about ms compiler, but it will look in system path for angle bracket includes. There was some problem with gcc and in late version they changed that behavior as well to be able specify system include search path and -iquote search path. (and I believe that change originated from that issue that Symbian's port of gcc had!) http://gcc.gnu.org/onlinedocs/cpp/Search-Path.html : "For example, if /usr/include/sys/stat.h contains #include "types.h", GCC looks for types.h first in /usr/include/sys, then i...

I'm just curious, who and why came up with that strange way to write includes: #ifdef _BUILD_SPEEX # include "speex_types.h" #else # include <speex/speex_types.h> #endif I personally consider it a bug. If I use speex then obviously I should not have _BUILD_SPEEX defined. The broken behavior happens in this simple scenario: 1) I check out latest git version to ./src/speex 2)