Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Vicente Olivert Riera <Vincent.Riera@imgtec.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] mesa3d: use -mno-compact-eh for Code Sourcery MIPS
Date: Tue, 31 May 2016 15:46:59 +0100	[thread overview]
Message-ID: <574DA3E3.7000101@imgtec.com> (raw)
In-Reply-To: <20160531164415.7f5c07b3@free-electrons.com>

Hello Thomas,

On 31/05/16 15:44, Thomas Petazzoni wrote:
> Hello,
> 
> On Tue, 31 May 2016 15:28:38 +0100, Vicente Olivert Riera wrote:
> 
>>> 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.  
>>
>> -mcompact-eh is only supported in Mentor tools currently. My patch is a
>> workaround for a broken toolchain feature. I'm not sure which
>> place is best. I suggest Buildroot is appropriate here as the issue is
>> specific to Mentor tools which are only used in cross compile
>> environments like Buildroot.
> 
> Hum, OK. This should probably have been explained in the commit log
> and/or in a comment above the workaround.

Sorry about that. Care to amend the commit log if you finally apply this
patch?

> But if indeed
> -mcompact-eh/-mno-compact-eh are available only in the Mentor
> toolchain, then your proposal is the most appropriate one.

This for master...

> Or, alternatively, we could simply add this as a forced CFLAGS when
> this toolchain is used, which would also avoid the need for a similar
> workaround in the libffi package.

...and this for next?

Regards,

Vincent.

> Best regards,
> 
> Thomas
> 

  reply	other threads:[~2016-05-31 14:46 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
2016-05-31 14:28   ` Vicente Olivert Riera
2016-05-31 14:44     ` Thomas Petazzoni
2016-05-31 14:46       ` Vicente Olivert Riera [this message]
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=574DA3E3.7000101@imgtec.com \
    --to=vincent.riera@imgtec.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