klibc - Apr 2003 - A few questions

I've spent some time looking at klibc today, and find myself in a state
of some puzzlement.

The 0.79 snapshot does not build against 2.5.68; it fails almost
immediately, apparently due to problems with include files.

I'm hesitant to try patching anything to get it building, because I can
find no sign of a CVS or BK repo that I can check against, and I don't
want to replicate janitorial work that's already been done.

Does there exist a CVS or BK repo somewhere that is anonymously
accessible and has seen some maintenance since 0.79?  If I generate some
patches, should I be sending them here, or to HPA?

	<b

Bryan O'Sullivan wrote:
> I've spent some time looking at klibc today, and find myself in a state
> of some puzzlement.
> 
> The 0.79 snapshot does not build against 2.5.68; it fails almost
> immediately, apparently due to problems with include files.
> 
What compiler are you using, and what other info?  I've heard this from 
gregkh too, and I can't reproduce it.
> I'm hesitant to try patching anything to get it building, because I can
> find no sign of a CVS or BK repo that I can check against, and I don't
> want to replicate janitorial work that's already been done.
> 
> Does there exist a CVS or BK repo somewhere that is anonymously
> accessible and has seen some maintenance since 0.79?  If I generate some
> patches, should I be sending them here, or to HPA?
There is a cvs repo on kernel.org you can download via rsync.

	-hpa

Bryan O'Sullivan wrote:
> I've spent some time looking at klibc today, and find myself in a state
> of some puzzlement.
> 
> The 0.79 snapshot does not build against 2.5.68; it fails almost
> immediately, apparently due to problems with include files.
> 
Oh yes, can you post the actual error message, please?

	-hpa

Bryan O'Sullivan wrote:
> I've spent some time looking at klibc today, and find myself in a state
> of some puzzlement.
> 
> The 0.79 snapshot does not build against 2.5.68; it fails almost
> immediately, apparently due to problems with include files.
> 
> I'm hesitant to try patching anything to get it building, because I can
> find no sign of a CVS or BK repo that I can check against, and I don't
> want to replicate janitorial work that's already been done.
> 
I just made a new snapshot 0.80 as of the current CVS tree.

	-hpa