From: Herbert Poetzl <herbert@13thfloor.at>
To: Andi Kleen <ak@suse.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Kernel Cross Compiling
Date: Sat, 14 Feb 2004 00:45:54 +0100 [thread overview]
Message-ID: <20040213234554.GA32440@MAIL.13thfloor.at> (raw)
In-Reply-To: <p73n07my8nn.fsf@verdi.suse.de>
On Fri, Feb 13, 2004 at 10:25:00PM +0100, Andi Kleen wrote:
> Herbert Poetzl <herbert@13thfloor.at> writes:
>
> > [ARCH sparc64/sparc] failed. failed.
> > [ARCH x86_64/x86_64] failed. succeeded.
>
> Your test methology must be broken. 2.4.25rc2 cross compiles
> just fine here from i386 to x86_64.
okay, here is the promised update, a little later
as planned, because I discovered that doing 'make dep'
would be a great idea too (well that isn't necessary
for 2.6.x so it doesn't change those results), but
still some archs give troubles ...
linux-2.4.25-rc2 config dep kernel modules
alpha/alpha: OK OK OK OK
hppa/parisc: OK OK FAILED FAILED
hppa64/parisc: OK OK FAILED FAILED
i386/i386: OK OK OK OK
m68k/m68k: OK OK OK OK
mips/mips: OK OK FAILED FAILED
mips64/mips64: OK OK FAILED FAILED
ppc/ppc: OK OK OK OK
ppc64/ppc64: OK FAILED FAILED OK
s390/s390: OK OK OK OK
sparc/sparc: OK OK FAILED FAILED
sparc64/sparc64: OK OK OK OK
x86_64/x86_64: OK OK OK OK
but hey, it's better than before ...
you can get all the details, what and why? it fails
from the logs:
http://vserver.13thfloor.at/Stuff/Cross/LOGS-2.4.25-rc2/
any help or hints are appreciated, as it would be great
to get this running ...
TIA,
Herbert
> -Andi
next prev parent reply other threads:[~2004-02-13 23:47 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20040213205743.GA30245@MAIL.13thfloor.at.suse.lists.linux.kernel>
2004-02-13 21:25 ` Andi Kleen
2004-02-13 21:46 ` Herbert Poetzl
2004-02-13 23:45 ` Herbert Poetzl [this message]
2004-02-15 11:16 ` Geert Uytterhoeven
2004-02-15 17:38 ` Herbert Poetzl
2004-02-16 13:51 ` Keith Owens
2004-02-17 21:51 Judith Lebzelter
2004-02-18 7:19 ` Herbert Poetzl
-- strict thread matches above, loose matches on Subject: below --
2004-02-14 21:03 Dan Kegel
2004-02-14 22:07 ` Herbert Poetzl
2004-02-15 3:51 ` Dan Kegel
2004-02-14 3:26 Stephen M. Kenton
2004-02-14 14:21 ` Herbert Poetzl
2004-02-15 23:28 ` Robert Schwebel
2004-02-15 23:59 ` William Lee Irwin III
2004-02-13 20:57 Herbert Poetzl
2004-02-13 21:31 ` David Mosberger
2004-02-13 21:44 ` Herbert Poetzl
2004-02-14 0:58 ` David Mosberger
2004-02-14 1:08 ` Herbert Poetzl
2004-02-14 2:35 ` Herbert Poetzl
2004-02-14 2:51 ` David Mosberger
2004-02-16 22:50 ` Jim Wilson
2004-02-16 0:03 ` Peter Chubb
2004-02-14 8:32 ` Timothy D. Witham
2004-02-14 13:03 ` Herbert Poetzl
2004-02-14 19:25 ` Timothy D. Witham
2004-02-14 22:08 ` Herbert Poetzl
2004-02-16 21:41 ` cliff white
2004-02-16 22:10 ` Herbert Poetzl
2004-02-17 13:26 ` Maciej W. Rozycki
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=20040213234554.GA32440@MAIL.13thfloor.at \
--to=herbert@13thfloor.at \
--cc=ak@suse.de \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®