similar to: klibc 2.0.2 doesn't compile with kernel 3.7.x

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

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

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

I've run into a problem with building klibc with high parallelism It's not quite predictable, but at a -j of approx 25-30 or more (on a 24 hyperthreaded machine), I often get something like the following error messages: ... KLIBCCC usr/klibc/sigsuspend.o KLIBCCC usr/klibc/sigprocmask.o KLIBCCC usr/klibc/pselect.o KLIBCCC usr/klibc/ppoll.o /git/KLIBC/usr/klibc/sigsuspend.c:8:31: fatal

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

It seems that a minor modification to usr/klibc/arch/$(ARCH)/MCONFIG is needed to build klibc successfully against kernel version 3.4.3. At lease the arch "arm" and "x86_64" have this issue. It is because that some include files are under "generated/asm/" in addition to "asm/". --- a/usr/klibc/arch/x86_64/MCONFIG +++ b/usr/klibc/arch/x86_64/MCONFIG @@ -36,4

Commit-ID: d7d16afbdae9bdea83aeb26ac572e6fc4d7d4940 Gitweb: http://git.kernel.org/?p=libs/klibc/klibc.git;a=commit;h=d7d16afbdae9bdea83aeb26ac572e6fc4d7d4940 Author: Steve McIntyre <steve at einval.com> AuthorDate: Fri, 29 Jun 2012 18:13:34 +0100 Committer: maximilian attems <max at stro.at> CommitDate: Sun, 1 Jul 2012 22:51:00 +0200 [klibc] arm/setjmp.S: fix longjmp

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

Steve Capper dixit: >> Do we need the fpregs saved even though klibc doesn't do fp? >For gcc targetting Aarch64, We can only guarantee that d8-d15 are >left alone when -mgeneral-regs-only is supplied for building klibc >and any software linked against klibc. I would much prefer to We can enforce this in klcc, just like -mregparm=3 is used by the i386 target. bye, //mirabilos

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 Sun, 2019-01-20 at 14:18 +0000, Thorsten Glaser wrote: > 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 >

Hi, On Fri, May 23, 2014 at 10:57:31AM -0300, Mauricio Faria de Oliveira wrote: > > The ppc64el port needs klibc's static binaries, like ppc64. This segfaulting is a bug in klibc that needs investigation. > This patch enables the ARCH=ppc64 make env var in debian/rules, in order > for 'debian/patches/ppc64-static.patch' to take effect on ppp64el too. I have no problem

Hey Greg, On 08-09-2020 22:07, Thorsten Glaser wrote: > Greg Thelen dixit: > >> This doesn't work with older versions of make. ?make 4.2.1 seems common >> now and does not support $(shell command). >> >> $ cat Makefile >> $(info take1: $(shell command -v ls)) >> $(info take2: $(shell bash -c 'type -p ls')) >> >> all: >>

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,

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

New clang versions need the '-ffreestanding' flag because new changes convert system calls to their unlocked versions, which don't exist in the kernel library. Signed-off-by: Bill Wendling <morbo at google.com> diff --git a/scripts/Kbuild.klibc b/scripts/Kbuild.klibc index f500d535..9cf4b2d9 100644 --- a/scripts/Kbuild.klibc +++ b/scripts/Kbuild.klibc @@ -67,7 +67,8 @@ include

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. > > bye, > //mirabilos Yes, indeed I found out that instead of doing

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