Hi, I get the same problem here with LLVM/Clang trunk.
LLVM API tends to change in the LLVM SVN trunk. So LanguageKit needs to be updated to build again against the new API (and the old API too). That's why we usually suggest to use LLVM/Clang release rather than trunk. Cheers, Quentin. Le 20 nov. 2012 à 17:00, Maxthon Chan a écrit : > I got a compile failure like this - huh?! > > Build Project: LanguageKitCodeGen > > Making all for framework LanguageKitCodeGen... > Compiling file AMD64/AMD64ABIInfo.mm ... > AMD64/AMD64ABIInfo.mm:650:36: error: too few arguments to function call, > expected 2, have 1 > return AttrListPtr::get(attributes); > ~~~~~~~~~~~~~~~~ ^ > /usr/include/llvm/Attributes.h:334:3: note: 'get' declared here > static AttrListPtr get(LLVMContext &C, ArrayRef<AttributeWithIndex> Attrs); > ^ > 1 error generated. > make[5]: *** [obj/LanguageKitCodeGen.obj/AMD64/AMD64ABIInfo.mm.o] Error 1 > make[4]: *** [internal-framework-run-compile-submake] Error 2 > make[3]: *** [LanguageKitCodeGen.all.framework.variables] Error 2 > make[2]: *** [internal-all] Error 2 > make[1]: *** [internal-all] Error 2 > make: *** [internal-all] Error 2 > > clang and GNUstep are both the latest development version just checked out > from svn an hour ago, and clang is bootstrapped "properly" using an older > version of clang. > _______________________________________________ > Etoile-discuss mailing list > [email protected] > https://mail.gna.org/listinfo/etoile-discuss _______________________________________________ Etoile-discuss mailing list [email protected] https://mail.gna.org/listinfo/etoile-discuss
