This is the mail archive of the
mailing list for the glibc project.
Re: Multiple definition of __libc_multiple_libcs
- From: "P. J. McDermott" <pjm at nac dot net>
- To: Mike Frysinger <vapier at gentoo dot org>
- Cc: libc-help at sourceware dot org
- Date: Sun, 22 Apr 2012 13:30:43 -0400
- Subject: Re: Multiple definition of __libc_multiple_libcs
- References: <4F9378BB.firstname.lastname@example.org> <email@example.com>
On 04/22/2012 11:35 AM, Mike Frysinger wrote:
> On Saturday 21 April 2012 23:19:23 P. J. McDermott wrote:
>> Trying to cross build EGLIBC 2.15
> again, same answer as before -- we can't keep track of all the patches that
> are in there different from glibc-2.15. why don't you just use glibc instead ?
>> arm-cortex_a8-linux-gnueabi-gcc -nostdlib -nostartfiles -r -o <build
>> >/elf/librtld.map.o '-Wl,-(' <build>/elf/dl-allobjs.os <build>/libc_pi
>> c.a -lgcc '-Wl,-)' -Wl,-Map,<build>/elf/librtld.mapT
>> <build>/libc_pic.a(init-first.os):(.data+0x0): multiple definition of
>> <build>/elf/dl-allobjs.os:(.bss+0x9c): first defined here
>> collect2: ld returned 1 exit status
> this is a generic error. you should look at the .map file produced and trace
> back why the extra objects are getting included. i'm not aware of an easier
> way than that. some common reasons are the toolchain implicitly enables SSP
> or other hardened options that end up causing more objects than normal to get
> pulled in.
Sorry, it turns out I failed to correctly place the ports add-on...
With that fixed, the library builds without error.