From: Adrian Bunk <bunk@kernel.org>
To: Martin Schwidefsky <schwidefsky@de.ibm.com>
Cc: gerg@uclinux.org, linux-kernel@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: m68knommu compile error
Date: Sat, 9 Feb 2008 12:53:44 +0200 [thread overview]
Message-ID: <20080209105344.GH6505@cs181133002.pp.htv.fi> (raw)
In-Reply-To: <1202552472.8936.7.camel@localhost>
On Sat, Feb 09, 2008 at 11:21:12AM +0100, Martin Schwidefsky wrote:
> On Sat, 2008-02-09 at 00:25 +0200, Adrian Bunk wrote:
> > Commit 2f569afd9ced9ebec9a6eb3dbf6f83429be0a7b4 breaks m68knommu:
>
> Does the patch below fixes the problem?
Thanks, it fixes it.
> I tried to cross compile for
> m68knommu but it seems like you need a special m68k compiler to get it
> compile all the way through.
I'm using one from upstream svn head (= tree that will become gcc 4.3).
> With the patch it did fail with a different
> error, so I assume it is fixed.
That's Matt's "break all no-MMU architectures in swapops.h" regression
for which a patch is already floating around.
> The problem is that the pgtable_t is
> simply missing for m68knommu, I must have overlooked a reject for one of
> the constant regenerations of the patch to keep up with upstream. Sorry
> about that.
>
> blue skies,
> Martin.
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
next prev parent reply other threads:[~2008-02-09 10:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-08 22:25 Adrian Bunk
2008-02-09 10:21 ` Martin Schwidefsky
2008-02-09 10:53 ` Adrian Bunk [this message]
2008-02-09 10:58 ` Martin Schwidefsky
2008-02-09 17:59 ` Mike Frysinger
2008-02-11 5:22 ` Greg Ungerer
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=20080209105344.GH6505@cs181133002.pp.htv.fi \
--to=bunk@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=gerg@uclinux.org \
--cc=linux-kernel@vger.kernel.org \
--cc=schwidefsky@de.ibm.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
all inboxes | Powered by JetHome®