It _probably_ works to just pass free(ptr) another two arguments, but
compilers don't like this kind of sloppiness anymore.
The call site only expects this function to free the first value,
ignoring the other two, so model that in the local wrapper function.
putenv doesn't copy the data, so the stack address used here is plain
wrong. It _probably_ doesn't matter all that much because it's
immediately followed by execv(), but let's keep things clean.
From a diff file provided by Mariusz Zynel:
Every time, every dt program gives that error on its
start. t_optmgmt() is called once in _tt_tli_set_nodelay(), as the
name says, to set TCP_NODELAY option for ToolTalk connections.
The current behavior is not standards conformant, and will cause the
format operation to result in empty text as glibc fails any calls to
getwc against a narrow stream with WEOF. Additionally, narrow write
operations against a wide stream appears to bypass the buffer, causing
incorrect formatting results.
Fix this by changing all write operations against the reformatted output
file stream to be wide operations, and reopening the temporary input
file before performing any wide read operations.
Some mice have more than 3 buttons. Although Xlib.h doesn't provide
definitions for these buttons, button 6 to 9 is reported through the
XButtonEvent struct.
This adds support for mapping actions to mouse button 6 to 9.
The sh_access was defined to two arguments
Made a workaround to not use the sh_access
that was outputting the error.
Not ideal, but it will hopefully compile on Arch Linux
Also added mksh for compatibility
Ksh is unmaintained in the Arch User Repository
Signed-off-by: Nilton Perim Neto <niltonperimneto@gmail.com>
Patch from Cy Schubert:
FreeBSD bb421be6c117 moved ftime(3) from libcompat to libutil. This
results in the following error,
ld: error: undefined symbol: ftime
>>> referenced by getdate.c
>>> libDtCmP_a-getdate.o:(cm_getdate) in archive
../libDtCmP/libDtCmP.a
>>> did you mean: ctime
Signed off by: Cy Schubert <cy@FreeBSD.org>
