similar to: [PATCH] make DEBUG=true

--- ../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

The *.shared targets require -shared on powerpc, and -R leads to linker errors. This patch makes the -R an arch define. ia64 at least requires -R. --- ash/Makefile +++ ash/Makefile 2003/11/27 15:04:02 @@ -36,7 +36,7 @@ $(STRIP) $(PROG) $(PROG).shared: $(OBJS) $(LIBS) - $(LD) $(LDFLAGS) -o $(PROG).shared -e main $(KLIBSRC)/interp.o $(OBJS) -R $(KLIBSRC)/libc.so $(LIBGCC) + $(LD) $(LDFLAGS)

In klibc-0.114, any shell script like this: ====================================================================== #!/path/to/klibc-0.114/ash/sh echo hi ====================================================================== ...elicits the following error when executed: /var/tmp/hack.sh: Can't open /var/tmp/hack.sh Running under strace, I get: execve("/var/tmp/hack.sh",

On Mon, Feb 24, 2003 at 05:26:32PM -0800, H. Peter Anvin wrote: > Greg has taken on the job of integrating klibc with the kernel, but > please post klibc bug reports to the klibc mailing list at > <klibc@zytor.com>. To avoid annoying warning from gcc I had to check for compatibility with -falign-* like we do in arch/i386/Makefile. check_usergcc located in top-level makefile to

To make it more obvious where the files are supposed to end up move files so they reflect the directory structure in the kernel: mkdir scripts mv kernel/Kbuild.* scripts/ mkdir usr mv kernel/Kbuild usr rmdir kernel Furthermore: - updated cp-to-kernel to refelct new directory layout - teach cp-to-kernel to place gzip right under usr/ - Add '#' in front of comment in usr/Kbuild --- I

Though most people do have which installed somewhere. --- klibc/Makefile.orig 2005-04-08 18:34:56.827117248 +0200 +++ klibc/Makefile 2005-04-08 18:36:08.000297280 +0200 @@ -18,12 +18,12 @@ echo 'ARCH=$(ARCH)' >> $@ echo 'CROSS=$(CROSS)' >> $@ echo 'KCROSS=$(KCROSS)' >> $@ - echo "CC=$(shell bash -c 'type -p

Following patch improves integration with kbuild. With a future kernel (2.6.14-rc) it now has working support for 'make clean'. Included is an example of how to compile an early userspace program. I selected gzip as the most simple one for this - and left out all the links to different names (gunzip etc.) Before proceeding with this I need some inputs on what functionality is required by

From: Matt Fleming <matt.fleming at linux.intel.com> Move the MCONFIG files into a mk/ directory and give them more descriptive names. This is purely a cosmetic change to make the 'include' directives a bit more coherent by making it obvious exactly which MCONFIG file we're including. For example, in com32/lua/src/Makefile we exchange the line, include ../../MCONFIG for the

I have the following toolchain: $ ld --version GNU ld version 2.15.90.0.3 20040415 $ gcc --version gcc (GCC) 3.3.2 I attempted to build klibc with this toolchain. It builds without errors, but the included "ash" shell does not function properly. Testcase: read cmdline </proc/cmdline echo $cmdline The first command prints a message: cannot open /proc/cmdline: error 14 Other

This patch allows klibc to build on parisc64 platforms. $ diff -u MCONFIG.old MCONFIG --- MCONFIG.old 2005-06-18 01:16:12.000000000 +0000 +++ MCONFIG 2005-06-18 01:18:51.000000000 +0000 @@ -33,7 +33,7 @@ KLIBCVER = -D__KLIBC__=$(shell cut -d. -f1 < $(SRCROOT)/version) \ -D__KLIBC_MINOR__=$(shell cut -d. -f2 < $(SRCROOT)/version) -ARCH = $(shell uname -m | sed -e

Commit-ID: 95a3123c94abc28c65f33c9589693dde9f140fe1 Gitweb: http://git.kernel.org/?p=libs/klibc/klibc.git;a=commit;h=95a3123c94abc28c65f33c9589693dde9f140fe1 Author: Ben Hutchings <ben at decadent.org.uk> AuthorDate: Sat, 29 Aug 2020 22:29:52 +0100 Committer: Ben Hutchings <ben at decadent.org.uk> CommitDate: Sat, 29 Aug 2020 22:53:10 +0100 [klibc] Kbuild, klcc: Support

Commit-ID: f24c4d725f5b178d1027dca14203f57e8e78a34d Gitweb: http://git.kernel.org/?p=libs/klibc/klibc.git;a=commit;h=f24c4d725f5b178d1027dca14203f57e8e78a34d Author: Ben Hutchings <ben at decadent.org.uk> AuthorDate: Tue, 19 Feb 2019 02:31:39 +0000 Committer: Ben Hutchings <ben at decadent.org.uk> CommitDate: Tue, 19 Feb 2019 02:31:39 +0000 [klibc] klcc: Enable stripping

Commit-ID: 72fea69b91bdc8981d958984bc78401a08f8aff5 Gitweb: http://git.kernel.org/?p=libs/klibc/klibc.git;a=commit;h=72fea69b91bdc8981d958984bc78401a08f8aff5 Author: Ben Hutchings <ben at decadent.org.uk> AuthorDate: Fri, 1 Feb 2019 16:00:20 +0000 Committer: Ben Hutchings <ben at decadent.org.uk> CommitDate: Sat, 2 Feb 2019 00:09:23 +0100 [klibc] README.klibc: Replace list

Below is a patch to get rid of several warnings which occur while building syslinux 3.07 with the current gcc 4 snapshot. This fixes all the warnings except one unused variable. Take them or leave them as you see fit. They're all com32 stuff that's pulled in from external sources. --- syslinux-3.07/memdisk/unzip.c.gcc4 2004-12-07 23:29:22.000000000 -0500 +++

Factor out all kernel specific path's (those containing usr/) into two variables: KLIBSRC + KLIBINC. Set the variables in a kernel spcific Kbuild file. Sam commit e6f989c1597a837f4aecbd11083697184c089611 tree 93f88d7564bb9e4d4bc95fd455b842d0bd0fdc54 parent 8151f4a98f82fba4fe3b949f49da4ab8bba71501 author Sam Ravnborg <sam@mars.(none)> Thu, 28 Jul 2005 23:36:07 +0200 committer Sam

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.

On Wed, Sep 15, 2004 at 10:48:02AM +0930, Alan Modra wrote: > After using SHAREDFLAGS = -Ttext 0x0f000200 on ppc64 (which I see you > suggested in another email), I see the problem you're talking about. > > klibc is fundamentally broken on ppc64. You just can't call into > another chunk of code (klibc.so in this case) which has a separate toc > and expect things to

klibc now runs on the CRIS archtitecture. The patch below is against 0.146. Most of the changes are trivial but the new files in libgcc requires some comments. __negdi2.c: The CRIS port fallbacks to C-code for negdi2. The code in __negdi2.c is copied from libgcc2.c but with modified typenames. I would really appreciate if someone could check if it seams sane. crisarith.c: CRIS has no built-in

The parts of klibc specific to the i386 architecture. Signed-off-by: H. Peter Anvin <hpa at zytor.com> --- commit bd0599e5290ca1a16bb7a68f7c362d395c612eb3 tree 8f33afdd02a14c22e7a3984da2bad13184e3f729 parent 84f6a72f42cf41e32daa59871a0b5424572093e4 author H. Peter Anvin <hpa at zytor.com> Sun, 25 Jun 2006 16:58:21 -0700 committer H. Peter Anvin <hpa at zytor.com> Sun, 25 Jun

This patch make it possible to run udev with the latest klibc. One patch for the udev/Makefile to match the moved include/ dir. Another one for klibc's string fuctions, that are causing segfaults: strncpy.c: the while() gets n == -1 and memset() dies strncat.c: cat's only strlen(dest) count of chars from src to dest Thanks, Kay -------------- next part -------------- ===== Makefile