similar to: klibc and cross-compilation

hello hpa, please review this unsorted patch queue, as I wasn't sure about them they didn't land yet in todays pull request. thanks max git clone git://git.debian.org/users/maks/klibc.git test Thomas B?chler (1): klcc: compile shared by default jeremy buisson (1): [klibc] sparc64: fix bad 32 bits socket syscalls maximilian attems (1): [klibc] add losetup utils the

Hello, in OpenEmbedded we build kexec-tools and kexecboot statically linked against klibc. So we gathered some patches for klibc_1.5.15 here: http://cgit.openembedded.org/cgit.cgi/openembedded/tree/recipes/klibc Patches and utils have been added (wc, losetup, modprobe) as well as fs-detection for vfat and jffs2. Perhaps someone can find something useful... We are waiting for the 1.5.16 release

Hi, I am trying to setup an environment where I can build external projects against klibc. It works - except if I have a program that links to libc. Then I get a multiple definition of `_start' message. Here is a simple test case. Jon [ringlej at ringlejxbuild ~/temp/klibc-test]$ cat klibc-test.c #include <stdio.h> int main(void) { printf("hello world"); } [ringlej

Could we publish an Alpine package for libklibc-dev, to make it easier for embedded developers to obtain klcc? -- Cheers, Andrew -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://www.zytor.com/pipermail/klibc/attachments/20170414/d86fc964/attachment.html>

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

Hi Currently I am trying to get device-mapper and dmraid ported to compile against klibc. So far there was no real issues, as the only thing they used was fscanf and feof not available presently in klibc (but easy to work around). Other than that there are really no way to easily check for installed klibc's other than trying to mangle the output of klcc (from adjusted configure.in): -----

Commit-ID: 7752eb456addbd1973e9c6b609294ccef89a65a2 Gitweb: http://git.kernel.org/?p=libs/klibc/klibc.git;a=commit;h=7752eb456addbd1973e9c6b609294ccef89a65a2 Author: Ben Hutchings <ben at decadent.org.uk> AuthorDate: Thu, 20 Aug 2020 21:48:07 +0100 Committer: Ben Hutchings <ben at decadent.org.uk> CommitDate: Thu, 20 Aug 2020 21:50:09 +0100 [klibc] klcc: Treat CC, LD, STRIP

Commit-ID: 23273aa05bdc564eb8ff0565d9df9c3edfffaee9 Gitweb: http://git.kernel.org/?p=libs/klibc/klibc.git;a=commit;h=23273aa05bdc564eb8ff0565d9df9c3edfffaee9 Author: Olliver Schinagl <oliver at schinagl.nl> AuthorDate: Sat, 25 Jul 2020 10:59:01 +0200 Committer: Ben Hutchings <ben at decadent.org.uk> CommitDate: Sun, 26 Jul 2020 00:16:13 +0100 klcc: Remove the need for bash

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

On Sat, 31 Dec 2011, Aurelien Jarno wrote: > s390 and s390x are sharing the same include files, in > /usr/lib/klibc/include/arch/s390. However klcc seatches for the s390x > includes in /usr/lib/klibc/include/arch/s390x, which doesn't exist. > > The patch below fixes the issue by using the ARCHDIR variable instead > of the ARCH one in klcc. It's one possible fix,

Commit-ID: 994adfcbd9bfcb45967b834c962db20b875fbd6c Gitweb: http://git.kernel.org/?p=libs/klibc/klibc.git;a=commit;h=994adfcbd9bfcb45967b834c962db20b875fbd6c Author: Greg Thelen <gthelen at google.com> AuthorDate: Sun, 25 Feb 2018 23:16:35 -0800 Committer: Ben Hutchings <ben at decadent.org.uk> CommitDate: Wed, 2 Jan 2019 03:08:04 +0000 [klibc] remove some 'make -s'

Anil Singhar dixit: >Manual testing as provided within the package has been done with all tests >passing. This includes the units tests available under usr/klibc/tests, >usr/utils, usr/dash and usr/gzip. For dash and gzip, only sanity testing >has been done. It?s *massively* recommended to try to build mksh against klibc then run mksh?s testsuite, since it?s proven, time and time

Commit-ID: 6888a69d8735e508d62285c613fc521d418c30a1 Gitweb: http://git.kernel.org/?p=libs/klibc/klibc.git;a=commit;h=6888a69d8735e508d62285c613fc521d418c30a1 Author: Greg Thelen <gthelen at google.com> AuthorDate: Sun, 25 Feb 2018 23:16:34 -0800 Committer: Ben Hutchings <ben at decadent.org.uk> CommitDate: Wed, 2 Jan 2019 03:08:04 +0000 [klibc] use more consistent quoting

Commit-ID: c76d1e32379835dcc0e66c8874b0a384bf1ac5cf Gitweb: http://git.kernel.org/?p=libs/klibc/klibc.git;a=commit;h=c76d1e32379835dcc0e66c8874b0a384bf1ac5cf Author: Ben Hutchings <ben at decadent.org.uk> AuthorDate: Sun, 6 Jan 2019 21:11:05 +0000 Committer: Ben Hutchings <ben at decadent.org.uk> CommitDate: Fri, 18 Jan 2019 03:10:14 +0000 [klibc] Makefile: Add dependencies

Commit-ID: 547065c81db978d1c3ddd26d495dd7d29fa9bcca Gitweb: http://git.kernel.org/?p=libs/klibc/klibc.git;a=commit;h=547065c81db978d1c3ddd26d495dd7d29fa9bcca Author: Ben Hutchings <ben at decadent.org.uk> AuthorDate: Wed, 6 Jan 2016 01:19:55 +0000 Committer: H. Peter Anvin <hpa at linux.intel.com> CommitDate: Tue, 5 Jan 2016 17:50:46 -0800 [klibc] Install headers with

Commit-ID: 0959d3e5a37096f4f110362b46cd7ecc678bf44c Gitweb: http://git.kernel.org/?p=libs/klibc/klibc.git;a=commit;h=0959d3e5a37096f4f110362b46cd7ecc678bf44c Author: Ben Hutchings <ben at decadent.org.uk> AuthorDate: Fri, 1 Feb 2019 23:51:24 +0100 Committer: Ben Hutchings <ben at decadent.org.uk> CommitDate: Sat, 2 Feb 2019 00:09:23 +0100 [klibc] Makefile: Check for

With some hacks kexec-tools can compile against klibc. On the klibc side only this syscall addition is missing. The patch has been carried in OpenEmbedded klibc for some time. Signed-off-by: Thomas Kunze <thommycheck at gmx.de> Signed-off-by: Yuri Bushmelev <jay4mail at gmail.com> Signed-off-by: Andrea Adami <andrea.adami at gmail.com> Signed-off-by: maximilian attems <max at

Hi Ben, *massive* thanks for picking up klibc work. This might motivate me to pick up some of the TODOs for it that have piled on in my TODO (but only after the freeze, I?m sorry to say, I have more to do for other packages). >And I spotted another test program that has this property (setjmptest setjmp is a good topic? I found that building mksh and running its testsuite is a good test to

kbuild: add klibc/tests to kbuild Add a kbuild file so we now can build the test programs. A new dedicated target is used: make test Signed-off-by: Sam Ravnborg <sam@ravnborg.org> --- commit 5492ae07007399d8838dea5f44b3d9cf3603abc3 tree 4339d2d3aa0e80bc81ac0cd8ca3b7c89486b2150 parent 64dda666c087b6e537892ac9984aff57d2b32c47 author Sam Ravnborg <sam@mars.(none)> Sun, 07 Aug 2005

Compilation was ok with klibc-1.5.10 on linux-2.6.25. Distrib does not matter as it is inside a chroot a la LSF With the upgrade to linux-2.6.27 it broke on 1.5.10 (I try too the last 1.5.14) with make[1]: Entering directory `/usr/src/klibc-1.5.14' GEN klcc/klibc.config GEN klcc/klcc HOSTCC scripts/basic/fixdep KLIBCCC usr/klibc/__static_init.o KLIBCCC usr/klibc/vsnprintf.o