similar to: howto to use klcc from a kernel tree?

> You could also try adding "-x usb_set_altinterface" to the command line > (or adding it to ups.conf). The lsusb output implies that the only valid > setting is 0 (bAlternateSetting), but it might need to be set explicitly. I checked with -x usb_set_altinterface and it says nut_usb_set_altinterface: usb_set_altinterface() should not be necessary - please email the

Hi again, > On Sep 8, 2016, at 10:05 AM, Vassilis Virvilis <vasvir at iit.demokritos.gr> > wrote: >> Now that's a problem. I am not sure that I can find >> >> 1) the original software >> 2) a (physical) windows machine in the vicinity of the UPS >> Ha! I jumped several hooks but I think I got it. 01. I contacted the store that sold us the UPS and

Halo, I don't know if this is already done but the following two patches (one for klibc) and a big one (several smaller incorporated to one) to modules-init-tools enables running modprobe and friends in early user space. There are some issues so I post here for discussion The porting strategy was copied from the udev package. I make a file mod_libc_wrapper.{c,h} in order to provide the

Halo, fnmatch() and getopt_long are necessary to compile module-init-tools with klibc out of the box. Would you consider accepting patches to implement those 2 functions? Can we use the bsd libc functions? is the lisence acceptable to you? .bill

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

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 \

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

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

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

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~

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

A little deciphering > Looks like the ups always replies > 22 = 16035500 50005300 20004e00 6f002000 41006300 6b00 That is length = 0x16 = 22 type = 0x3 = string Message = "UPS No Ack" Very fun... Regards Vassilis Virvilis

[snip hex dump analysis] > > It is possible that the blazer_usb driver initialization has put the UPS > into a bad state. If you can schedule some downtime, you might want to try > usbhid-ups again after powering the UPS down completely and unplugging it > for a little while. (Often, a few seconds after the output is off and the > AC has been removed, you will hear relays

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

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

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

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

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

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

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