linux-omap.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@ucw.cz>
To: Rob Landley <rob@landley.net>
Cc: "Nicolas Pitre" <nico@fluxnic.net>,
	"Russell King - ARM Linux" <linux@arm.linux.org.uk>,
	"Måns Rullgård" <mans@mansr.com>, "Andrew Morton" <akpm@osdl.org>,
	"Trivial patch monkey" <trivial@kernel.org>,
	"Catalin Marinas" <Catalin.Marinas@arm.com>,
	"Will Deacon" <will.deacon@arm.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
	"Linus Torvalds" <torvalds@linux-foundation.org>,
	"linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>
Subject: Re: new binutils needed for arm in 3.12-rc1
Date: Fri, 27 Sep 2013 21:41:32 +0200	[thread overview]
Message-ID: <20130927194132.GA31663@amd.pavel.ucw.cz> (raw)
In-Reply-To: <1380235709.1974.93@driftwood>

Hi!

On Thu 2013-09-26 17:48:29, Rob Landley wrote:
> On 09/25/2013 11:13:17 AM, Nicolas Pitre wrote:
> >On Wed, 25 Sep 2013, Rob Landley wrote:
> >
> >> On 09/24/2013 09:07:57 PM, Nicolas Pitre wrote:
> >> > I'd strongly suggest you make your binutils compatible with newer
> >> > instruction syntax instead of making the kernel more complex.
> >>
> >> Meaning I play whack-a-mole as this becomes permission to depend
> >on endless
> >> new gnuisms just because they're there and nobody else is
> >regression testing
> >> against them, not because they actually add anything.
> >
> >Gnuism?
> >
> >Let me quote the ARM ARchitecture Reference Manual, version 7
> >revision C,
> >section A8.8.44 (sorry for the whitespace dammage):
> 
> Globally changing the binutils requirement for all architectures, as
> the doc patch at the start of this thread proposed doing, would mean
> gnuisms in common code (ext2 and such) wouldn't get caught, giving
> llvm and pcc and such a moving target when trying to build the
> kernel with non-gnu toolchains. That's what I meant by gnuisms
> breeding.

Well. I did the docs patch, but my preferred solution would actually
be to get the patches reverted so that it still works with old
binutils.

(So far, I updated one machine with new cross environment, two more to
go.)

Anyway, it should be solved _somehow_.
									Pavel
-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

  reply	other threads:[~2013-09-27 19:41 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-19  9:30 3.12-rc1: no longer compiles for Nokia n900 (omap based) Pavel Machek
2013-09-19  9:36 ` Will Deacon
2013-09-19  9:57   ` Pavel Machek
2013-09-23 23:59   ` new binutils needed for arm in 3.12-rc1 Pavel Machek
2013-09-24  2:13     ` Rob Landley
2013-09-24 12:11       ` Måns Rullgård
2013-09-24 21:23         ` Rob Landley
2013-09-24 21:48           ` Russell King - ARM Linux
2013-09-25  1:13             ` Rob Landley
2013-09-25  2:07               ` Nicolas Pitre
2013-09-25 15:23                 ` Rob Landley
2013-09-25 15:52                   ` Måns Rullgård
2013-09-26  0:10                     ` Rob Landley
2013-09-26 22:24                       ` Måns Rullgård
2013-09-25 16:13                   ` Nicolas Pitre
2013-09-26 22:48                     ` Rob Landley
2013-09-27 19:41                       ` Pavel Machek [this message]
2013-09-28  8:43                       ` Pavel Machek
2013-09-25 20:44                   ` Russell King - ARM Linux
2013-09-25 20:49                     ` Måns Rullgård
2013-09-26 22:50                       ` Rob Landley
2013-09-26  7:18               ` Geert Uytterhoeven
2013-09-28  9:03                 ` richard -rw- weinberger
2013-09-24  2:20     ` Rob Landley
2013-09-19  9:44 ` 3.12-rc1: no longer compiles for Nokia n900 (omap based), display no longer works Pavel Machek
2013-09-19 18:47   ` Aaro Koskinen
2013-09-26  0:23     ` Pavel Machek

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=20130927194132.GA31663@amd.pavel.ucw.cz \
    --to=pavel@ucw.cz \
    --cc=Catalin.Marinas@arm.com \
    --cc=akpm@osdl.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=linux@arm.linux.org.uk \
    --cc=mans@mansr.com \
    --cc=nico@fluxnic.net \
    --cc=rob@landley.net \
    --cc=torvalds@linux-foundation.org \
    --cc=trivial@kernel.org \
    --cc=will.deacon@arm.com \
    /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;
as well as URLs for NNTP newsgroup(s).