similar to: klibc compilation breakage on 2.6.8+

Hello, can someone direct me to a code sample showing usage of sys_clone on IA64 ? I use that syscall in the multipathd daemon, and I received compilation errors from IA64 pepole. As I don't have hardware to play with, I'd appreciate guidance. regards, -- christophe varoqui <christophe.varoqui@free.fr>

Hello, I maintain the multipath tools, some of which are intended to be packed into early userspace. I had to drop a klibc tree into the tools archive for that, like GregKH does for udev. I don't like it, because tarballs are bigger than they should be and it brings more maintenance. Recently, scsi_id became a required multipath dependency. scsi_id is currently build with glibc and I need a

Hello, I would like to know if initrd is here to stay, now that klibc and initramfs are ready. As the multipath-tools maintainer, I'm facing the choice to 1) put the multipath configuration tool in the initrd * dynamic binary is possible * storage hba drivers as modules loaded * no klibc limitations (no mntent for libsysfs ...) 2) put the multipath configuration tool in the initramfs *

Hi, is there a DD-accessible porterbox somewhere (slow would be ok, as this is smallish software) with an up-to-date sid (enough to install the recently-built libklibc-dev 2.0~rc5-1 and all other B-D of mksh 40.9.20120518-1, as well as strace and gdb-minimal)? Similarily to http://www.zytor.com/pipermail/klibc/2012-May/003229.html I found klibc-compiled programmes on Alpha to fail (SIGSEGV

Kay Sievers wrote: > Hi, > this simple program compiled with klibc: > > #include <stdio.h> > int main(int argc, char* argv[]) > { > setenv("TESTENV", "happy", 1); > printf("TESTENV='%s'\n", getenv("TESTENV")); > } > > prints: > > ./env > TESTENV='(null)' > >

--- ../multipath-tools-0.2.8.1/klibc/klibc/arch/i386/MCONFIG 2004-07-20 10:51:42.000000000 +0200 +++ klibc/klibc/arch/i386/MCONFIG 2004-07-27 17:10:12.000000000 +0200 @@ -13,7 +13,7 @@ # them to be cdecl # REGPARM = -mregparm=3 -DREGPARM -gcc_major := $(shell $(CC) -v 2>&1 | awk '/gcc version/{print int($$3)}') +gcc_major := $(shell unset LANG;$(CC) -v 2>&1 | awk

Hi, I've already submitted the attached patch to the Debian BTS: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=480994 Basically it fixes the argument parsing when running something like "mount -t ext3,ext2...". If that is fixed, I assume that "-t auto" could also be faked by replacing auto with a long list of fs types (or running "fstype" in the

Le 21/08/2013 17:36, leroy christophe a ?crit : > > Le 21/08/2013 17:15, maximilian attems a ?crit : >> On Wed, Aug 21, 2013 at 01:39:50PM +0200, leroy christophe wrote: >>> Le 21/08/2013 12:20, maximilian attems a ?crit : >>>> On Tue, Aug 20, 2013 at 07:44:39AM +0200, leroy christophe wrote: >>>>> Find attached two patches I have in order to build

Le 22/08/2013 07:43, leroy christophe a ?crit : > Le 22/08/2013 00:59, Thorsten Glaser a ?crit : >> leroy christophe dixit: >> >>> Also you can see that it does try to create /lib instead of >>> /tmp/klibc-install/lib hence my second patch. >> That actually seems to be by design. I always set >> SHLIBDIR on the make command line, so it overrides that.

On Wed, Aug 21, 2013 at 06:48:08PM +0200, maximilian attems wrote: > On Wed, Aug 21, 2013 at 06:03:41PM +0200, leroy christophe wrote: > > > > Note that step B is working well. > > It is step C, the 'make install', which fails. > > right, it is the toplevel Makefile one needs to poke for the target. > see belows proper patch: >From

On Wed, Aug 21, 2013 at 01:39:50PM +0200, leroy christophe wrote: > > Le 21/08/2013 12:20, maximilian attems a ?crit : > >On Tue, Aug 20, 2013 at 07:44:39AM +0200, leroy christophe wrote: > >>Find attached two patches I have in order to build klibc 2.0.2 > >>against kernel 3.8.13 > >>We had to introduce those patches when going from kernel 3.6 to kernel 3.7

leroy christophe dixit: > Also you can see that it does try to create /lib instead of > /tmp/klibc-install/lib hence my second patch. That actually seems to be by design. I always set SHLIBDIR on the make command line, so it overrides that. bye, //mirabilos -- > Wish I had pine to hand :-( I'll give lynx a try, thanks. Michael Schmitz on

Le 22/08/2013 14:36, Thorsten Glaser a ?crit : > leroy christophe dixit: > >> If I set prefix to / and INSTALLROOT to /opt/klibc, klcc is not able to find >> the include files >> If I set prefix to /opt/klibc and SHLIBDIR to /opt/klibc/lib, it is the target >> that tries to load klibc.so from /tmp/klibc-install/lib instead of /lib > INSTALLROOT is some sort of

In case people here don't follow the udev mailing list, udev seems to be quasi-dropping klibc support. Well, see the forwarded message below. As I don't agree with the "omg udev is complex! use glibc!" rationale, I want klibc and udev to remain working with each other.... Assuming some minor breakage in the near future, is klibc open to accepting patches for "basic C

Dear FreeBSD Community, OpenSVC has is now available for FreeBSD. OpenSVC is a GPLv2 project automating the low-level operations needed 1/ to bring up system resources (virtual machine container, ip, disk groups, filesystem mounts, application launchers) on a node and 2/ to replicate data to secondary nodes (in local or remote sites). OpenSVC can be coupled to a tiers heartbeat daemon to form a

Okay, as of this point, I think klibc is in quite good shape; my testing so far is showing that it can be used as a drop-in replacement for the kernel root-mounting code. That being said, there is guaranteed to be breakage, for two reasons: a. There are several architectures which don't have klibc ports yet. Since I don't have access to them, I can't really do them, either.

Commit 8418552 ("[klibc] ia64: Fix shared build") missed this use of the GP register, although the code appears to have been dubious anyway, assuming the address of errno was the first thing pointed to by GP. --- usr/klibc/arch/ia64/vfork.S | 6 +----- 1 file changed, 1 insertion(+), 5 deletions(-) diff --git a/usr/klibc/arch/ia64/vfork.S b/usr/klibc/arch/ia64/vfork.S index

Hello! I have encountered a problem when building shared klibc with recent binutils versions - apparently the breakage happened since binutils 2.17.50.0.2 due to the following change: http://sources.redhat.com/ml/binutils/2006-05/msg00279.html http://sourceware.org/ml/binutils/2006-05/msg00466.html --- a/binutils/bfd/elf64-x86-64.c +++ b/binutils/bfd/elf64-x86-64.c @@ -3630,7 +3630,8 @@ static

Gauche as it may be, I am reviving an old thread from January: http://www.zytor.com/pipermail/klibc/2013-January/003402.html. Building Smoothwall Express 3.1 in a chroot jail works well. (gcc 4.7.2, linux 3.4.58, klibc 2.0.1, et alia). I'm now working on 'express-next' to prepare for a future release (linux 3.10.7, klibc 2.0.2, et alia). Same build system, worked through some

-fcommon is not default anymore, with GCC 10 you get the following failure without it: KLIBCLD usr/klibc/libc.so ppc-linux-ld: usr/klibc/globals.o:/root/packages/klibc-2.0.7/usr/klibc/../include/unistd.h:15: multiple definition of `environ'; usr/klibc/__shared_init.o:/root/ldb_base/ofl/packages/klibc-2.0.7/usr/klibc/libc_init.c:42: first defined here ppc-linux-ld: