Alexis Hildebrandt

Thanks for raising this, @cho-m. Would be it be possible to include the header only if a boost version compile flag indicates that boost >= 1.85.0 is being used?

Ledger already defines `BOOST_FILESYSTEM_NO_DEPRECATED` ([`CMakeLists.txt:23`](https://github.com/ledger/ledger/blob/master/CMakeLists.txt#L23))when compiling, so I'm a bit surprised this wasn't noticed earlier. Thanks for digging deeper into the headers, very helpful. I think understanding what is necessary...

ℹ️ `boost/system/error_code.hpp` is also included by `boost/filesystem/operations.hpp`, which is directly inluded by `system.hh.in`, so that only leaves to check if `boost/config.hpp` is somehow indirectly being included by any of the...

@leedm777 I'm quite clueless at the moment. I've updated to the latest version of the formula from you tap and as requested I've gathered all relevant files in the following...

@leedm777 Compiling gcc takes a while… :hourglass_flowing_sand: I'll post updates as soon as it's done

@leedm777 I can confirm that compiling asterisk without the ~~`--with-clang`~~ option using GCC asterisk is then correctly linked to the homebrewed OpenSSL and the segfaults do **not** occur. :smile: Unfortunately...

Now that version [`v1.0.0`](https://github.com/katzer/cordova-plugin-local-notifications/releases/tag/v1.0.0) was released August 18th 2024 when will the version published on [npmjs.org](https://www.npmjs.com/package/cordova-plugin-local-notification) follow suit? 🙂

Thanks for the info @GitToTheHub. What's the recommended solution for the time being—apart from installing from a local clone—in order to use version 1.0.0? Unfortunately using older versions breaks the...

Excellent, thank you @GitToTheHub 💯

Auxiliary / effective dates can also be specified in a posting's metadata, e.g. `; [=2009/03/01]` (see [section on _Effective Dates_ in the Ledger manual](https://www.ledger-cli.org/3.0/doc/ledger3.html#Effective-Dates)): ``` 2008/10/16 * (2090) Bountiful Blessings...