linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Rob Landley <rob@landley.net>
To: Lennart Sorensen <lsorense@csclub.uwaterloo.ca>
Cc: Geert Uytterhoeven <geert@linux-m68k.org>,
	Sam Ravnborg <sam@ravnborg.org>,
	linux-kernel@vger.kernel.org, dwmw2@infradead.org
Subject: Re: make headers_install broken for ARCH=m68k in 2.6.29-rc7.
Date: Wed, 1 Apr 2009 21:14:05 -0500	[thread overview]
Message-ID: <200904012114.07183.rob@landley.net> (raw)
In-Reply-To: <20090401225916.GZ3795@csclub.uwaterloo.ca>

On Wednesday 01 April 2009 17:59:16 Lennart Sorensen wrote:
> On Wed, Apr 01, 2009 at 10:23:06PM +0200, Geert Uytterhoeven wrote:
> > It entered mainline just before v2.6.29 (after v2.6.29-rc8)?
> > Or did you find a new problem?
>
> No, I just didn't check yet.  I am still solving uclibc issues, so
> 2.6.29-rc3 was still doing the job.

uClibc's working for me just fine.  Either grab the most recent build scripts 
from http://impactlinux.com/hg/firmware or grab the prebuilt binaries from 
http://impactlinux.com/fwl/downloads/snapshots/ (which has cross compilers, 
root filesystem tarballs, and system images bootable by qemu).

I haven't tested m68k yet because qemu doesn't support it (just coldfire), and 
aranym hasn't got a serial console, but it did compile using the same build 
scripts as all the other targets...

Rob
-- 
GPLv3 is to GPLv2 what Attack of the Clones is to The Empire Strikes Back.

  reply	other threads:[~2009-04-02  2:14 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-12  9:37 make headers_install broken for ARCH=m68k in 2.6.29-rc7 Rob Landley
2009-03-12  9:58 ` Sam Ravnborg
2009-03-12 20:03   ` Rob Landley
2009-03-12 20:58     ` Sam Ravnborg
2009-03-12 23:24       ` Stephen Rothwell
2009-03-12 21:02     ` Sam Ravnborg
2009-03-12 22:40       ` Geert Uytterhoeven
2009-03-13  3:25         ` Rob Landley
2009-03-13  7:04           ` Greg Ungerer
2009-03-13  8:25             ` Sam Ravnborg
2009-03-13  8:33               ` Geert Uytterhoeven
2009-03-13  8:59                 ` Sam Ravnborg
2009-03-13 10:52                   ` Greg Ungerer
2009-03-13 12:14                     ` Geert Uytterhoeven
2009-03-16 12:40                       ` Greg Ungerer
2009-03-16 20:20                         ` Rob Landley
2009-03-16 22:08                           ` Geert Uytterhoeven
2009-03-16 23:09                             ` Greg Ungerer
2009-03-16 23:10                           ` Greg Ungerer
2009-03-18  4:03                             ` Rob Landley
2009-03-18  5:34                               ` Greg Ungerer
2009-03-18 18:12                                 ` Rob Landley
2009-03-18 23:53                                   ` Greg Ungerer
2009-03-19  7:59                                   ` Geert Uytterhoeven
2009-03-19  8:41                                     ` Rob Landley
2009-03-13  8:25           ` Geert Uytterhoeven
2009-03-13  6:53         ` Greg Ungerer
2009-04-01 16:57 ` Lennart Sorensen
2009-04-01 19:03   ` Sam Ravnborg
2009-04-01 19:48     ` Lennart Sorensen
2009-04-01 20:23       ` Geert Uytterhoeven
2009-04-01 22:59         ` Lennart Sorensen
2009-04-02  2:14           ` Rob Landley [this message]
2009-04-02 21:59             ` Lennart Sorensen
2009-04-03  0:24               ` Rob Landley
2009-04-03  4:10                 ` Lennart Sorensen

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=200904012114.07183.rob@landley.net \
    --to=rob@landley.net \
    --cc=dwmw2@infradead.org \
    --cc=geert@linux-m68k.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lsorense@csclub.uwaterloo.ca \
    --cc=sam@ravnborg.org \
    /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).