From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail.cs.ucla.edu (mail.cs.ucla.edu [131.179.128.66]) by sourceware.org (Postfix) with ESMTPS id 0C3BC385E458 for ; Tue, 28 May 2024 14:35:45 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org 0C3BC385E458 Authentication-Results: sourceware.org; dmarc=pass (p=none dis=none) header.from=cs.ucla.edu Authentication-Results: sourceware.org; spf=pass smtp.mailfrom=cs.ucla.edu ARC-Filter: OpenARC Filter v1.0.0 sourceware.org 0C3BC385E458 Authentication-Results: server2.sourceware.org; arc=none smtp.remote-ip=131.179.128.66 ARC-Seal: i=1; a=rsa-sha256; d=sourceware.org; s=key; t=1716906947; cv=none; b=B/NrM4fMoyFznv4p20lePKWO6MCZgC82AXoUumjxIhII0/cjAo4XYeIT3bxCarqf3nPQVL9gkBLYm7MQcb5D9g6gisAa7IOZqF59kN3Qfsc1IexC2z/l9b+Y6dcPf1m3lgbOEHTVxP8Y4mq578S7PBcHaEjY4gHHZRl2VasxcNg= ARC-Message-Signature: i=1; a=rsa-sha256; d=sourceware.org; s=key; t=1716906947; c=relaxed/simple; bh=wKdIm/sdaoLwpp8nhaw2ZfZSi+GC61gOMH0OEzTmf94=; h=DKIM-Signature:Message-ID:Date:MIME-Version:Subject:To:From; b=HKx/LWsYow/DuElstpmVvNGDn6OGmuM2XREK6e+QsSHvods5GP3vx5Z1aNPuthsuHnB/du2kIUObdwDZP52b3eo1uBisj18J8FLKXtAJgLO8kFOcg7h0QdVf2e3aLXWItHCKXDYnf0APf580hTpT8/WWyalvJVKWwpIEPvVqceU= ARC-Authentication-Results: i=1; server2.sourceware.org Received: from localhost (localhost [127.0.0.1]) by mail.cs.ucla.edu (Postfix) with ESMTP id 3409B3C011BDB; Tue, 28 May 2024 07:35:44 -0700 (PDT) Received: from mail.cs.ucla.edu ([127.0.0.1]) by localhost (mail.cs.ucla.edu [127.0.0.1]) (amavis, port 10032) with ESMTP id JFnxFrcbxrsh; Tue, 28 May 2024 07:35:43 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by mail.cs.ucla.edu (Postfix) with ESMTP id B786A3C00E401; Tue, 28 May 2024 07:35:43 -0700 (PDT) DKIM-Filter: OpenDKIM Filter v2.10.3 mail.cs.ucla.edu B786A3C00E401 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cs.ucla.edu; s=9D0B346E-2AEB-11ED-9476-E14B719DCE6C; t=1716906943; bh=MbVWIBSPz80gGd5AirkLJQb5M7HSssZ0JbXYVT8koKc=; h=Message-ID:Date:MIME-Version:To:From; b=emV9BNLVzGu3kORKxJfUza9fxugtNgr+YyoHte9or7qXuXT53xOGNANpK4649lSpi jZds4fRNw0rJkC91pfUy4gyvmkDjcmH8+DRM7Z4I8vJq6eVzyD8qfCZmBWpe5+phcP OYq8a2jziqjSdSYP2oSWS6tKbE3YJHYxE/Xni4t7jfVhzGobU49JZX1O4Qo+uEGwO9 qdqAHRgavamN4yKPV+LAUesDA0bnlDzT4t+IKr29SmhkTDTMemypxCfUL6WOYSr/+e H2BmSJP56tTfzDRGYdJ7iNVO4NlN44Ed4Ubotjy2lv4l/3GLSSCSkOodfh2o3zBV5e b+kObCiZiAejA== X-Virus-Scanned: amavis at mail.cs.ucla.edu Received: from mail.cs.ucla.edu ([127.0.0.1]) by localhost (mail.cs.ucla.edu [127.0.0.1]) (amavis, port 10026) with ESMTP id 5n1rvYYBBoNo; Tue, 28 May 2024 07:35:43 -0700 (PDT) Received: from [192.168.254.12] (unknown [47.154.17.165]) by mail.cs.ucla.edu (Postfix) with ESMTPSA id 8D8DF3C011BDB; Tue, 28 May 2024 07:35:43 -0700 (PDT) Message-ID: Date: Tue, 28 May 2024 07:35:43 -0700 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: configure adds -std=gnu++11 to CXX variable To: Jonathan Wakely Cc: Jakub Jelinek , Florian Weimer , Peter Johansson , Zack Weinberg , Autoconf , "gcc@gcc.gnu.org" References: <00dc6e30-2e12-4b29-951b-d600097b38d0@gmail.com> <80bf1a5a-63a3-4da4-8721-88c760243add@cs.ucla.edu> <878qzv1r13.fsf@oldenburg.str.redhat.com> <3e852f76-9508-4c2e-bef3-7af8a10b626e@cs.ucla.edu> <25aee7da-bdd5-4a2a-b6ac-fa1a4aa11cc7@cs.ucla.edu> Content-Language: en-US From: Paul Eggert Organization: UCLA Computer Science Department In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-3.5 required=5.0 tests=BAYES_00,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,SPF_HELO_NONE,SPF_PASS,TXREP,T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on server2.sourceware.org List-Id: On 2024-05-28 01:20, Jonathan Wakely wrote: > I am not aware of any distro ever changing the default -std setting for g++ > or clang++. Are you attempting to solve a non-problem, but introducing new > ones? If it's a non-problem for C++, why does Autoconf upgrade to C++11 when the default is C++98? Autoconf has done so since Autoconf 2.70 (2020), with nobody complaining as far as I know. Was the Autoconf 2.70 change done so late that it had no practical effect, because no distro was defaulting to C++98 any more? If so, it sounds like Autoconf should go back to its 2.69 behavior and not mess with the C++ version as that's more likely to hurt than help. For background on that Autoconf 2.70 change, see this 2013 thread: https://lists.gnu.org/r/autoconf/2013-01/msg00016.html