bug-coreutils
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

bug#7073: threadlib vs. pthread modules


From: Assaf Gordon
Subject: bug#7073: threadlib vs. pthread modules
Date: Mon, 29 Oct 2018 23:35:29 -0600
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.2.1

(triaging old bugs)

Hello,

This thread ( https://bugs.gnu.org/7073 )
starts with build error on Mac OS X due to pthread related issues.

It then deals with this (already commited) gnulib change:
=====
2010-09-22  Bruno Haible  <address@hidden>
   threadlib: Allow the package to change the default to 'no'.
   * m4/threadlib.m4 (gl_THREADLIB_EARLY_BODY): When
   gl_THREADLIB_DEFAULT_NO is defined, change the default to 'no'.
=====

And finally:

On 2010-09-22 11:48 a.m., Paul Eggert wrote:
On 09/22/10 08:18, Bruno Haible wrote:

Would you (in coreutils, sort) be willing to use such an API that is
slightly different from POSIX, but much closer to POSIX than
'lock', 'tls', 'cond', 'thread', 'yield' are now?

Yes, that sounds like a better option, thanks!  Two further thoughts.


Can this bug be closed?
(at least - I believe newer coreutils builds fine on newer Mac OS X)

thanks!
 - assaf





reply via email to

[Prev in Thread] Current Thread [Next in Thread]