[klibc] RFT: klibc 2.0.5

Ben Hutchings ben at decadent.org.uk
Fri Jan 18 18:15:26 PST 2019

In preparation for the klibc 2.0.5 release I wrote a basic test script

1. Builds for each architecture (with a cross-compiler where needed)
2. Runs several statically-linked programs (using qemu-user where
   a. Many self-test programs
   b. "sh -c exit"
   c. "sh -c '.../bin/true; exit'"

The results for the architectures I was able to test are:

                                2.0.4                    2.0.5
alpha/alpha-linux-gnu:          fail: fcntl, sigint, 2c  fail: sigint, 2c
arm/arm-linux-gnueabi:          pass                     pass
arm/arm-linux-gnueabihf:        pass                     pass
arm64/aarch64-linux-gnu:        fail: fcntl              pass
i386/i686-linux-gnu:            fail: build              pass
m68k/m68k-linux-gnu:            pass                     pass
mips/mips-linux-gnu:            fail: build              pass
mips/mipsel-linux-gnu:          fail: build              pass
mips64/mips64el-linux-gnuabi64: fail: build              pass
parisc/hppa-linux-gnu:          fail: fcntl, vfork       fail: fcntl, vfork
ppc/powerpc-linux-gnu:          pass                     pass
ppc/powerpc-linux-gnuspe:       fail: all tests          fail: all tests
ppc64/powerpc64-linux-gnu:      fail: fcntl              pass
ppc64/powerpc64le-linux-gnu:    fail: fcntl              pass
riscv64/riscv64-linux-gnu:      N/A                      pass
s390x/s390x-linux-gnu:          fail: fcntl              pass
sh/sh4-linux-gnu:               pass                     pass
sparc64/sparc64-linux-gnu:      fail: all tests          fail: select, sigint, 2c
x86_64/x86_64-linux-gnu:        fail: fcntl              pass

So this doesn't indicate any regressions, but does show some serious
problems remaining.

I'm not able to test cris, ia64, s390 (32-bit), or sparc32 at all, so I
would appreciate any regression testing people can do on those, or
indeed more regression testing on the architectures listed above.

(As the test script currently only covers static builds, it wouldn't
have caught the x86 problems with shared libraries.  qemu-user also
provides imperfect emulation of architecture-specific quirks of the
kernel, which could result in false positives or negatives.  So I would
like to switch to building a kernel and an initramfs with a shared
build of klibc and then running them under qemu-system, but that will
take a lot more work.)


Ben Hutchings
Hoare's Law of Large Problems:
   Inside every large problem is a small problem struggling to get out.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: This is a digitally signed message part
URL: <http://www.zytor.com/pipermail/klibc/attachments/20190119/a92e730a/attachment.sig>

More information about the klibc mailing list