Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Giulio Benetti <giulio.benetti@benettiengineering.com>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH] package/elfutils: fix host build failure due to missing demangle support
Date: Thu, 9 May 2024 17:37:45 +0200	[thread overview]
Message-ID: <20240509173745.3f28d735@windsurf> (raw)
In-Reply-To: <20240418135615.457970-1-giulio.benetti@benettiengineering.com>

On Thu, 18 Apr 2024 15:56:15 +0200
Giulio Benetti <giulio.benetti@benettiengineering.com> wrote:

> When building on hosts with libstdc++ without demangle support this error
> shows up:
> checking for __cxa_demangle in -lstdc++... no
> configure: error: __cxa_demangle not found in libstdc++, use --disable-demangler to disable demangler support.
> make[1]: *** [package/pkg-generic.mk:273: /home/giuliobenetti/br_reproduce/c2524c7580d97f7387ec22da62be71d77f2ed8ec/output/build/host-elfutils-0.189/.stamp_configured] Error 1
> make: *** [Makefile:23: _all] Error 2
> 
> So let's disable demangler for host by default.
> 
> Fixes: still not showed by autobuilders. Reproduced on Ubuntu 22.04 with
> Ubuntu APT g++ 11.4.0
> 
> Signed-off-by: Giulio Benetti <giulio.benetti@benettiengineering.com>
> ---
>  package/elfutils/elfutils.mk | 1 +
>  1 file changed, 1 insertion(+)

Applied to master, thanks.

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

  parent reply	other threads:[~2024-05-09 15:37 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-18 13:56 [Buildroot] [PATCH] package/elfutils: fix host build failure due to missing demangle support Giulio Benetti
2024-04-22  1:24 ` Christian Stewart via buildroot
2024-05-09 15:37 ` Thomas Petazzoni via buildroot [this message]
2024-06-03 10:51 ` Peter Korsgaard

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=20240509173745.3f28d735@windsurf \
    --to=buildroot@buildroot.org \
    --cc=giulio.benetti@benettiengineering.com \
    --cc=thomas.petazzoni@bootlin.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox