similar to: [PATCH] klcc on multiple files

Displaying 20 results from an estimated 1000 matches similar to: "[PATCH] klcc on multiple files"

2005 May 20
0
[PATCH] let klcc pass input from STDIN to gcc
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
2005 Mar 02
2
[PATCH] klcc compatibility with gcc
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 \
2020 Aug 20
0
[klibc:master] klcc: Treat CC, LD, STRIP as multiple words
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
2005 May 24
2
klibc-1.0.12 released
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
2020 Aug 29
0
[klibc:riscv64-enable-relax] Kbuild, klcc: Support multiple objects in KLIBCCRTSHARED
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
2012 Jun 07
1
[PATCH] klcc --version is -V because -v is --verbose already (unbreak -v)
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 =~
2020 Jul 25
2
[PATCH] klcc: Remove the need for bash
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
2011 Mar 21
1
[PATCH] support the gcc parameter --param in klcc
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
2005 May 22
1
[patch 05/12] make __constant_htons visible
The __constant_htons and similar are defined in klibc version of netinet/in.h, but not in glibc counterpart. Include the same thing from <asm/byteorder.h>, which is available in both glibc and klibc. Perhaps __constant_htons should be dropped from the klibc version of netinet/in.h: it provides nothing that you cannot get via asm/byteorder, and gets in the way of porting between glibc and
2006 Jan 25
1
Don't hardcode paths in klcc
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~
2006 May 15
1
howto to use klcc from a kernel tree?
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
2005 May 22
1
[patch 11/12] Unpleasantness in linux/nfs_mount.h
There is a conflict in glibc between <linux/in.h> and <netinet/in.h>: one defines protocols with an enum, the other does the same, but adds a self-define for every enumerated value. #define IPPROTO_IP IPPROTO_IP This means the two cannot be mixed, and since loads of include files refer to <netinet/in.h>, effectively <linux/in.h> cannot be used with glibc. Since
2011 Apr 14
1
Bug#622814: klibc: patch to make klcc play nice with multiarch linux-libc-dev
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
2012 Feb 23
0
Bug#653790: klibc/s390x: searches for include in the wrong path
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,
2020 Jul 25
0
[klibc:master] klcc: Remove the need for bash
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
2011 Jul 20
2
[PATCH 1/1] Modify --param support to include additional option
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 ---
2020 Jul 25
0
[PATCH] klcc: Remove the need for bash
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 `command -v` instead, we achieve the same result, in a POSIX > compliant manor
2019 Feb 19
0
[klibc:master] klcc: Enable stripping even if CONFIG_DEBUG_INFO is enabled
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
2020 Sep 08
3
[PATCH] klcc: Remove the need for bash
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
2006 Jul 03
0
[PATCH]: klcc typo recognizing .S files
Trying to use klcc to compile an application I was getting gcc: no input files. Tracked it down to filename2lang having and extra space, causing .S files to be labeled "obj". Signed-off-by: Milton Miller <miltonm at bga.com> --- There is probably another bug that we called gcc without any files when we were called with what we parsed as an obj file. ---