From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] mesa3d: use -mno-compact-eh for Code Sourcery MIPS
Date: Tue, 31 May 2016 13:59:36 +0200 [thread overview]
Message-ID: <20160531135936.4f2c0691@free-electrons.com> (raw)
In-Reply-To: <1464689755-63804-1-git-send-email-Vincent.Riera@imgtec.com>
Hello,
On Tue, 31 May 2016 11:15:55 +0100, Vicente Olivert Riera wrote:
> +# mesa3d doesn't like the new compressed exception handling of the Code
> +# Sourcery MIPS toolchain and it fails to compile. Using -mno-compact-eh
> +# fixes the problem.
> +ifeq ($(BR2_TOOLCHAIN_EXTERNAL_CODESOURCERY_MIPS),y)
> +MESA3D_CONF_ENV += CFLAGS="$(TARGET_CFLAGS) -mno-compact-eh"
> +MESA3D_CONF_ENV += CXXFLAGS="$(TARGET_CXXFLAGS) -mno-compact-eh"
> +endif
Isn't an upstreamable fix to mesa3d configure script a better solution?
See package/libffi/0002-Fix-use-of-compact-eh-frames-on-MIPS.patch in
Buildroot.
Do you know when code can be built with this "Compact EH" feature and
when code cannot? I.e how many packages are going to be potentially
affected by this?
Thanks,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2016-05-31 11:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-31 10:15 [Buildroot] [PATCH] mesa3d: use -mno-compact-eh for Code Sourcery MIPS Vicente Olivert Riera
2016-05-31 11:59 ` Thomas Petazzoni [this message]
2016-05-31 14:28 ` Vicente Olivert Riera
2016-05-31 14:44 ` Thomas Petazzoni
2016-05-31 14:46 ` Vicente Olivert Riera
2016-05-31 19:11 ` Thomas Petazzoni
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=20160531135936.4f2c0691@free-electrons.com \
--to=thomas.petazzoni@free-electrons.com \
--cc=buildroot@busybox.net \
/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