Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH/next v2] package/mesa3d: fix nouveau std::isinf related compile failure
Date: Thu, 5 Mar 2020 18:21:31 +0100	[thread overview]
Message-ID: <20200305172131.GG5357@scaer> (raw)
In-Reply-To: <20200304221146.461a3864@gmx.net>

Peter, All,

On 2020-03-04 22:11 +0100, Peter Seiderer spake thusly:
> On Wed, 4 Mar 2020 18:58:00 +0100, "Yann E. MORIN" <yann.morin.1998@free.fr> wrote:
> > On 2020-03-04 12:00 +0100, Peter Seiderer spake thusly:
> > > Activate already existing mesa3d solution for the isinf compile
> > > failure for uclibc based toolchains instead of using a custom
> > > workaround.
> > >
> > > - remove 0005-src-gallium-drivers-nouveau-codegen-nv50_ir_ra.cpp-p.patch
> > > - add 0004-c99_math-import-isinf-for-uclibc-based-toolchains.patch
> > >
> > > Fixes:
> > >   http://autobuild.buildroot.net/results/cbefc5d4a4fefb674e596400fa1d2698cd89c5b3/
> > >   http://autobuild.buildroot.net/results/dc974da012f53fa4ed3be616f937b0afae423d66/
> > You've tagged this patch for next, but the two failures pccured on
> > master.
> > Where should this patch be applied, then?
> The patch [1] was meant for master (minimal change, minimal risk)
> and this one (v1/v2) for next..., chronological later, first not
> sure about the solution...., but after re-thinking more sure this
> one is the right (and upstream acceptable) solution suitable for
> master and next...

Followign this discusion, I've applied it to master (rather than next).
Thanks!

Regards,
Yann E. MORIN.

-- 
.-----------------.--------------------.------------------.--------------------.
|  Yann E. MORIN  | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software  Designer | \ / CAMPAIGN     |  ___               |
| +33 561 099 427 `------------.-------:  X  AGAINST      |  \e/  There is no  |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL    |   v   conspiracy.  |
'------------------------------^-------^------------------^--------------------'

      reply	other threads:[~2020-03-05 17:21 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-04 11:00 [Buildroot] [PATCH/next v2] package/mesa3d: fix nouveau std::isinf related compile failure Peter Seiderer
2020-03-04 17:58 ` Yann E. MORIN
2020-03-04 21:11   ` Peter Seiderer
2020-03-05 17:21     ` Yann E. MORIN [this message]

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=20200305172131.GG5357@scaer \
    --to=yann.morin.1998@free.fr \
    --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