Re: Docs for --unresolved-symbols unclear?

[Vladimir Prus <ghost at cs dot msu dot su>]

Hi Nick,

>> I get only warning, and binary crashes at runtime. So, it seems that
>> default  value of --unresolved-symbls is not "ignore-all".
> 
>> Is it so, and what's the real default value, or I'm missing
>> something?
> 
> No - the default was changed in order to allow autoconf to work, but
> the documentation was not updated to match this change.  I am going to
> apply the patch below to fix the documentation.

Thanks for explaining this!

> *************** for which shared libraries are supported
> *** 985,992 ****
>   default on such platforms.  The different variants of this option are
>   for compatibility with various systems.  You may use this option
>   multiple times on the command line: it affects library searching for
> ! @option{-l} options which follow it.  This
> ! option also implies @option{--unresolved-symbols=ignore-all}.
>   
>   @kindex -Bgroup
>   @item -Bgroup
> --- 985,991 ----
>   default on such platforms.  The different variants of this option are
>   for compatibility with various systems.  You may use this option
>   multiple times on the command line: it affects library searching for
> ! @option{-l} options which follow it.

Now, I'm at loss again. This change removes stagement that -Bdynamic implies
--unresolved-symbols=ignore-all. But when I try my test case:

    void foo();

    int main()
    {
        foo();
    }

with 

  g++ a.cpp -Wl,-Bdynamic

I get:

a.cpp:6:2: warning: no newline at end of file
/tmp/ccaT8qMm.o(.text+0x11): In function `main':
: warning: undefined reference to `foo()'

That is, I get warning, not error. Without, -Bdynamic, I get error, as
expected. I'm using binutils 2.14.90.0.6-3 on Debian, so it might not be
the most current version. OTOH, Changelog does not mention any significant
changes to -Bdynamic.

- Volodya