From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Waldemar Brodkorb <wbx@openadk.org>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH] package/ffmpeg: fix microblaze compile issue
Date: Thu, 15 Aug 2024 14:50:06 +0200 [thread overview]
Message-ID: <20240815145006.72b13d72@windsurf> (raw)
In-Reply-To: <Zr3cWSzM+spo0TNf@waldemar-brodkorb.de>
On Thu, 15 Aug 2024 12:45:45 +0200
Waldemar Brodkorb <wbx@openadk.org> wrote:
> +ifeq ($(BR2_TOOLCHAIN_HAS_GCC_BUG_68485),y)
> +FFMPEG_CONF_OPTS += --disable-optimizations
> +FFMPEG_CFLAGS += -O0
> +endif
Could you clarify why both --disable-optimizations and -O0 are needed?
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
next prev parent reply other threads:[~2024-08-15 12:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-15 10:45 [Buildroot] [PATCH] package/ffmpeg: fix microblaze compile issue Waldemar Brodkorb
2024-08-15 12:50 ` Thomas Petazzoni via buildroot [this message]
2024-08-15 14:15 ` Waldemar Brodkorb
2024-08-15 19:49 ` Yann E. MORIN
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=20240815145006.72b13d72@windsurf \
--to=buildroot@buildroot.org \
--cc=thomas.petazzoni@bootlin.com \
--cc=wbx@openadk.org \
/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