That should do it. I changed my user-config.jam as described, changed to the test directory in libs/beast and ran b2 -a Dave On 3/23/20 12:57 PM, Richard Hodges wrote:

On Mon, 23 Mar 2020 at 17:09, David P. Riedel via Boost-users mailto:boost-users@lists.boost.org> wrote:

Hi  ...

Are beast and asio not concepts ready? Or am I missing something?  Is there some flag I need to set?

My set up:

boost: 1.72 gcc: 9.3

I added -std=c++2a -fconcepts  to compile flags in my user-config.jam file to enable compiler concepts support.

Are these the only criteria to reproduce the problem, or is there something else I should know about the setup prior to investigating?

I have no problems using these compiler flags with other non-boost code.

Thanks

_______________________________________________ Boost-users mailing list Boost-users@lists.boost.org mailto:Boost-users@lists.boost.org https://lists.boost.org/mailman/listinfo.cgi/boost-users

-- Richard Hodges hodges.r@gmail.com mailto:hodges.r@gmail.com office: +442032898513 home: +376841522 mobile: +376380212

On 3/23/20 1:24 PM, Vinnie Falco via Boost-users wrote:

On Mon, Mar 23, 2020 at 9:10 AM David P. Riedel via Boost-users wrote:

...

My set up:

Perhaps you might provide a self-contained example program which exhibits the problem here:

https://godbolt.org/z/uPrSGo

Thanks

I'm just building the tests from the boost distribution. No code of mine involved. libs/beast/tests

Thanks ! On 3/23/20 2:25 PM, Mathias Gaunard wrote:

...

On Mon, Mar 23, 2020 at 9:10 AM David P. Riedel via Boost-users wrote:

...

My set up: Perhaps you might provide a self-contained example program which exhibits the problem here:

https://godbolt.org/z/uPrSGo This empty main with a recent gcc and -fconcepts is enough to trigger

On Mon, 23 Mar 2020 at 17:24, Vinnie Falco via Boost-users wrote: plenty of errors.