similar to: [PATCH] make install support

Hi folks, attached you can find a tiny patch for klibc-0.198 to get rid of the symbolic link pointing to the kernel sources, and to get rid of some obsolete rebuilds during incremental. Feel free to include it. Regards Harri -------------- next part -------------- diff -ur old/klibc-0.198/MCONFIG klibc-0.198/MCONFIG --- old/klibc-0.198/MCONFIG 2004-10-14 06:32:24.000000000 +0200 +++

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

this implements a ln(1) with -f and -s support. diff -p -purN klibc-0.112/utils/Makefile klibc-0.112.utils/utils/Makefile --- klibc-0.112/utils/Makefile 2004-02-21 23:49:26.000000000 +0100 +++ klibc-0.112.utils/utils/Makefile 2004-02-22 01:23:17.000000000 +0100 @@ -6,7 +6,7 @@ MAKEDEPS = -Wp,-MD,.$(subst /,-,$*). CFLAGS = $(MAKEDEPS) $(OPTFLAGS) $(REQFLAGS) -W -Wall LIBS =

Several people have run into problems when attaching large disk arrays to a mainframe because of running /sbin/hotplug as a bash script takes far longer than the interval between hotplug events. Attaching more than 300 devices at once will cause an out-of-memory condition and the kernel starts killing random processes. Running only udev instead of hotplug from the kernel is fast enough.

'rm -rf /' for klibc Doesnt comply to the standard, but does the job. http://www.opengroup.org/onlinepubs/009695399/utilities/rm.html diff -p -purN klibc-0.172/utils/Makefile klibc-0.172.rm/utils/Makefile --- klibc-0.172/utils/Makefile 2004-08-14 00:24:20.000000000 +0200 +++ klibc-0.172.rm/utils/Makefile 2004-09-05 20:11:14.109062216 +0200 @@ -6,7 +6,7 @@ MAKEDEPS = -Wp,-MD,.$(subst

Commit-ID: 47e429ec6c758b98a00e69df541448942c6f3ba3 Gitweb: http://git.kernel.org/?p=libs/klibc/klibc.git;a=commit;h=47e429ec6c758b98a00e69df541448942c6f3ba3 Author: Ben Hutchings <ben at decadent.org.uk> AuthorDate: Sat, 19 Jan 2019 22:47:18 +0000 Committer: Ben Hutchings <ben at decadent.org.uk> CommitDate: Sat, 19 Jan 2019 22:51:00 +0000 [klibc] Build and install shared

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

leroy christophe dixit: > So the only way I have found to be able to install klibc in /opt/klibc on the > development host and let it run properly from /lib on the target is with the > attached patch. And, again, your patch is wrong because this _seems_ to be by design, unless it?s by accident. > If I set prefix to / and INSTALLROOT to /opt/klibc, klcc is not able to find > the

leroy christophe dixit: > But I'm building a klibc/klcc for cross-compilation, and I don't need (and > don't want) a powerpc klibc.so in /lib in the middle of all other i386 libs. Of course you don?t. You?re just needing to set SHLIBDIR explicitly for this specific use case. > As I say above your answer, when I set prefix to /opt/klibc and SHLIBDIR to > /opt/klibc/lib,

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.

Le 19/08/2013 22:45, Neal Murphy a ?crit : > 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

linux-2.6 2ad780978b7c0c3e7877949f098cbd06e7c73839 cleaned up linux/nfsmount.h and thus a klibc build would produce this: > usr/kinit/nfsmount/mount.c:179: error: 'MNTPROC_MNT' undeclared (first use in this function) > usr/kinit/nfsmount/mount.c:179: error: (Each undeclared identifier is reported only once > usr/kinit/nfsmount/mount.c:179: error: for each function it appears

2ad780978b7c0c3e7877949f098cbd06e7c73839 broke klibc build MNTPROC_MNT and MNTPROC_UMNT no longer defined. usr/kinit/nfsmount/mount.c: In function ?mount_call?: usr/kinit/nfsmount/mount.c:179: error: ?MNTPROC_MNT? undeclared (first use in this function) usr/kinit/nfsmount/mount.c:179: error: (Each undeclared identifier is reported only once usr/kinit/nfsmount/mount.c:179: error: for each function

use AF_INET directly. Signed-off-by: maximilian attems <max at stro.at> --- usr/kinit/nfsmount/dummypmap.c | 2 +- usr/kinit/nfsmount/mount.c | 4 ++-- usr/kinit/nfsmount/sunrpc.c | 4 ++-- 3 files changed, 5 insertions(+), 5 deletions(-) diff --git a/usr/kinit/nfsmount/dummypmap.c b/usr/kinit/nfsmount/dummypmap.c index 43abe37..481e23b 100644 ---

Hi Bryan and other klibc people. I have taken a stamp on the Makefiles for klibc, this is what I came up with. 1) No longer recompile on every invocation 2) Correct checking on dependencies 3) Simpler makefile syntax (almost all over the place) I compile-time tested it only. Two open issues: a) Do we realy use .a files for initramfs. I renemed that to the executable. b) I renamed

Commit-ID: c4b811a1e4647224ddc717fac59900d16d0e9d4d Gitweb: http://git.kernel.org/?p=libs/klibc/klibc.git;a=commit;h=c4b811a1e4647224ddc717fac59900d16d0e9d4d Author: Baptiste Jonglez <baptiste.jonglez at imag.fr> AuthorDate: Thu, 14 Sep 2017 09:22:21 -0700 Committer: Ben Hutchings <ben at decadent.org.uk> CommitDate: Wed, 2 Jan 2019 03:08:04 +0000 [klibc] nfsmount: support

Without this patch gcc 4.6 warns: KLIBCCC usr/kinit/nfsmount/dummypmap.o usr/kinit/nfsmount/dummypmap.c: In function 'dummy_portmap': usr/kinit/nfsmount/dummypmap.c:191:13: warning: array subscript is below array bounds [-Warray-bounds] Signed-off-by: Greg Thelen <gthelen at google.com> --- usr/kinit/nfsmount/dummypmap.c | 2 +- 1 files changed, 1 insertions(+), 1 deletions(-)

There is a conflict in glibc between <linux/in.h> and <netinet/in.h>: one defines protocols with an enum, the other does the same, but adds a self-define for every enumerated value. #define IPPROTO_IP IPPROTO_IP This means the two cannot be mixed, and since loads of include files refer to <netinet/in.h>, effectively <linux/in.h> cannot be used with glibc. Since

The standard mount option nowadays to specify NFS version is "nfsvers", as documented in nfs(5) on modern Linux systems. Up to now, nfsmount only supported the old "v2" or "v3" boolean options. Extend option parsing to support both "nfsvers=X" and "vers=X", with X being equal to either 2 or 3 (nfsmount does not support NFSv4 at present). If both

I'm still pondering with kbuild and klibc. Next in line was to get ipconfig support in the kernel (build wise). A little challenge that is bigger than anticipated was to create a shared executable. This required a far bigger rewrite of Kbuild.klibc than originally planned. The good part is that I now managed to treat linking of objects with single and multiple .o files almost the same.