All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Giulio Benetti <giulio.benetti@benettiengineering.com>
Cc: Bernd Kuhls <bernd@kuhls.net>,
	Pieter De Gendt <pieter.degendt@gmail.com>,
	Samuel Martin <s.martin49@gmail.com>,
	Giulio Benetti <giulio.benetti@micronovasrl.com>,
	buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 2/7] package/libheif: new package
Date: Sun, 30 Jul 2023 13:25:58 +0200	[thread overview]
Message-ID: <20230730132558.3bb1a428@windsurf> (raw)
In-Reply-To: <6c02501e-2414-4611-97cb-1460352f55a7@benettiengineering.com>

On Sun, 30 Jul 2023 12:56:42 +0200
Giulio Benetti <giulio.benetti@benettiengineering.com> wrote:

> there is a possible toolchain gcc bug:
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79509
> 
> but they point this to be a binutils bug, so I'm going to open a bug
> in Sourceware. I can't find it already, so yes, it must be open.
> We then need to add a BR2_TOOLCHAIN_HAS_BINUTILS_BUG_ and then I can
> check against it with the workaround(-fno-dwarf2-cfi-asm) and see if
> someone will fix it in binutils and backport patches.
> BUT I see only now that for BR2_m68k_cf C/CXXFLAGS have by default
> -fno-dwarf2-cfi-asm enabled and if that doesn't make the trick I need
> to find another work-around, or maybe it's completely another bug at
> this point. Soon I'll be on holidays and I will have more time so
> I will look into it.

Thanks for the feedback. I don't think we really need to find a
workaround, as I don't think we care much about m68k_cf support. It's
just that I prefer to have a clear relationship between an exclusion in
Buildroot (don't build this package) and a gcc or binutils bug, rather
than random architecture exclusions.

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-07-30 11:26 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-08 20:04 [Buildroot] [PATCH 1/7] package/libde265: new package Bernd Kuhls
2023-07-08 20:04 ` [Buildroot] [PATCH 2/7] package/libheif: " Bernd Kuhls
2023-07-30 10:26   ` Thomas Petazzoni via buildroot
2023-07-30 10:56     ` Giulio Benetti
2023-07-30 11:25       ` Thomas Petazzoni via buildroot [this message]
2023-07-08 20:04 ` [Buildroot] [PATCH 3/7] package/gd: add optional support for libheif Bernd Kuhls
2023-07-30 10:27   ` Thomas Petazzoni via buildroot
2023-07-08 20:04 ` [Buildroot] [PATCH 4/7] package/imagemagick: " Bernd Kuhls
2023-07-30 10:27   ` Thomas Petazzoni via buildroot
2023-07-08 20:04 ` [Buildroot] [PATCH 5/7] package/libvips: " Bernd Kuhls
2023-07-30 10:27   ` Thomas Petazzoni via buildroot
2023-07-08 20:04 ` [Buildroot] [PATCH 6/7] package/kodi-imagedecoder-heif: new package Bernd Kuhls
2023-07-30 10:33   ` Thomas Petazzoni via buildroot
2023-07-08 20:04 ` [Buildroot] [PATCH 7/7] package/kodi-imagedecoder-raw: " Bernd Kuhls
2023-07-30 10:35   ` Thomas Petazzoni via buildroot
2023-07-30 10:24 ` [Buildroot] [PATCH 1/7] package/libde265: " Thomas Petazzoni via buildroot

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=20230730132558.3bb1a428@windsurf \
    --to=buildroot@buildroot.org \
    --cc=bernd@kuhls.net \
    --cc=giulio.benetti@benettiengineering.com \
    --cc=giulio.benetti@micronovasrl.com \
    --cc=pieter.degendt@gmail.com \
    --cc=s.martin49@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.