RE: multiple __libc_multiple_libcs error in compiling glibc 2.3.1

["Hu, Boris" <boris dot hu at intel dot com>]

The link map seems to be glibc/elf/librtld.mapT. 
But I could find __libc_multiple_libcs only once ???
any opinions? thanks. 

# cat librtld.mapT | grep __libc_multiple_libcs
                0x0000030c                __libc_multiple_libcs

boris

> -----Original Message-----
> From: Hu, Boris 
> Sent: 2003?1?24? 13:16
> To: 'Roland McGrath'
> Cc: 'Libc-Alpha (E-mail)'
> Subject: RE: multiple __libc_multiple_libcs error in 
> compiling glibc 2.3.1 
> 
> 
> or this map? thanks. 
> 
> # less librt.map
> GLIBC_2.1 {
>   global:
>     aio_cancel; aio_cancel64; aio_error; aio_error64; 
> aio_fsync; aio_fsync64;
>     aio_init; aio_read; aio_read64; aio_return; aio_return64; 
> aio_suspend;
>     aio_suspend64; aio_write; aio_write64; lio_listio; lio_listio64;
>   local:
>     *;
> };
> GLIBC_2.2 {
>   global:
>     clock_getres; clock_gettime; clock_settime; clock_getcpuclockid;
>     clock_nanosleep;
>     shm_open; shm_unlink;
>     timer_create; timer_delete; timer_getoverrun; timer_gettime;
>     timer_settime;
> } GLIBC_2.1;
> 
> 
> > -----Original Message-----
> > From: Hu, Boris 
> > Sent: 2003?1?24? 11:16
> > To: 'Roland McGrath'
> > Cc: Libc-Alpha (E-mail)
> > 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.
> > > 
> > 
>