On Fri, Sep 01, 2023 at 10:31:45PM -0600, Brook Milligan wrote:
> I'll submit a PR; what category?
Definitively hardware specific, so port-arm.
> - When the kernel boots into multiuser, run cu as
>
> # cu -l /dev/tty01
You mean /dev/dty01 here? Is 01 the correct number (you should check
> On Sep 1, 2023, at 7:05 PM, Brook Milligan wrote:
>
>> On Sep 1, 2023, at 5:33 PM, Brett Lymn wrote:
>>
>> On Thu, Aug 31, 2023 at 09:02:53PM -0600, Brook Milligan wrote:
>>>
>>> However, a write fails and hangs the board hard: no keyboard response, no
>>> response to pings. I have attach
> On Sep 1, 2023, at 5:33 PM, Brett Lymn wrote:
>
> On Thu, Aug 31, 2023 at 09:02:53PM -0600, Brook Milligan wrote:
>>
>> However, a write fails and hangs the board hard: no keyboard response, no
>> response to pings. I have attached the test program below, and would
>> appreciate more eyes
On Thu, Aug 31, 2023 at 09:02:53PM -0600, Brook Milligan wrote:
>
> However, a write fails and hangs the board hard: no keyboard response, no
> response to pings. I have attached the test program below, and would
> appreciate more eyes on it from (the many) people who obviously know serial
> l
On Fri, Sep 01, 2023 at 11:29:45PM +, RVP wrote:
>
> This is more a pkgsrc issue than a curses issue; and a PR was indeed filed...
>
Only sort of. It is a bug with our curses if an application does not work
properly.
I do understand that the issue with pkgsrc needs a fix but the deeper iss
On Sat, 2 Sep 2023, Brett Lymn wrote:
It could be avoided altogether if there were PRs logged against the builtin
curses. I do
perform sweeps of the PR database for curses related problems every now and
then. There was
a major update to the refresh code between 9 and 10 driven by problems ra
On Fri, 1 Sep 2023, Rhialto wrote:
I did an experiment with a Makefile.test which just contains
PREFER.curses= pkgsrc
.include "../../mk/curses.buildlink3.mk"
.include "../../mk/termcap.buildlink3.mk"
.include "../../mk/bsd.pkg.mk"
[...]
Then I noticed the symlink: /usr/lib/libtermcap.
On Fri, Sep 01, 2023 at 08:36:08AM +, RVP wrote:
>
> https://mail-index.NetBSD.org/current-users/2023/04/16/msg043785.html
>
> This _really_ ought to be fixed once and for all.
>
It could be avoided altogether if there were PRs logged against the builtin
curses. I do
perform sweeps of the
On Fri 01 Sep 2023 at 08:36:08 +, RVP wrote:
> This _really_ ought to be fixed once and for all.
I did an experiment with a Makefile.test which just contains
PREFER.curses= pkgsrc
.include "../../mk/curses.buildlink3.mk"
.include "../../mk/termcap.buildlink3.mk"
.include "../../mk/bs
On Fri, 1 Sep 2023, Rhialto wrote:
I guess I found a corner case in pkgsrc if you do
PREFER.curses= pkgsrc
.include "../../mk/curses.buildlink3.mk"
.include "../../mk/termcap.buildlink3.mk"
Other people have been bitten by this ;). See PR pkg/57365 (prompted by this
thread):
https:
On Thu 31 Aug 2023 at 21:45:32 +, RVP wrote:
> On Thu, 31 Aug 2023, Rhialto wrote:
>
> > So I'm trying ncurses.
> >
> > However at startup it crashes in NetBSD's libterminfo.
> >
>
> If you use ncurses, then you _shouldn't_ be linking in the system libterminfo
> as well. Ncurses, as it's us
11 matches
Mail list logo
