[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Making shared libraries (DLLs) on Windows: -no-undefined
From: |
Brian Dessent |
Subject: |
Re: Making shared libraries (DLLs) on Windows: -no-undefined |
Date: |
Mon, 30 Apr 2007 10:51:26 -0700 |
John Brown wrote:
> Running 'nm --undefined-only libamrnb-2.dll' gives:
>
> U ___crt_xc_end__
> U ___crt_xc_start__
> U ___crt_xi_end__
> U ___crt_xi_start__
> U ___crt_xl_start__
> U ___crt_xp_end__
> U ___crt_xp_start__
> U ___crt_xt_end__
> U ___crt_xt_start__
> U ___tls_end__
> U ___tls_start__
> U __end__
>
> If undefined symbols are not allowed, then what's that?
Those are labels created by the linker script. They represent
locations, not data. You can refer to them in your C code only as
&__foo__, never as __foo__. I don't know why they are marked U. In any
case, this is not at all the same situation as function or data imports.
Brian
- Making shared libraries (DLLs) on Windows: -no-undefined, John Brown, 2007/04/29
- Re: Making shared libraries (DLLs) on Windows: -no-undefined, Brian Dessent, 2007/04/29
- Re: Making shared libraries (DLLs) on Windows: -no-undefined, John Brown, 2007/04/30
- Re: Making shared libraries (DLLs) on Windows: -no-undefined, Ralf Wildenhues, 2007/04/30
- Re: Making shared libraries (DLLs) on Windows: -no-undefined, John Brown, 2007/04/30
- Re: Making shared libraries (DLLs) on Windows: -no-undefined, Bob Rossi, 2007/04/30
- Re: Making shared libraries (DLLs) on Windows: -no-undefined, Brian Dessent, 2007/04/30
- Re: Making shared libraries (DLLs) on Windows: -no-undefined, Bob Rossi, 2007/04/30
- Re: Making shared libraries (DLLs) on Windows: -no-undefined,
Brian Dessent <=
Re: Making shared libraries (DLLs) on Windows: -no-undefined, Christian Biesinger, 2007/04/30