This is the mail archive of the
libc-alpha@sources.redhat.com
mailing list for the glibc project.
RE: multiple __libc_multiple_libcs error in compiling glibc 2.3.1
- From: "Hu, Boris" <boris dot hu at intel dot com>
- To: "'Roland McGrath'" <roland at redhat dot com>
- Cc: "Libc-Alpha (E-mail)" <libc-alpha at sources dot redhat dot com>
- Date: Fri, 24 Jan 2003 11:15:46 +0800
- Subject: RE: multiple __libc_multiple_libcs error in compiling glibc 2.3.1
thanks for your response. Sorry for I am a newbie to glibc.
Do you mean ld.map ? I couldn't figure out the relation between
__libc_multiple_libcs
with ld.map.
another strange point is that I run the config without tls support, however
many tls functions
still found in ld.map???
# ../configure arm-linux --build=i686-pc-linux-gnu
--with-headers=/arm-linux-2.4.18/include
--enable-add-ons --enable-shared --prefix=$PREFIX --without-__thread
--without-tls
# less ld.map
GLIBC_2.0 {
global:
_r_debug;
calloc; free; malloc; realloc; __libc_memalign;
local:
*;
};
GLIBC_2.1 {
global:
_dl_mcount;
} GLIBC_2.0;
GLIBC_2.3 {
global:
__tls_get_addr;
} GLIBC_2.1;
GLIBC_PRIVATE {
global:
__libc_enable_secure; __libc_stack_end;
_dl_argv; _dl_catch_error; _dl_check_map_versions;
_dl_debug_printf; _dl_debug_state; _dl_dst_count;
_dl_dst_substitute; _dl_init; _dl_lookup_symbol; _dl_lookup_symbol_skip;
_dl_get_origin; _dl_tls_setup;
_dl_get_tls_static_info; _dl_allocate_tls_init;
_dl_lookup_versioned_symbol; _dl_lookup_versioned_symbol_skip;
_dl_map_object; _dl_map_object_deps; _dl_out_of_memory;
_dl_relocate_object; _dl_signal_error; _dl_start_profile;
_dl_starting_up;
_dl_unload_cache;
_rtld_global; _dl_tls_symaddr; _dl_allocate_tls; _dl_deallocate_tls;
} GLIBC_2.3;
> -----Original Message-----
> From: Roland McGrath [mailto:roland@redhat.com]
> Sent: 2003?1?24? 11:04
> To: Hu, Boris
> Cc: Libc-Alpha (E-mail)
> Subject: Re: multiple __libc_multiple_libcs error in
> compiling glibc 2.3.1
>
>
> That kind of lossage usually happens when something you didn't want is
> getting linked into ld.so for some reason. Look at the link
> map and figure
> out what leads to bringing in suspicious objects.
>