Zeta:Tests
From Freehackers
Contents |
[edit] Host Plateforms tested
The test consisted, from a clean checkout, on:
- compile/install the toolchain (binutils+gcc)
- make successful in tests/
- kernel compiles
- load_kernel goes to the same point as on the main computer (basically, as seen on the screenshots)
Zeta-0.5 was successfully tested on the following hosts :
- gentoo, gcc 4.0.3, amd64 (orzel@berlioz)
- gentoo, gcc 3.4.6, x86 (orzel@verdi)
- Zeta-0.4 was successfully tested on the following hosts :
- gentoo, gcc 4.0.3, amd64 (orzel@berlioz)
- gentoo, gcc 3.4.6, x86 (orzel@verdi)
- OpenSuse, gcc 4.0.2, amd64 (orzel@vmware)
- Gentoo, gcc 3.4.5, amd64 Turion (orzel@farfalla)
- Debian, gcc 3.3.5, VIA Esther (orzel@kyu) couldn't mknod, even as root (because this is a vserver). downloaded the ramdisk.romfs from another computer.
- Gentoo, gcc 3.4.6, x86 (orzel@barbichu)
- Fedora Core 4, gcc 4.0.0, amd64, (orzel@vmware)
Unsuccessfull tests
- Freebsd, gcc 3.4.4, i386 install on a amd64, (orzel@vmware) still doesn't compile (byteswap.h and endian.h missing)
- Darwin, gcc 3.1, ppc (64or32bits?), (orzel on sourceforge compile farm)
gcc -g -O2 -o fixincl fixincl.o fixtests.o fixfixes.o server.o procopen.o fixlib.o fixopts.o ../libiberty/libiberty.a ld: archive: ../libiberty/libiberty.a has no table of contents, add one with ranlib(1) (can't load from it)
and then :
ranlib: archive member: libiberty/libiberty.a(regex.o/) offset in archive not a multiple of sizeof(unsigned long)
[edit] Component Tests
More accurate details are given in the handbook about tests. More especially the zeta-specific tests are described in it.
Both binutils and gcc use dejagnu as testing framework. So you need to have it installed. We describe here how to run the tests, the expected results, and the current results.
[edit] Binutils
To start the tests, you need to go in the build dir :
cd zeta/bbinutils # this is the standard build dir for binutils in zeta make check
The results are kept in the page : Zeta:Binutils Tests
[edit] Gcc
To start the tests, you need to install an additional package named gcc-testsuite-4.x.y.tar.bz2, that you can find on any gnu/gcc mirror. The gcc/ dir in zeta is actually the package released by the gcc team under the name gcc-core-* (patched for zeta, of course). The testsuite package contains a directory 'testsuite' that you need to put as zeta/gcc/gcc/testsuite. Then, you need to start the tests with :
cd zeta/bgcc # standard build dir for gcc in zeta make -k check-gcc RUNTESTFLAGS="-v"
The -k is to keep on testing if some tests fail. the -v is to have some (verbose) report. You can remove it(less verbose) or write it twice("-v -v") for more verbosity.
The results are kept in the page : Zeta:Gcc Tests
[edit] Known bugs
This is not the place to report bugs. the zeta bugtracker is to be used for that. Here i take note about famous bug and fixes in case they re-appear later on.