similar to: Bug#622814: klibc: patch to make klcc play nice with multiarch linux-libc-dev

headers_install needs KLIBCKERNELOBJ instead of KLIBCKERNELSRC Signed-off-by: Karl Beldan <karl.beldan at gmail.com> --- scripts/Kbuild.install | 2 +- 1 files changed, 1 insertions(+), 1 deletions(-) diff --git a/scripts/Kbuild.install b/scripts/Kbuild.install index 370b54e..fd4a2ed 100644 --- a/scripts/Kbuild.install +++ b/scripts/Kbuild.install @@ -95,7 +95,7 @@ header: $(Q)mkdir

Version: 2.0.4 and git Kernel tested: 3.10.70 Description: make install fails with: No rule to make target `headers_install'. File impacted: scripts/Kbuild.install Error Received: make[2]: *** No rule to make target `headers_install'. Stop. make[1]: *** [header] Error 2 make: *** [install] Error 2 Issue: KLIBCKERNELSRC=`pwd`/linux/usr points to Makefile without headers_install rule.

klibc currently builds and installs differently depending on the locale and umask at build time. This series fixes that. Ben. Ben Hutchings (2): Install headers with consistent mode dash: mkbuiltins: Fix sort order harder scripts/Kbuild.install | 2 +- usr/dash/mkbuiltins | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) -------------- next part -------------- A non-text

We currently use KLIBCKERNELSRC and KLIBCKERNELOBJ variables which used to be required to point to a kernel source and object directories. However the kernel headers were reorganised starting in Linux 3.7 such that that doesn't work properly. This series removes KLIBCKERNELOBJ and changes the use and documentation of KLIBCKERNELSRC to be consistent. Ben. Ben Hutchings (4): [klibc]

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

Some packages want to pass input to gcc via STDIN (iptables for example) This patch lets klcc accept '-' as a valid input filename, prevents it from setting -x in that case and changes the invocation of gcc from system() to open3() so that gcc's STDIN can be connected to klcc's STDIN. Daniel Thaler -------------- next part -------------- --- klibc-1.0.8/klcc.in.old 2005-05-20

Hopefully I should be up to date with all patches; haven't integrated the module-init-tools, and some of Erik's patches didn't make it for different reasons, which hopefully can be resolved soon. If you have sent another patch which I haven't applied, please do let me know. -hpa

Signed-off-by: Thorsten Glaser <tg at mirbsd.org> --- klcc/klcc.in | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/klcc/klcc.in b/klcc/klcc.in index 43d0984..e03bf3c 100644 --- a/klcc/klcc.in +++ b/klcc/klcc.in @@ -136,7 +136,7 @@ while ( defined($a = shift(@ARGV)) ) { } else { die "$0: unknown option: $a\n"; } - } elsif ( $a =~

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

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 \

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

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

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

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

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~

Hi, Why isn't 'R CMD check --force-multiarch' installing the package for all the architectures that are going to be checked? For some packages, it only installs for the default arch ('i386'). Then testing the package for 'x64' fails. For example, Output of R CMD check --force-multiarch fabia_1.5.0.tar.gz: ----------------------------------------------------------- *

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.

Hello, I'm unable to update my Samba from 4.1.17 to 4.4.2. I'm looking to build from tar instead. From what I gather the following should be the steps taken. ./configure --without-ad-dc -- sbindir= /usr/sbin --sysconfdir=/etc/samba/ --/usr/share/man/ make make install Am I missing something else? Thanks. -- -James

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