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] |
Bryan, All, On Friday 19 March 2010 07:50:41 Bryan Hundven wrote: > When CT_USE_SYSROOT is not set, build scripts like gcc.sh try to copy > headers from ${CT_HEADERS_DIR}/* > In this case ${CT_HEADERS_DIR} directory does not contain the headers, > but ${CT_SYSROOT_DIR}/usr/include does. > The attached patch ensures ${CT_HEADERS_DIR}/* contains the kernel > headers when both CT_USE_SYSROOT is set and when it is not set. I was thinking of dumping the non-sysroot case. sysrooted toolchains have many advantages over non-sysrooted toolchain. For one, they are fully relocatable. And nowadays, non-sysrooted toolchains should simply die (IMHO). Do you have a specific requirement that you do not want a sysrooted toolchain? 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
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |