Re: Static linking impossible on the host system

[Christian Kujau <lists at nerdbynature dot de>]

On Sat, 15 Sep 2012 at 12:22, Yann E. MORIN wrote:
> config/cc/gcc.in.2:
>   43  config CC_STATIC_LIBSTDCXX
>   44      bool
>   45      prompt "Link libstdc++ statically into the gcc binary"
>   46      default y
>   47      depends on CC_GCC_4_4_or_later
>   48      select WANTS_STATIC_LINK

Isn't CC_STATIC_LIBSTDCXX a blind option as well? Two lines above it 
reads:

40 config STATIC_TOOLCHAIN
41   select CC_STATIC_LIBSTDCXX if CC_GCC_4_4_or_later
 
And since I'm using GCC 4.6.2, CC_STATIC_LIBSTDCXX will be selected - thus 
in turn WANTS_STATIC_LINK will be selected. I did not select anything :)

> So, if you sleected to statically link libstdc++, CT_WANTS_STATIC_LINK
> *will* be selected.

AFAICS, CT_WANTS_STATIC_LINK appears in 3 files:

config/toolchain.in
config/debug/gdb.in.cross
config/cc/gcc.in.2

But as I said before: I don't have EXPERIMENTAL enabled, thus I cannot 
(and have not) selected STATIC_TOOLCHAIN. In fact, STATIC_TOOLCHAIN does 
not even appear in my .config. So I really don't know why 
CT_WANTS_STATIC_LINK is selected at all.

> Please, see the code that does the failing test, run it by hand, note the
> error you get, and try to see how the code could be changed so as to avoid
> this error.

What is the advantage in having a static toolchain? Disabling 
WANTS_STATIC_LINK at least makes the compilation to progress further.

Christian.
-- 
BOFH excuse #215:

High nuclear activity in your area.

--
For unsubscribe information see http://sourceware.org/lists.html#faq