Displaying 5 results from an estimated 5 matches for "lksh".
Did you mean:
ksh
2019 Jan 20
0
testing by building mksh (was Re: RFT: klibc 2.0.5)
...easiest way is to just package klibc, throw that into an sbuild
or cowbuilder/pbuilder chroot and try to rebuild mksh with it, then
look at the build log (look for ?Build information for static-klibc
mksh? and some lines blow ?Result: regressed? and ?| Total failed: 0?
are the important knobs, but lksh is also currently built with klibc
if it failed, so a few lines below, under ?Build information for
legacy mksh? the same should be, plus ?| CC='klcc'? under ?Variables
used?.
This does not test shared klibc, but should give you an idea what
flags to use. To build manually, get the source...
2019 Jan 20
3
RFT: klibc 2.0.5
On Sun, 2019-01-20 at 04:37 +0000, Ben Hutchings wrote:
[...]
> ppc/powerpc-linux-gnu: pass fail: malloctest2*,
> setjmptest*, sigint*
[...]
> s390x/s390x-linux-gnu: fail: fcntl fail: malloctest2*, setjmptest* setjmptest*,
>
2014 Oct 03
0
Fwd: mksh-static segfaults on continued jobs
...com>
Message-ID: <20141003053550.GA8510 at gmail.com>
Date: Fri, 3 Oct 2014 07:35:50 +0200
Subject: Bug#763842: mksh-static segfaults on continued jobs
Package: mksh
Version: 50b-1
Severity: normal
Dear Maintainer,
When a job is continued after being stopped in interactive mksh-static
or lksh, they crash with segmentation fault.
The simplest way to reproduce is to call "fg" for any stopped job in
interactive mksh-static or lksh (full mksh is not affected); it results
in job being continued but shell crashing immediately after that.
The crash happens in j_print() at jobs.c:15...
2019 Jan 21
1
testing by building mksh (was Re: RFT: klibc 2.0.5)
...ust package klibc, throw that into an sbuild
> or cowbuilder/pbuilder chroot and try to rebuild mksh with it, then
> look at the build log (look for ?Build information for static-klibc
> mksh? and some lines blow ?Result: regressed? and ?| Total failed: 0?
> are the important knobs, but lksh is also currently built with klibc
> if it failed, so a few lines below, under ?Build information for
> legacy mksh? the same should be, plus ?| CC='klcc'? under ?Variables
> used?.
[...]
I've pushed my current test script out to:
https://git.kernel.org/pub/scm/linux/kernel/gi...
2020 Mar 27
2
[PATCH v2 5/5] Clean up clang warnings
- Convert the "old style" GNU field designator extension to the new
style.
- Use proper indexing into a string literal.
- Use "%s" for the format string in "fmtstr".
- Add or remove casts of the "void *" argument of ioctl.
- Convert "if (!exitstatus == isor)" to "if ((!exitstatus) == isor)"
which retains the current semantics, but may