From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] docs/manual: add a 'Known issues' chapter
Date: Sun, 6 Oct 2013 23:22:40 +0200 [thread overview]
Message-ID: <20131006232240.3c8923c0@skate> (raw)
In-Reply-To: <87r4byfdql.fsf@dell.be.48ers.dk>
Dear Peter Korsgaard,
On Sun, 06 Oct 2013 20:36:34 +0200, Peter Korsgaard wrote:
> Thomas> +* The +prboom+ package triggers a compiler failure with the SuperH 4
> Thomas> + compiler from Soucery CodeBench, version 2012.09.
>
> I believe we have a lot of other situations with packages triggering
> internal compiler errors, especially for microblaze and avr32.
I agree, but I'm merely documenting the exceptions I've added in my
autobuilders script. I'm planning on adding similar exceptions and
documentation in this "Known issues" section for the other compiler
failures as well.
Best regards,
Thomas
--
Thomas Petazzoni, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2013-10-06 21:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-06 17:49 [Buildroot] [PATCH] docs/manual: add a 'Known issues' chapter Thomas Petazzoni
2013-10-06 18:36 ` Peter Korsgaard
2013-10-06 21:22 ` Thomas Petazzoni [this message]
2013-10-06 18:37 ` Samuel Martin
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=20131006232240.3c8923c0@skate \
--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