From: Jonathan de Boyne Pollard <J.deBoynePollard-newsgroups@NTLWorld.COM>
To: Supervision <supervision@list.skarnet.org>
Cc: Charlie Brady <charlieb-supervision@budge.apana.org.au>
Subject: Re: nosh build problems (Re: Compatibilities between runit and s6 (re: )
Date: Tue, 16 Jan 2018 20:51:13 +0000 [thread overview]
Message-ID: <a605c9d3-3cb7-613f-0ce3-15fcc20c5805@NTLWorld.COM> (raw)
In-Reply-To: <Pine.LNX.4.64.1801161106270.25033@e-smith.charliebrady.org>
[-- Attachment #1: Type: text/plain, Size: 758 bytes --]
Charlie Brady:
> /usr/include/curses.h:843:31: error: initializing argument 1 of 'char*
> tigetstr(char*)' [-fpermissive]
>
> service-status.cpp:148:21: error: invalid conversion from 'const char*' to
> 'char*' [-fpermissive]
> s = tigetstr(setaf);
This is a problem that I thought was confined to OpenBSD, and its
not-|const|-correct ncurses library. Certainly this has never been a
problem on Debian nor on FreeBSD, and M. Caravia did not report any lack
of |const|-correctness on Arch Linux. What does line 843 of your
|/usr/include/curses.h| actually say? Because that's not the location
of that function declaration in that header in either Dickey ncurses or
Acton pdcurses as far as I can see. So what curses are you actually using?
next prev parent reply other threads:[~2018-01-16 20:51 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-10 23:23 Incompatibilities between runit and s6? Avery Payne
2018-01-11 14:14 ` Charlie Brady
2018-01-13 18:03 ` Compatibilities between runit and s6 (re: Incompatibilities between runit and s6?) Charlie Brady
2018-01-13 18:55 ` Laurent Bercot
2018-01-14 11:36 ` Jonathan de Boyne Pollard
2018-01-14 21:08 ` Charlie Brady
2018-01-14 21:54 ` Jonathan de Boyne Pollard
2018-01-15 12:53 ` Thomas Caravia
2018-01-15 13:33 ` Laurent Bercot
2018-01-16 0:33 ` Charlie Brady
2018-01-16 0:44 ` nosh build problems (Re: Compatibilities between runit and s6 (re: ) Charlie Brady
2018-01-16 16:09 ` Charlie Brady
2018-01-16 20:51 ` Jonathan de Boyne Pollard [this message]
2018-01-17 1:26 ` Guillermo
2018-01-17 7:35 ` Jonathan de Boyne Pollard
2018-01-17 15:25 ` Charlie Brady
2018-01-18 11:58 ` Guillermo
2018-01-18 14:25 ` nosh build problems (Re: Compatibilities between runit and s6 Charlie Brady
2018-02-18 21:16 ` nosh build problems (Re: Compatibilities between runit and s6 (re: ) Guillermo
2018-01-16 8:10 ` Compatibilities between runit and s6 (re: Incompatibilities between runit and s6?) Jonathan de Boyne Pollard
2018-01-16 15:59 ` Charlie Brady
2018-01-16 21:51 ` Jonathan de Boyne Pollard
2018-01-16 8:06 ` Jonathan de Boyne Pollard
2018-01-16 14:52 ` multiplexd
[not found] ` <89cffa18-a72a-ed98-031c-c72fc00ad5aa@ntlworld.com>
2018-01-16 15:44 ` Laurent Bercot
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=a605c9d3-3cb7-613f-0ce3-15fcc20c5805@NTLWorld.COM \
--to=j.deboynepollard-newsgroups@ntlworld.com \
--cc=charlieb-supervision@budge.apana.org.au \
--cc=supervision@list.skarnet.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).