My working copy just refuses to show the changes but the merge info is
there, strange. Taking testencode.c from trunk and it builds great. Test
passes. Thank you.
cheers
On 3/25/2019 4:05 AM, Yann Ylavic wrote:
Hi Gregg,
On Mon, Mar 25, 2019 at 6:17 AM Gregg Smith wrote:
No, r1856096
On Sun, Mar 24, 2019 at 11:14 PM William A Rowe Jr wrote:
>
> AFAICT the very last 'nit' is our bad habit of using the deprecated
> readdir_r()/readdir64_t() functions in modern gcc. Comparing ./configure and
> make reminds me I had a kludge to finish in my working 1.7 tree. See
>
Hi Gregg,
On Mon, Mar 25, 2019 at 6:17 AM Gregg Smith wrote:
>
> No, r1856096 doesn't help, but thanks.
I missed most of the cases actually, better with r1856178?
On 25.03.2019 07:17, Gregg Smith wrote:
> Hi Yann,
>
> No, r1856096 doesn't help, but thanks.
>
> I think VS just doesn't like these arrays of unknown size.
>
> usrc = (unsigned char[]){ };
> utarget = (unsigned char[]){ };
This is not ANSI C. Visual Studio doesn't support C99 and later
Hi Yann,
No, r1856096 doesn't help, but thanks.
I think VS just doesn't like these arrays of unknown size.
usrc = (unsigned char[]){ };
utarget = (unsigned char[]){ };
It's fine with the ones that are initialized with values like
usrc = (unsigned char[]){'f'};
utarget =
