Le 23 juil. 2011 à 15:36, Ryan Harter a écrit : > Hey Quentin, > > On Jul 23, 2011 8:10 AM, "Quentin Mathé" <qma...@gmail.com> wrote: > > > > Hi Ryan, > > > > Le 22 juil. 2011 à 20:55, Ryan Harter a écrit : > > > > > Thanks David- > > > > > > Running clang -v gets me the following. I did check out the trunk, > > > following the directions on the Etoile website. > > > > > > ryan@localhost ~/Etoile $ clang -v > > > clang version 3.0 (trunk 135766) > > > Target: x86_64-unknown-linux-gnu > > > Thread model: posix > > > > > > When I change the line in NSObject+Trait.m to move the @synthesize above > > > the load method the class compiles properly, > > > > It's quite possible that this warning is bogus because of recent changes in > > Clang. Over the past years, I observed several times that Clang trunk was > > reporting weird or unknown warnings, and these disappeared If I updated my > > Clang working copy in the next days or weeks. > > I usually comment out the ERROR_FLAG in etoile.make to work around such > > temporary issues. > > I'll comment out that flag and see what happens.
I just moved @synthesize to come first and eliminates the warning. See r7121 Thanks for reporting the issue. > > > but then I get a ton of errors in LanguageKit. I can't imagine there are > > > this many errors in the trunk so I must be doing something wrong. > > > > It's possible that LanguageKit is currently broken with LLVM trunk. > > > > I did a Étoilé repository build from scratch with LLVM+Clang 2.9 today on > > Ubuntu x86 (32 bits), and everything went smoothly. I'm building LLVM/Clang > > trunk currently… I'll let you know about the results. > > I'm out of town for the weekend but when I get home I'll try building with > 2.9 and see if I can't get it going. Im assuming theres a 2.9 branch in the > repo, cireect? Should I still use the GNUstep trunk? > > I'm building on Gentoo x86_64, hopefully that shouldn't be an issue. If I run > into too many problems ill switch to Ubuntu and see if I can just get the > standard build going. LanguageKit is indeed broken with recent LLVM trunk, looks like LLVM devs have removed the 'const' qualifier in various functions that were taking 'const llvm::Type' previously. A possible workaround is to define at the top of LLVMCompat.h (in LanguageKit/CodeGen): #if LLVM_MAJOR < 3 #define LLVMType const llvm::Type #else #define LLVMType llvm::Type #endif However I have no idea if all the API has been changed or only some parts. So I'm unsure if it's the best solution, and if a global search/replace would work. The trouble is that const llvm::Type is used in many declarations in LanguageKit (hence we get a lot of warnings). Cheers, Quentin. _______________________________________________ Etoile-dev mailing list Etoile-dev@gna.org https://mail.gna.org/listinfo/etoile-dev
