> Does the compiler complain that the "mbtowc_with_lock" function has an
> unresolved symbol relating to 'pthreads' ?
I believe it was a link error.
It's been a few weeks. :)
I can go and look, but also passing -pthread or -pthreads is fairly common "in
the ecosystem" (across
the random set of
Hi,
Claws Mail uses the Enchant spell checking library, which we build with
relocatable support for Windows.
Running with app verifier enabled caught a memory leak in
lib/relocatable.c. The memory allocated in DllMain() by:
shared_library_fullname = strdup (location);
is never freed. _DLL_Ini
On 8/4/21 2:29 PM, Assaf Gordon wrote:
(But as you're aware, there's a limited amount of support for older
systems...)
Yes, HP dropped support for Tru64 in 2012, and a good rule of thumb for
GNU code is to not worry about an OS if it's so old that even its own
maintainer doesn't worry about i
(adding gnulib@)
Hello,
On 2021-07-01 12:35 a.m., Jay K wrote:
Hi. I built GNU sed for Tru64.
With native cc, not gcc. I realize it is an old system.
$ uname -srm
OSF1 V5.1 alpha
$ which cc
/usr/bin/cc
$ cc -V
Compaq C V6.5-303 (dtk) on HP Tru64 UNIX V5.1B (Rev. 2650)
Compiler Driver V6.5-30
tis 2021-08-03 klockan 16:51 -0700 skrev Jim Meyering:
> On Tue, Aug 3, 2021 at 12:25 PM Paul Eggert
> wrote:
> > On 8/3/21 12:20 PM, Simon Josefsson via Gnulib discussion list
> > wrote:
> > > + print "\nThe SHA256 checksum is base64 encoded and not
> > > hexadecimal,\n";
> > > + print "which i