similar to: kbuild improvements for klibc

klibc integrated with the kernel can now be found at: http://linux-sam.bkbits.net Se the repository: klibc. For non-BK users the patches can be retreived using the following links: klibc on top of 2.6.8-rc2: http://linux-sam.bkbits.net:8080/klibc/gnupatch@41098c67CQHEC6lH2E3rfIXcnRW1RA kbuild adaptions to klibc: http://linux-sam.bkbits.net:8080/klibc/gnupatch@4109923a7O1XqfXw_V7JzAmet_AzbA

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.

Hi Xen people, I can read in the Xen 3.0 Roadmap that "A port to IA64 is making good progress". I have found nothing about IA-64 support in the "bk://xen.bkbits.net/xeno-unstable.bk" repository. Could you tell if an advanced version for IA-64 is available and where the source files can downloaded from ? Regards Jean-Paul Pigache

Hi all, I'm a bit concerned about the following statement included in 2.6.0-test4: +For active users, you are better off using the klibc BitKeeper +repositories, at http://klibc.bkbits.net/ Since I refuse to use bk because I consider the anti-competition clause in the free bk license to (a) be abhorrent and (b) meaning that it's of at best questionable legality for me to use free BK,

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

There are two hosted BitKeeper repos: klibc is a BK clone of the klibc CVS tree 2.5-klibc is my attempts to integrate klibc into the kernel If you want commit access to either repo, send me an ssh1 public key. <b

BTW, the xenlinux-2.6.11.bk''s version is: ChangeSet@1.2085, 2005-05-12 11:10:24-06:00, djm@kirby.fc.hp.com More work on hyperprivops Signed-off-by: Dan Magenheimer <dan.magenheimer@hp.com> Thanks, Kevin >-----Original Message----- >From: xen-devel-bounces@lists.xensource.com >[mailto:xen-devel-bounces@lists.xensource.com] On Behalf Of Tian, Kevin >Sent: Friday,

Yes, like real Linux/ia64, it is not possible to run the same Xenlinux bits both on ski and on real hardware. A different configuration and build is required. The config difference is the same as it was with the privified xenlinux... I think you did that successfully before (with privified xenlinux) so give that config file a try and if it doesn''t work, let me know. BTW, I think I know

I''ve just finished Xeno-HOWTO which contains a detailed list of instructions on how to setting up Xen and XenoLinux, from downloading Bitkeeper, compilation of Xen, XenoLinux, tools to configuration, start and stop of new domains. A complete version has just been pushed in xeno.bk and xeno-1.1.bk in our Laboratory. A partital version is already available in

It's now in sync with 2.5.71. bk://klibc.bkbits.net/2.5-klibc <b

Hi hpa & others. Following is a list of issues that I hope to be addressed soon so we are in even better shape for -mm inclusion. 1) rebuild initramfs when content changes. > It is a simple matter of copying in usr/Makefile from the latest > -linus kernel and replace the 10 first lines with the content from > klibc Kbuild file. 2) havesyscalls.h is not deleted after make

This fixes a long standing issue where it was not possible to do "make usr/klibc/arch/x86_64/longjmp.o" in the kernel. The principle is that all .o files to be part of klibc are listed with klib-y. For each directory a klib.list file is made that specify all .o file and the final AR then adds all .o files to create libc.a. This patch introduce the infrastructure and converts x86_64 to

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

sparc still needs gcc-3.3 for a working run-init. belows makes use of the exported CC var. Signed-off-by: maximilian attems <maks@sternwelten.at> diff --git a/scripts/Kbuild.klibc b/scripts/Kbuild.klibc index 66e16e7..70e4071 100644 --- a/scripts/Kbuild.klibc +++ b/scripts/Kbuild.klibc @@ -72,7 +72,7 @@ KLIBCROSS := $(CROSS_COMPILE) # binutils KLIBCLD := $(KLIBCROSS)ld

If you only run released (rather than development) versions of rsync then you can skip this message. rsync's source tree has been converted from CVS to BitKeeper. This message contains brief instructions for people who want to track development or make contributions. I think it should take about 30-60 minutes to get started with BK. I hope you will agree that it is worthwhile. First

Hi, I've been messing around with the early userspace for the last couple days. What are the goals of early userspace? Is the end goal to use it as an initrd replacement or is it simply to do all the mounting (nfsroot, initrd, hard disk) that is currently done in init/do_mounts*? thanks mh -- Martin Hicks Wild Open Source Inc. mort@wildopensource.com 613-266-2296

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

Hello, I have attached a patch wich adds support for 4kb pages to xen 2.0 proper. (No changes were required from xen 2.0-beta. Apprently mixing xenolinux from one release and xen kernel from another release is a no-no. Other than that there were no problems. Thanks to Rupert Schlick for helping to nail it down. The "noacpi" parameter does not seem to be mandatory. Finally

hi, lately i try to download xen from bitkeeper - bk://xen.bkbits.net/xen-2.0.bk (ought to be version 2.0); but encounter a probelm when build from source. it has error as follow. the env is cygwin, gcc 3.3.3 and make 3.80 how to slove it? i appreciate any suggestion. sinrecely. jason ===============ERROR BEG ============ ac_timer.c:44: warning: alignment of `ac_timers'' is greater than

I've updated the BK klibc tree to reflect all of the recent flurry of activity. Complete CVS change history is preserved. http://klibc.bkbits.net/klibc <b