This is the mail archive of the crossgcc@sourceware.org mailing list for the crossgcc project.
See the CrossGCC FAQ 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] |
On Thu, Jan 20, 2011 at 12:43 PM, Yann E. MORIN <yann.morin.1998@anciens.enib.fr> wrote: > Alexey, All, > > On Thursday 20 January 2011 12:13:42 Alexey Kuznetsov wrote: >> I've taken 1.9.2 and seems the issue is still here >> >> [CFG Â]         /*-----------------------------------------------* >> [CFG Â]         Â*      CLooG configuration is OK      * >> [CFG Â]         Â*-----------------------------------------------*/ >> [CFG Â]  ÂIt appears that your system is OK to start CLooG compilation. You need >> [CFG Â]  Ânow to type "make". After compilation, you should check CLooG by typing >> [CFG Â]  Â"make check". If no problem occur, you can type "make uninstall" if >> [CFG Â]  Âyou are upgrading an old version. Lastly type "make install" to install >> [CFG Â]  ÂCLooG on your system (log as root if necessary). >> [EXTRA]  ÂBuilding CLooG/ppl >> [DEBUG]  Â==> Executing: 'make -j8' >> [ALL Â]  Âmake[1]: Entering directory `/home/alexey/Downloads/.build/arm-iwmmxt-linux-gnueabi/build/build-cloog-ppl' >> [ALL Â]  Âmake[1]: *** No rule to make target `/home/alexey/Downloads/.build/src/cloog-ppl-0.15.10/m4/libtool.m4', needed by `/home/alexey/Downloads/.build/src/cloog-ppl-0.15.10/Makefile.in'. ÂStop. >> [ALL Â]  Âmake[1]: Leaving directory `/home/alexey/Downloads/.build/arm-iwmmxt-linux-gnueabi/build/build-cloog-ppl' >> [ERROR]  ÂBuild failed in step 'Installing CLooG/ppl' > > Yes, the patch made it after the release. It's available in the fixes > directory: > Âhttp://ymorin.is-a-geek.org/download/crosstool-ng/01-fixes/1.9.2/ I still see the issue on fedora core 14. >> 2nd question: Is it possible to have a sysroot location >> configurable? > > No, the sysroot has to be a sub-directory of the toolchain, so that the > toolchain is relocatable. When the sysroot is a sub-directory of the > toolchain installation path, then gcc knows where to search it, so the > whole toolchain can be moved around. If the sysroot is not a sub-directory > of the toolchain installation path, and the toolchain is moved, then gcc > will fail to find the sysroot. Is it possible to have a sysroot location configurable and still restricted to the toolchain directory? > 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 > > -Bryan -- 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] |