mailing list of musl libc
 help / color / mirror / code / Atom feed
From: daggs <daggs@gmx.com>
To: Rich Felker <dalias@libc.org>
Cc: musl@lists.openwall.com
Subject: Re: [musl] musl 1.2.2 link error on __libc_malloc with --with-malloc=oldmalloc
Date: Sat, 17 Jul 2021 14:41:28 +0200	[thread overview]
Message-ID: <trinity-1eedd7fc-3fbf-4978-a306-80eaabb808d9-1626525688860@3c-app-mailcom-bs08> (raw)
In-Reply-To: <trinity-522aae38-39c9-4391-b405-32bd334a1c28-1626524167568@3c-app-mailcom-bs08>

confirmed, Thanks!

> Sent: Saturday, July 17, 2021 at 3:16 PM
> From: "daggs" <daggs@gmx.com>
> To: "Rich Felker" <dalias@libc.org>
> Cc: musl@lists.openwall.com
> Subject: Re: [musl] 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@libc.org>
> > To: "daggs" <daggs@gmx.com>
> > Cc: musl@lists.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
>

      reply	other threads:[~2021-07-17 12:41 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-17 11:35 daggs
2021-07-17 11:43 ` Rich Felker
2021-07-17 12:16   ` daggs
2021-07-17 12:41     ` daggs [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=trinity-1eedd7fc-3fbf-4978-a306-80eaabb808d9-1626525688860@3c-app-mailcom-bs08 \
    --to=daggs@gmx.com \
    --cc=dalias@libc.org \
    --cc=musl@lists.openwall.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/musl/

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).