Hello,
I added this option inside my config.linux file, at the end of the first
line (COMPILE_OPTS).
Then I ran `make distclean`, regenerated the makefiles (`./genMakefiles
linux`). Then, `make` worked, building with the option.
Best regards,
Flavio
On Wed, 29 Nov 2023 at 15:25, Ross Finlayson
> On Nov 30, 2023, at 6:50 AM, Dmitry Bely wrote:
>
> BTW I'm curious what the purpose of std::atomic_flag? What was wrong with
> good old "volatile bool"?
FYI, that’s what you get if you compile with -DNO_STD_LIB
Ross Finlayson
Live Networks, Inc.
http://www.live555.com/
On Wed, Nov 29, 2023 at 4:09 PM Ross Finlayson
wrote:
>
> > On Nov 30, 2023, at 4:14 AM, Dmitry Bely wrote:
> >
> > Hi,
> > Recent versions of live555 use std::atomic_flag array to work with
> > event triggers. Consider the following code fragment:
> >
> > #ifndef NO_STD_LIB
> > if (fTrigger
> On Nov 30, 2023, at 4:14 AM, Dmitry Bely wrote:
>
> Hi,
> Recent versions of live555 use std::atomic_flag array to work with
> event triggers. Consider the following code fragment:
>
> #ifndef NO_STD_LIB
> if (fTriggersAwaitingHandling[i].test()) {
> fTriggersAwaitingHandling[i].c
Hi,
Recent versions of live555 use std::atomic_flag array to work with
event triggers. Consider the following code fragment:
#ifndef NO_STD_LIB
if (fTriggersAwaitingHandling[i].test()) {
fTriggersAwaitingHandling[i].clear();
#else
It is problematic in two ways: 1) it's not atomic:
