This is the mail archive of the crossgcc@sourceware.org mailing list for the crossgcc project.
See crosstool-NG for lots more information.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
Other format: | [Raw text] |
Hi All, I have made a try for support clang. (https://github.com/diorcety/crosstool-ng/tree/llvm) it seems work for C compiler but it uses gcc for assemble and link(only binutils if your target is *-*-linux ...) All the paths are hardcoded so for C++ it will no easy to make it works (look here: http://llvm.org/svn/llvm-project/cfe/trunk/lib/Frontend/InitHeaderSearch.cpp) Yann 2012/11/17 Maurizio Vitale <mrz.vtl@gmail.com>: > On Thu, Nov 15, 2012 at 3:00 PM, Yann E. MORIN <yann.morin.1998@free.fr> wrote: >> Maurizio, All, >> >> On Thursday 15 November 2012 Maurizio Vitale wrote: >>> My understanding is that no Clang support is planned until Clang gets >>> to cross-compilation on more platforms. >> >> That's my understanding, too, that clang is not yet ready for cross- >> compilation. And that's why I did not plan its inclusion for now. >> >>> Wouldn't be interesting to have initial support of clang in native mode >>> only? >>> I for one (ab?)use crosstool to build native toolchains, as it make a >>> good job at putting together compiler, binary utilities and libraries. >> >> Good to read. But then, how do you cope with sysroot? > > It's been a while, but from what I remember I was using sysroot to get > a nice hierarchy for libs and includes. > Then in compilation I was passing -I, -L and -Wl,-rpaths to get the > right pieces. I might forgetting parts, but that was the gist of it. > What do you suspect wouldn't work? > If I remember correctly I did confirm that the right dynamic libraries > were linked. > I didn't confirm that the right include files were used. > >> In crosstool-NG terminology, a native toolchain is one that targets >> the current system. It means that: >> - it targets the same architecture >> - it targets the same ABI >> - it targets the same kernel-system (eg. the same C library) >> > > For me is only the first one (and maybe the second, depending). I'm > definitely compiling a elibc and getting diffrent kernel headers from > what installed. > So maybe is not native in crosstool sense. > >> Also, crosstool-NG currently has no support for the 'native' toolchain >> case, and even explicitly aborts if you select 'native' in the menuconfig. >> Did you patch crosstool-NG to allow the 'native' case? > > No, see above. > > I'll try to find the time to go back to my setup and maybe add some > support for clang. Not sure when or if, though. > Thanks for all the work on crosstool, > > Maurizio > >> >>> Any work going on in this direction? >> >> Not from my part, except for keeping an eye on clang status from time to >> time. >> >> Regards, >> Yann E. MORIN. >> >> -- >> .-----------------.--------------------.------------------.--------------------. >> | Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: | >> | +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ | >> | +33 223 225 172 `------------.-------: X AGAINST | \e/ There is no | >> | http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. | >> '------------------------------^-------^------------------^--------------------' > > -- > For unsubscribe information see http://sourceware.org/lists.html#faq > -- Diorcet Yann -- For unsubscribe information see http://sourceware.org/lists.html#faq
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |