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 Sunday 17 October 2010 20:00:13 Bryan Hundven wrote: > > It be might be interesting to have a toolchain using only static libs on > > the target, but this is another thing. > Oops, I forgot to remove the static options for the target. That was > just an experiment. Sorry ;) OK! :-) [--SNIP--] > > We do indeed want the final cc to be static. But what about the core cc? > > I know it is only a temporary build, and that it does not get into the > > toolchain proper. But would it also make sense to also build it static? > So, the gcc_core_shared should be another gcc_core_static? > I will start working on that if that is what you mean. No. gcc_core_shared means "gcc with support for shared libs on the target". And gcc_core_static means "gcc without support for shared libs on target". What I meant was "do we want the core gcc (static and shared) to also be statically linked?" I guess you can forget about the two core gcc-s. Lets keep them as they are for now, that is they get dynamically linked. (Note: gcc_core_shared also means "gcc with support for threads and TLS", but that's another thing...) > > Also, you're missing another component that runs on the host: the cross-gdb. > > There is already an option to build it statically, so it should be really > > easy to also apply this "static toolchain" option to the cross-gdb. > Do you mean in 'config STATIC_TOOLCHAIN' to add: > depends on GDB_CROSS_STATIC I mean that if STATIC_TOOLCHAIN is selected, then the cross-gdb should also be staticaly linked, as the current GDB_CROSS_STATIC does. So, GDB_CROSS_STATIC should "depends on ! STATIC_TOOLCHAIN", and the build script for gdb should use: if [ "${CT_GDB_CROSS_STATIC}" = "y" \ -o "${CT_STATIC_TOOLCHAIN}" = "y" ]; then blabla... fi > > Overall, it is good. Would you care to repost an amended version, please? > It wouldn't be a problem at all. When I get answers to my two > questions, I will post my revision. Thank you! 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] |