From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] package/minidlna: disable on nios2
Date: Sun, 30 Nov 2014 14:55:24 +0100 [thread overview]
Message-ID: <20141130145524.3fce8153@free-electrons.com> (raw)
In-Reply-To: <20141130112049.GA4124@free.fr>
Dear Yann E. MORIN,
On Sun, 30 Nov 2014 12:20:49 +0100, Yann E. MORIN wrote:
> > Can we instead please blacklist only the specific NIOS II toolchain
> > causing the problem?
>
> Well, as Bernd says, both toolchains we support exhibit that bug.
>
> And you already did two similar patches, where you just did what Bernd
> submitted for minidlna:
> - f287f0aa crda: disable on NIOS II
> - 50d36731 aiccu: not available on NIOS II
>
> So I think it is a bit too much to ask to just blacklist the affected
> toolchains, especially since they all are affected, and we can not build
> our own.
I agree that we may not be doing this properly in other packages.
However, I still believe in such situations that it's better to
blacklist the individual toolchains that are known to be broken, so
that if we add another toolchain, we will be able to see if the same
bug happens as well or not.
Ideally, we should report such bugs to Mentor, but so far, they have
never seem to be really interested by bug reports we could make about
their toolchains.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
prev parent reply other threads:[~2014-11-30 13:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-29 18:56 [Buildroot] [PATCH 1/1] package/minidlna: disable on nios2 Bernd Kuhls
2014-11-29 21:29 ` Yann E. MORIN
2014-11-30 8:43 ` Thomas Petazzoni
2014-11-30 10:25 ` Bernd Kuhls
2014-11-30 11:20 ` Yann E. MORIN
2014-11-30 13:55 ` Thomas Petazzoni [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=20141130145524.3fce8153@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