similar to: [PATCH] klcc --version is -V because -v is --verbose already (unbreak -v)

Here's a patch to klcc.in from klibc-0.202. The context: I have an application, managed with GNU automake/autoconf. Packagers should be able to build the application with klibc if available, with plain gcc otherwise, as follows: $ cd ~/klibc-0.202 $ ... make linux symlink $ make bindir=$HOME/local/bin \ mandir=$HOME/local/man \ INSTALLDIR=$HOME/local \ SHLIBDIR=$HOME/local/shlib \

This patch adds support to klcc for the --param parameter. Signed off by: Mike Pagano <mpagano at gentoo.org> --- klcc.in | 3 +++ 1 file changed, 3 insertions(+) --- klcc/klcc.in.orig 2011-03-21 08:35:02.130497501 -0400 +++ klcc/klcc.in 2011-03-21 08:47:21.025476293 -0400 @@ -159,6 +159,9 @@ while ( defined($a = shift(@ARGV)) ) { # gcc options, that force preprocessing mode

Later versions of gcc include an option in the form of --param=name=value. This patch adds support for this and continues to support the --param name=value option. Signed-off-by: Mike Pagano <mpagano at gentoo.org> --- klcc/klcc.in | 15 +++++++++++---- 1 files changed, 11 insertions(+), 4 deletions(-) diff --git a/klcc/klcc.in b/klcc/klcc.in index 711a832..5d00bfd 100644 ---

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

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, Apr 13, 2016 at 7:24 PM, Thorsten Glaser <tg at mirbsd.de> wrote: > Denis Bychkov dixit: > >>This is a klibc port to x32 architecture. I tried to reuse as many >>existing files as possible, hence, a >>script making symlinks to x86-64 files. I was running this on Debian >>for about six months and hopefully, >>found any close to surface bugs. Of

Currently, in the entire klibc bash is only used to identify the path of the perl binary. It is doing so using the bash built-in 'type' function, which is POSIX compliant according to [0], but the option -c is not. By using `command -v` instead, we achieve the same result, in a POSIX compliant manor [1], potentially removing the unneeded bash dependency. 0

Ben Hutchings <ben at decadent.org.uk> wrote: > On Sat, 2020-07-25 at 10:59 +0200, Olliver Schinagl wrote: >> Currently, in the entire klibc bash is only used to identify the path of >> the perl binary. It is doing so using the bash built-in 'type' function, >> which is POSIX compliant according to [0], but the option -c is not. >> >> By using

There's a problem in klibc 1.0.12: klcc -c t.c && klcc t.o && ./a.out works, but klcc t.c && ./a.out fails because open3() wants to close its input, and you can do that only once to STDIN. Attached patch makes "klcc t.c" work again. This might break the klcc from stdin option, but I can't tell because I've got no idea how it's supposed to

Stop makeklcc.pl from hardcoding paths of cc, ld and strip in the klcc script it generates. Using hardcoded paths is generally a bad idea. First, the whole idea of $PATH is that you don't need to hardcode paths. Second, klcc is a Perl script but my hardcoding the paths you make it less portable. Signed-off-by: Martin Michlmayr <tbm@cyrius.com> --- klibc-1.1.16/klcc/makeklcc.pl~

Halo, I was wondering to no avail how to to use the klcc wrapper in order to build udev and module-init-tools. Does klibc has an install target when is embedded in the kernel tree? Is klcc available? .bill

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

Package: klibc Version: 1.5.20-1 Severity: normal Tags: patch User: ubuntu-devel at lists.ubuntu.com Usertags: origin-ubuntu natty ubuntu-patch Hi maks, Since the Ubuntu linux-libc-dev is now installing its asm headers to the multiarch /usr/include/<triplet>/ directory to allow co-installability, I've pushed the attached patch to Ubuntu so klcc knows to include this path when searching

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.

Commit-ID: 62d84fb8793fdf21c5267688de231cc1a111e070 Gitweb: http://git.kernel.org/?p=libs/klibc/klibc.git;a=commit;h=62d84fb8793fdf21c5267688de231cc1a111e070 Author: Thorsten Glaser <tg at mirbsd.org> AuthorDate: Sat, 29 Sep 2012 20:18:48 +0000 Committer: maximilian attems <max at stro.at> CommitDate: Mon, 1 Oct 2012 14:55:24 +0200 [klibc] arm: unbreak armhf shared binaries

Hi, after changing mksh to no longer use mkstemp, I decided to try and build mksh-static with klcc on most platforms, in Debian. Here are the results by Debian architecture: alpha (4) fails amd64 works armel works armhf (3) fails i386 works ia64 works m68k (1) workaround mips works mipsel works powerpc (2) fails ppc64 works (!) s390 works s390x works sparc works Architectures not listed either

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

Hi, we?re currently seeing trouble with klibc on several architectures, cf. http://www.zytor.com/pipermail/klibc/2012-May/003277.html and armhf is being one of them, when using klibc to compile mksh-static with it. I can look into it (asked zumbi for build-deps in a sid chroot on harris already), but not 100% sure I?ll find it, so more eyes on klibc would not be unwelcome ;-) maks, does klibc

On Debian/m68k, with latest klibc, I get this warning? /usr/bin/m68k-linux-gnu-ld: warning: /usr/lib/klibc/lib/crt0.o: requires executable stack (because the .note.GNU-stack section is executable) ? trying to link an executable with klcc. bye, //mirabilos -- Gestern Nacht ist mein IRC-Netzwerk explodiert. Ich hatte nicht damit gerechnet, darum bin ich blutverschmiert? wer konnte ahnen, da? SIE

SIGSUSPEND(2) Linux Programmer's Manual SIGSUSPEND(2) NAME sigsuspend - wait for a signal SYNOPSIS #include <signal.h> int sigsuspend(const sigset_t *mask); ? and ? SIGSUSPEND(2) BSD Programmer's Manual SIGSUSPEND(2) NAME sigsuspend - atomically release blocked signals and wait for interrupt SYNOPSIS