From: Jon Ringle <jon@ringle.org>
To: "ptxdist@pengutronix.de" <ptxdist@pengutronix.de>
Subject: Re: [ptxdist] Is OSELAS Toolchain (arm-1136jfs-linux-gnueabihf) affected by Blacklist GCC 4.8.0 to GCC 4.8.2 - PR58854
Date: Wed, 29 Oct 2014 11:02:17 -0400 [thread overview]
Message-ID: <CAMwGMjw2sbrg+gqE-dBzyKCTbW2TYCAjbFeY1ZafZqvwwM7HCg@mail.gmail.com> (raw)
In-Reply-To: <201410291446.20808.jbe@pengutronix.de>
[-- Attachment #1.1: Type: text/plain, Size: 946 bytes --]
On Wed, Oct 29, 2014 at 9:46 AM, Juergen Borleis <jbe@pengutronix.de> wrote:
> Hi Matthias,
>
> On Wednesday 29 October 2014 14:04:14 Matthias Klein wrote:
> > I try to complile linux-next and get an error about GCC4.8.2:
> > http://permalink.gmane.org/gmane.linux.ports.arm.omap/119412
> >
> > arch/arm/kernel/asm-offsets.c:53:2: error: #error Your compiler is too
> > buggy; it is known to miscompile kernels
> > #error Your compiler is too buggy; it is known to miscompile kernels
> > ^
> > arch/arm/kernel/asm-offsets.c:54:2: error: #error and result in
> > filesystem corruption and oopses.
> > #error and result in filesystem corruption and oopses.
> > ^
> >
> > Is the OSELAS Toolchain affected, or can I ignore / suppress that error?
>
> You can ignore this error (but you must comment out the test). Our
> OSELAS-4.8.2-Toolchains have the required patch already applied.
>
>
Is this fixed in OSELAS.Toolchain-2013.12.1 ?
Jon
[-- Attachment #1.2: Type: text/html, Size: 1566 bytes --]
[-- Attachment #2: Type: text/plain, Size: 48 bytes --]
--
ptxdist mailing list
ptxdist@pengutronix.de
next prev parent reply other threads:[~2014-10-29 15:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-29 13:04 Matthias Klein
2014-10-29 13:38 ` Alexander Dahl
2014-10-29 13:47 ` Juergen Borleis
2014-10-29 13:46 ` Juergen Borleis
2014-10-29 15:02 ` Jon Ringle [this message]
2014-10-29 15:35 ` Juergen Borleis
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=CAMwGMjw2sbrg+gqE-dBzyKCTbW2TYCAjbFeY1ZafZqvwwM7HCg@mail.gmail.com \
--to=jon@ringle.org \
--cc=ptxdist@pengutronix.de \
/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