[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Sat, 17 Jul 2021 14:16:07 +0200
From: daggs <daggs@....com>
To: Rich Felker <dalias@...c.org>
Cc: musl@...ts.openwall.com
Subject: Re: musl 1.2.2 link error on __libc_malloc with
--with-malloc=oldmalloc
Greetings Rich,
> Sent: Saturday, July 17, 2021 at 2:43 PM
> From: "Rich Felker" <dalias@...c.org>
> To: "daggs" <daggs@....com>
> Cc: musl@...ts.openwall.com
> Subject: Re: [musl] musl 1.2.2 link error on __libc_malloc with --with-malloc=oldmalloc
>
> On Sat, Jul 17, 2021 at 01:35:27PM +0200, daggs wrote:
> > Greetings,
> >
> > I seems to encounter an issue when creating a musl libc based cross compiler using crosstool-ng.
> > the error is as follows:
> > [ALL ] /home/dagg/workspace/crosstool-ng/.build/x86_64-unknown-linux-musl/buildtools/lib/gcc/x86_64-unknown-linux-musl/10.3.0/../../../../x86_64-unknown-linux-musl/bin/ld: obj/src/malloc/oldmalloc/malloc.lo: in function `__libc_malloc':
> > [ALL ] malloc.c:(.text.__libc_malloc+0x0): multiple definition of `__libc_malloc'; obj/src/malloc/lite_malloc.lo:lite_malloc.c:(.text.__libc_malloc+0x0): first defined here
> >
> > from the looks of it, __libc_malloc is defined in more than one files which are getting linked.
> > in comparison,in I downgrade musl to 1.2.1, the issue doesn't reproduces.
> >
> > has anyone encountered it? how can I fix this issue?
>
> commit 98b9df994c85dcb6a8a5a9099495dd44c7cf2bce fixes it:
>
> https://git.musl-libc.org/cgit/musl/commit/?id=98b9df994c85dcb6a8a5a9099495dd44c7cf2bce
>
I'll try it out.
Thanks
Powered by blists - more mailing lists
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
