2018-01-16 13:09 GMT-03:00 Charlie Brady:
>
> 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 =
2018-01-17 12:25 GMT-03:00 Charlie Brady:
>
> bash-4.2$ sed -n 843p /usr/include/curses.h
> extern NCURSES_EXPORT(char *) tigetstr (NCURSES_CONST char *); /*
> implemented */
> bash-4.2$ rpm -qf /usr/include/curses.h
> ncurses-devel-5.9-14.20130511.el7_4.x86_64
And
$ grep 'define NCURSES
On Tue, 16 Jan 2018, Jonathan de Boyne Pollard wrote:
> 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
Guillermo:
Jonathan de Boyne Pollard:
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?
Dickey n
2018-01-16 17:51 GMT-03:00 Jonathan de Boyne Pollard:
>
> 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]
>>
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 O
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 = tigets
On Mon, 15 Jan 2018, Charlie Brady wrote:
> > 1) package/compile: you'll need "redo" to build
>
> Sorry, doesn't work for me:
>
> bash-4.2$ package/compile
> redo: ERROR: all: Cannot find .do file to use.
> bash-4.2$ sh -ex package/compile
> + '[' '!' -d package ']'
> + '[' '!' -d source ']'
>
