similar to: [patch] Kbuild don't hardcode gcc and binutils version

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

From: Maciej ?enczykowski <maze at google.com> This adds a new setting: KBUILD_REPRODUCIBLE If it is non-empty, ar and ranlib will be called in such a way that timestamps do not affect the build output. This allows one to get perfectly reproducible builds. Signed-off-by: Maciej ?enczykowski <maze at google.com> --- scripts/Kbuild.klibc | 14 +++++++++----- usr/klibc/Kbuild |

Basic infrastructure for building klibc. Signed-off-by: H. Peter Anvin <hpa at zytor.com> --- commit 5bba564a5c133369b3e83e5827d053a98cb3c59a tree 11f2acc1f9d845e8764fa790f522b79ea1106b80 parent 378abd8f4d39024ea6c87eb5b54155238f647f0d author H. Peter Anvin <hpa at zytor.com> Sun, 25 Jun 2006 16:58:08 -0700 committer H. Peter Anvin <hpa at zytor.com> Sun, 25 Jun 2006 16:58:08

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,

From: Stanislav Fomichev <sdf at google.com> Clang's lld prefers the use of "-image-base" instead of "-Ttext-segment". Signed-off-by: Stanislav Fomichev <sdf at google.com> Signed-off-by: Bill Wendling <morbo at google.com> --- Makefile | 3 +++ usr/klibc/arch/i386/MCONFIG | 2 +- usr/klibc/arch/mips64/MCONFIG | 2 +-

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

Hi, From the Makefile I figured that to build klibc where the kernel was built with O=/someotherdir, you need to do: make KLIBCKERNELOBJ=/someotherdir KBUILD_SRC=1 Everything seems fine though, but it fails to link dash with: ----- KLIBCCC dash/bltin/printf.o KLIBCCC dash/system.o KLIBCCC dash/bltin/test.o KLIBCCC dash/bltin/times.o KLIBCCC dash/var.o GEN dash/init.c KLIBCCC

Commit-ID: eaca2447991709cddfd8c42f3fa4a2e890d2cce8 Gitweb: http://git.kernel.org/?p=libs/klibc/klibc.git;a=commit;h=eaca2447991709cddfd8c42f3fa4a2e890d2cce8 Author: Bill Wendling <morbo at google.com> AuthorDate: Sun, 29 Mar 2020 04:38:31 -0700 Committer: Ben Hutchings <ben at decadent.org.uk> CommitDate: Sat, 25 Jul 2020 20:45:34 +0100 [klibc] Kbuild: support clang's

The following patchset implements 3 seperate series of changes. External Building ================= Patches 1 through 8 enable to use of klibc's build system while leaving the src tree pristine (and potentially read only). Specifically: - srctree=<Sources for klibc> - objtree=<Ouput directory for klibc> - KLIBCKERNELSRC=<Kernel sources> - KLIBCKERNELOBJ=<Kernel

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

Clang doesn't have a suitable replacement for libgcc readily available. Supply one that we know exists. Use "-fno-builtin-bcmp" to prevent clang from calling a function that doesn't exist. Signed-off-by: Bill Wendling <morbo at google.com> --- scripts/Kbuild.klibc | 2 ++ usr/klibc/arch/x86_64/MCONFIG | 2 ++ 2 files changed, 4 insertions(+) diff --git

Hi, I wanted to test the kinit setup on my configuration, and I found out that I'm unable to build using an external object directory (i.e. using O=../dir). I'm using the sources from the GIT tree. The first problem is in usr/dask/Kbuild, in the invocations of mktokens; with O= the build system will try to execute something like:

- Renamed IMAGE_BASE to LD_IMAGE_BASE_OPT. - Moved "-fcommon" to KLIBCREQFLAGS in scripts/Kbuild.klibc. - Remove "dash" warning fixes which have been upstreamed. - Conditionalize the inclusion of compiler flags by using the proper compiler name or "cc-option". - Added "-Werror" to "cc-option" to catch flags that cause warnings. - Retain

When I compile klibc on little-endian mips, I get: KLIBCLD klibc/libc.so ld: klibc/arch/mips/crt0.o: compiled for a little endian system and target is big endian ld: klibc/arch/mips/crt0.o: endianness incompatible with that of the selected emulation ld: failed to merge target specific data of file klibc/arch/mips/crt0.o When I change "elf32-tradbigmips" to

LLD uses "-R" as an alias for "-rpath", while LD uses "-R" as an alias for "--just-symbols". Use "--just-symbols" so that it's correctly supported for both linkers. See Linux commit 3c1918c8f54166598195d938564072664a8275b1 (riscv: fix vdso build with lld). Signed-off-by: Bill Wendling <morbo at google.com> --- scripts/Kbuild.klibc | 2

On Wed, Jul 23, 2008 at 11:24:49AM +0200, Karel Zak wrote: > On Wed, Jul 23, 2008 at 04:43:30AM -0400, Christoph Hellwig wrote: > > On Wed, Jul 23, 2008 at 10:39:38AM +0200, maximilian attems wrote: > > > klibc mount has only short options thus uses the following syntax > > Frankly, it seems like a klibc problem... well not directly, but right klibc-utils should have

-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:

new klibc sparc build failure against gcc 4.2 ----- Forwarded message from Kilian Krause <kilian at debian.org> ----- Subject: Bug#440721: FTBFS on sparc while linking usr/klibc/libc.so From: Kilian Krause <kilian at debian.org> To: Debian Bug Tracking System <submit at bugs.debian.org> Date: Mon, 03 Sep 2007 23:35:23 +0200 Package: klibc Version: 1.5.6-2 Severity: serious

Hi, I just got a bug report that klibc doesn't compile on s390: KLIBCCC usr/klibc/libgcc/__clzsi2.o KLIBCCC usr/klibc/libgcc/__clzdi2.o usr/klibc/libgcc/__clzdi2.c: In function `__clzdi2': usr/klibc/libgcc/__clzdi2.c:24: warning: implicit declaration of function `__builtin_clz' This looks like a common problem, because __builtin_clz is available since gcc 3.4, while the kernel

Hi. HOSTCC should be used to set HOSTCFLAGS instead of CC. There is a case where HOSTCC doesn''t accept -Wdeclaration-after-statement, while CC does. It results in a compilation error. This patch fixes it Signed-off-by: Isaku Yamahata <yamahata@valinux.co.jp> -- diff -r 94cb428d363d -r 164e8408c67a Config.mk --- a/Config.mk Mon Dec 12 15:20:51 2005 +0900 +++ b/Config.mk Mon Dec