Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Akshay Bhat <nodeax@gmail.com>
Cc: "Yann E . MORIN" <yann.morin.1998@free.fr>, buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/1] package/libiberty: bump version to 2.38
Date: Fri, 10 Feb 2023 23:13:15 +0100	[thread overview]
Message-ID: <20230210231315.17b367e6@windsurf> (raw)
In-Reply-To: <20230210180222.88328-1-nodeax@gmail.com>

Hello,

On Fri, 10 Feb 2023 10:02:22 -0800
Akshay Bhat <nodeax@gmail.com> wrote:

> If the libiberty package is not the same version as the one packaged
> with binutils AND if libiberty is installed before binutils, then the
> below error is observed. Hence for now let us keep the versions in sync.
> 
> /usr/bin/ld: ../libiberty/libiberty.a(hashtab.o):(.data.rel.local+0x0): multiple definition of `htab_eq_pointer'
> 
> Signed-off-by: Akshay Bhat <nodeax@gmail.com>

Thanks a lot for the fix. Is this fixing
http://autobuild.buildroot.net/results/eaf/eaf23ea0c8d7803e3768da40b7070d04801cd36f/build-end.log
perhaps?

One issue that I see is that the binutils version is configurable: we
support 2.37, 2.38, 2.39 and the special ARC version. Do we need to
make the libiberty version match with that?

Also, see the conversation starting at:

  https://lore.kernel.org/buildroot/3f3d266c-2f21-197c-29b7-fff3e230e97a@smile.fr/

Thanks!

Thomas
-- 
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

  reply	other threads:[~2023-02-10 22:13 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-10 18:02 [Buildroot] [PATCH 1/1] package/libiberty: bump version to 2.38 Akshay Bhat
2023-02-10 22:13 ` Thomas Petazzoni via buildroot [this message]
2023-02-10 23:28   ` Akshay Bhat

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=20230210231315.17b367e6@windsurf \
    --to=buildroot@buildroot.org \
    --cc=nodeax@gmail.com \
    --cc=thomas.petazzoni@bootlin.com \
    --cc=yann.morin.1998@free.fr \
    /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. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox