On 04/24/19 13:39, William A Rowe Jr wrote:
> Hi Barry,
>
> you are looking at the latest consensus code spanning BSD and OS/X in
> two variants.
>
> It would help us if you would share your config.log and entire output of
> ./configure along with cc -version type data for the applicable
On Wed, Apr 24, 2019, 14:31 William A Rowe Jr wrote:
>...
>
>
> [X] Please drop 8-bit and focus only on utf-8 resource names on Win32.
>
It is a very good breaking change for 2.0. Leave that stuff behind. Devs
who need it can stick to 1.x or choose another solution.
Cheers,
-g
Some 17 years later we are at a crossroads, because the win32 code
is somewhat illegible and harder to maintain due to the ANSI-vs-UTF8,
Win9x-vs-NT code paths.
NT won. The only remaining question is how many apr consumers are
leveraging ANSI-specific builds for local code page semantics, vs how
Hi Barry,
you are looking at the latest consensus code spanning BSD and OS/X in two
variants.
It would help us if you would share your config.log and entire output of
./configure along with cc -version type data for the applicable compiler.
On Wed, Apr 24, 2019 at 1:04 PM Barry Scott wrote:
I use ./configure --prefix=/usr/local/svn and see the error:
...
checking whether int64_t and long long use fmt %lld... no
configure: error: could not determine the string function for int64_t
Looking in config.log I see this:
configure:24313:
