mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jan Dittmer <jdittmer@ppp0.net>
To: Linux kernel <linux-kernel@vger.kernel.org>
Subject: Kernel cross compile tests
Date: Wed, 05 Jan 2005 21:32:01 +0100	[thread overview]
Message-ID: <41DC4EC1.5030400@ppp0.net> (raw)

Hi,

I've been playing with gcc cross compilers lately and set up
a small test suite for linux kernels.
There is a (crude) web page summarizing the results here:
http://l4x.org/k/ .
On the web page you can nicely see that the -bk8 snapshot broke
the build for ia64, ppc64, s390 and sparc. m32r isn't
buildable anymore since 2.6.10.
2.6.10-mm1  is worse with only 4 (alpha, arm, i386, ppc) archs
buildable.
2.6.10 was quite good with 9 out of 22, 2.6.0 had 8 out of 20.

Notes:
- for frv I currently don't have a buildable gcc
  (I tried 3.3.3 and 3.4.2). There doesn't seem to be a list, web
  site, help forum for that arch. Also no entry in the MAINTAINERS
  file (2.6.10-mm1).
- for m68knommu I'm not really sure if m68k-linux is the appropriate
  toolchain, compiler complains about invalid option 5307
- dito arm26, 'as' doesn't know about 'no-fpu'
- h8300 and sh64 need a 'touch .config' before 'make defconfig'
- v850 is missing a defconfig
- sh defconfig is probably broken
- sh64 'as' has unrecognized option -isa=sh64, from help text
  it should probably be 'shmedia'

If anyone has workable configs for the non working archs I
could include them in the tests (better would be of course to
update the defconfig to anything buildable).
I'm trying to do daily runs of defconfig against -bk. I don't
know if it's useful - at least it produces a nice table :-).

Jan

ps: I'm aware of the osdl kernel testing pages, but they don't
  include that many archs nor do they test bk snapshots.


                 reply	other threads:[~2005-01-05 20:36 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=41DC4EC1.5030400@ppp0.net \
    --to=jdittmer@ppp0.net \
    --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

Powered by JetHome