similar to: klibc.org domain available, if anyone wants it

Hi hpa and others. With my ongoing work to prepare for potential integration of klibc in the kernel I wonder if there wold be any interest in using part of the kbuild infrastructure to build the vanilla klibc? The rationale is obvious: - common codebase for Kbuild files, so one only has to fix things in one place - I force klibc developers to create Kbuild files usable in the kernel - Much

I put together a spec file that appears to build binary RPMs quite happily. Binary packages for i386 are available at http://www.terminus.com/~bos/klibc To build RPMs, just type "make rpm" in the top-level directory of CVS head or today's CVS snapshot. The packaging mechanism isn't exactly the same as the usual "build an RPM from a SRPM" scheme, as it builds in place

Hi , One of the things I am working on requires me to have a kernel and an initrd (as root filesystem , based on busybox) in one single image. I am trying to use initramfs for this, but there are a few things that I just can't figure out. As a test, I made a cpio archive of my own for the kernel source (plain 2.6.0-test5). Everything gets unpacked just fine during boot. Somehow I was

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

Hi, Andrew - Looks like a recent change you fed to Linus broke the klibc build as of 2.5.71. Can you pass this fix along, please? ===== include/linux/bitops.h 1.4 vs edited ===== --- 1.4/include/linux/bitops.h Thu Jun 5 23:37:30 2003 +++ edited/include/linux/bitops.h Sat Jun 14 22:02:01 2003 @@ -108,7 +108,7 @@ return (res & 0x0F) + ((res >> 4) & 0x0F); }

Hi, Greg - I have a 2.5.70 BK repository, with klibc integrated, at: bk://klibc.bkbits.net/2.5-klibc This repo has the following features: * Completely up-to-date w.r.t. klibc itself. * Kbuild sort of happy, but still needs an eyeball from Kai to figure out why it always rebuilds everything in usr/. * Supports both IP autoconfig and NFS root from initramfs.

I've checked in an in-progress nfsmount program. It can mount over TCP from a v2 server right now. More to come. It's currently 17K stripped. By the way, the klibc-cvs notifier seems to have died again. <b

This seem to be a good timing taking up the integration of klibc in the kernel again. Based one klibc-0.152 and klibc.bkbits.net/2.5-klibc I will take a shot of it. I will focus on getting the library compiled (should be pretty straighforward). Next two steps are: 2) Adding minimum applications to the kernel (if any) 3) Support applications outside the kernel I will put my work on bkbits.net

Another post-2.5.68 one. The cramfs header defines u8, so we must quiet it down. <b diff -Nru a/utils/fstype.c b/utils/fstype.c --- a/utils/fstype.c Mon Apr 28 15:10:56 2003 +++ b/utils/fstype.c Mon Apr 28 15:10:56 2003 @@ -19,7 +19,9 @@ #include <asm/byteorder.h> #include <linux/romfs_fs.h> +#define __KERNEL__ #include <linux/cramfs_fs.h> +#undef __KERNEL__ #include

Sort of a brown paper headgear issue. <b diff -Nru a/ipconfig/netdev.c b/ipconfig/netdev.c --- a/ipconfig/netdev.c Mon Apr 28 15:26:12 2003 +++ b/ipconfig/netdev.c Mon Apr 28 15:26:12 2003 @@ -205,7 +205,7 @@ if (netdev_gif_addr(&ifr, SIOCGIFADDR, &dev->ip_addr) == -1) { perror("SIOCGIFADDR"); dev->ip_addr = 0; - dev->ip_broadcase = 0; +

Bryan O'Sullivan wrote: > Update of /home/cvs/klibc/klibc/klibc/arch/i386 > In directory terminus.zytor.com:/tmp/cvs-serv27981/klibc/arch/i386 > > Modified Files: > MCONFIG > Log Message: > Bring sanity to OPTFLAGS. Turn off -fomit-frame-pointer, which is worse > than useless, and use new names for other directives. > This unfortunately breaks older compilers.

Commit-ID: b3726254f4b33e08b7e3ffd21a8bca857758aabf Gitweb: http://git.kernel.org/?p=libs/klibc/klibc.git;a=commit;h=b3726254f4b33e08b7e3ffd21a8bca857758aabf Author: Rink Springer <rink at rink.nu> AuthorDate: Fri, 2 Feb 2018 08:44:55 +0100 Committer: Ben Hutchings <ben at decadent.org.uk> CommitDate: Fri, 25 Jan 2019 02:57:21 +0000 [klibc] expand: Remove dependency on

Commit-ID: be47d99b3d05ea898412536d717a15d80cd8b68f Gitweb: http://git.kernel.org/?p=libs/klibc/klibc.git;a=commit;h=be47d99b3d05ea898412536d717a15d80cd8b68f Author: Rink Springer <rink at rink.nu> AuthorDate: Fri, 2 Feb 2018 08:44:55 +0100 Committer: Ben Hutchings <ben at decadent.org.uk> CommitDate: Sat, 28 Mar 2020 21:42:54 +0000 [klibc] dash: expand: Remove dependency on

On Sun, 2003-05-25 at 17:07, Kai Germaschewski wrote: > I basically did a complete integration of klibc into kbuild two or so > months ago - however, I didn't touch it since, so it won't apply cleanly. > I can dig out the bk tree, if you're interested. I've put my own latest integrate-klibc-into-kbuild BK patch up at

Hi, Greg - The latest set of klibc work is all accessible from http://www.speakeasy.org/~bos Here's a brief description of each part. The patches are as independent as possible, and are in BitKeeper format. * ipconfig-2.5.69.patch removes ipconfig from the kernel, and prevents CONFIG_ROOT_NFS from working. * nfsroot-2.5.69.patch removes nfsroot from the kernel. *

Last patch for now. This gets gen_init_cpio into a state where it can pick up a "kinit" binary from usr and stuff it into the cpio archive as /sbin/init. This is obviously a crock, but it suffices for testing until something sane is done about integrating klibc into the kernel tree. The patch also adds a bit of instrumentation to initramfs.c, to try to help flush out bug 740.

Hi, Andrew - The ext3-0.0.6 patch doesn't build if CONFIG_JBD_DEBUG is set and CONFIG_BUFFER_DEBUG is not set, because include/linux/buffer-trace.h is missing a definition for BUFFER_TRACE2 in one branch of a #ifdef. One-liner patch appended. <b

Jon Harrop wrote: > If you are familiar with functional programming and, in particular, its > benefits in the context of compiler work then you might like to use Gordon's > OCaml bindings to LLVM that are bundled with LLVM. They are very easy to use > and will make subsequent work vastly easier than trying to write everything > in C++. Or, indeed, the Haskell bindings

Commit-ID: 9d8d648e604026b32cad00a84ed6c29cbd157641 Gitweb: http://git.kernel.org/?p=libs/klibc/klibc.git;a=commit;h=9d8d648e604026b32cad00a84ed6c29cbd157641 Author: Ben Hutchings <ben at decadent.org.uk> AuthorDate: Sat, 29 Feb 2020 00:03:20 +0000 Committer: Ben Hutchings <ben at decadent.org.uk> CommitDate: Sat, 29 Feb 2020 00:11:26 +0000 [klibc] Kbuild: Tell gas we

Commit-ID: 312b3d0a38ff2e43becd47cf1f4a930bc0c4b8e6 Gitweb: http://git.kernel.org/?p=libs/klibc/klibc.git;a=commit;h=312b3d0a38ff2e43becd47cf1f4a930bc0c4b8e6 Author: Ben Hutchings <ben at decadent.org.uk> AuthorDate: Wed, 29 Apr 2020 22:24:33 +0100 Committer: Ben Hutchings <ben at decadent.org.uk> CommitDate: Sat, 25 Jul 2020 17:33:29 +0100 Revert "[klibc] Kbuild: Tell