On 10/11/2023 7:27 pm, Sebastian Huber wrote:
> On 25.09.23 11:25, Sebastian Huber wrote:
>> On 25.09.23 08:45, Chris Johns wrote:
>>> On 22/9/2023 2:47 pm, Sebastian Huber wrote:
On 22.09.23 04:36, Joel Sherrill wrote:
> Are we doing something that particularly requires C++17? AFAIK we
On 25.09.23 11:25, Sebastian Huber wrote:
On 25.09.23 08:45, Chris Johns wrote:
On 22/9/2023 2:47 pm, Sebastian Huber wrote:
On 22.09.23 04:36, Joel Sherrill wrote:
Are we doing something that particularly requires C++17? AFAIK we
haven't
needed it yet and why wouldn't it also be needed with
On 25.09.23 08:45, Chris Johns wrote:
On 22/9/2023 2:47 pm, Sebastian Huber wrote:
On 22.09.23 04:36, Joel Sherrill wrote:
Are we doing something that particularly requires C++17? AFAIK we haven't
needed it yet and why wouldn't it also be needed with gcc? If the default on
recent gcc versions
On 22/9/2023 2:47 pm, Sebastian Huber wrote:
> On 22.09.23 04:36, Joel Sherrill wrote:
>> Are we doing something that particularly requires C++17? AFAIK we haven't
>> needed it yet and why wouldn't it also be needed with gcc? If the default on
>> recent gcc versions is that, ok but we should be
On 22.09.23 04:36, Joel Sherrill wrote:
Are we doing something that particularly requires C++17? AFAIK we
haven't needed it yet and why wouldn't it also be needed with gcc? If
the default on recent gcc versions is that, ok but we should be precise
in case an older gcc with a different default
Are we doing something that particularly requires C++17? AFAIK we haven't
needed it yet and why wouldn't it also be needed with gcc? If the default
on recent gcc versions is that, ok but we should be precise in case an
older gcc with a different default is used.
This may also eliminate some
---
trace/wscript | 8 +++-
1 file changed, 7 insertions(+), 1 deletion(-)
diff --git a/trace/wscript b/trace/wscript
index a3dd5d5..0ae90f8 100644
--- a/trace/wscript
+++ b/trace/wscript
@@ -33,11 +33,14 @@ def options(opt):
def configure(conf):
conf.load('compiler_c')
