[klibc] [PATCH] klcc compatibility with gcc

Erik van Konijnenburg ekonijn at xs4all.nl
Wed Mar 2 15:07:37 PST 2005

On Wed, Mar 02, 2005 at 12:27:43PM -0800, H. Peter Anvin wrote:
> Anyway, your patch applied (except for the 'obj' bit; instead I fixed 
> the underlying bug) and released as 0.203.

Thanks for the fast response.

In the mean time, I did some further testing: take a pristine
ash-0.5.1 tarball (from a debian source package), run configure/make
with klcc as compiler, and see what happens.  The purpose is not to
produce a better ash, only to find out how easy it is to use klcc
in an existing autoconf-based application.  Ash is a good candidate
for this kind of test because it has been ported before and is
included with klibc, so there's an example of how to get around
porting issues.

With some hacking, it turns out to be possible to build ash
with configure/make to a level where you have a running shell
that can invoke ls.  The changes to ash are quite sloppy and dump
core very easily, but could be cleaned up and distributed if
there's a pressing need for it.

There are also some points where a change in klibc would make it easier to
port existing software.  I cooked up some patches for this under 0.202;
they apply cleanly to 0.204.  The subject lines for these patches are
as follows:

 - dirent and extern define
 - klcc compatibility with gcc
 - select.h and extern define
 - signal.h
 - avoid size_t redefinition
 - sys/times.h

Looks like the new klcc will make it a lot easier to provide
klibc versions of existing packages :-)


More information about the klibc mailing list