supervision - discussion about system services, daemon supervision, init, runlevel management, and tools such as s6 and runit
 help / color / mirror / Atom feed
From: Charlie Brady <charlieb-supervision@budge.apana.org.au>
To: Jonathan de Boyne Pollard <J.deBoynePollard-newsgroups@NTLWorld.COM>
Cc: Supervision <supervision@list.skarnet.org>
Subject: Re: nosh build problems (Re: Compatibilities between runit and s6 (re: )
Date: Tue, 16 Jan 2018 11:09:58 -0500 (EST)	[thread overview]
Message-ID: <Pine.LNX.4.64.1801161106270.25033@e-smith.charliebrady.org> (raw)
In-Reply-To: <Pine.LNX.4.64.1801151943060.21371@e-smith.charliebrady.org>


OK, with pax installed, but gets a lot further.

Now seeing these many times:

/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);

and this:

service-status.cpp:276:111: warning: enumeral and non-enumeral type in 
conditional expression [enabled by default]
   const char state(b >= ENCORE_STATUS_BLOCK_SIZE ? 
status[ENCORE_STATUS_OFFSET] : p ? encore_status_running : 
encore_status_stopped);

 This is on CentOS7 build platform.



  reply	other threads:[~2018-01-16 16:09 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 [this message]
2018-01-16 20:51                   ` Jonathan de Boyne Pollard
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=Pine.LNX.4.64.1801161106270.25033@e-smith.charliebrady.org \
    --to=charlieb-supervision@budge.apana.org.au \
    --cc=J.deBoynePollard-newsgroups@NTLWorld.COM \
    --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).