From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 89110 invoked by alias); 13 Oct 2016 13:59:29 -0000 Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org Received: (qmail 89096 invoked by uid 89); 13 Oct 2016 13:59:28 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-2.3 required=5.0 tests=AWL,BAYES_00,RP_MATCHES_RCVD,SPF_PASS autolearn=ham version=3.3.2 spammy=hackers, uninstall, Hx-languages-length:1815, organizations X-HELO: eggs.gnu.org Received: from eggs.gnu.org (HELO eggs.gnu.org) (208.118.235.92) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Thu, 13 Oct 2016 13:59:18 +0000 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1bugXS-0006Ru-9N for gdb-patches@sourceware.org; Thu, 13 Oct 2016 09:59:17 -0400 Received: from fencepost.gnu.org ([2001:4830:134:3::e]:49100) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bugXS-0006RB-63; Thu, 13 Oct 2016 09:59:14 -0400 Received: from 84.94.185.246.cable.012.net.il ([84.94.185.246]:4448 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_128_CBC_SHA1:128) (Exim 4.82) (envelope-from ) id 1bugXQ-0001SC-5H; Thu, 13 Oct 2016 09:59:12 -0400 Date: Thu, 13 Oct 2016 13:59:00 -0000 Message-Id: <83pon48i54.fsf@gnu.org> From: Eli Zaretskii To: Pedro Alves CC: jan.kratochvil@redhat.com, brobecker@adacore.com, markus.t.metzger@intel.com, gdb-patches@sourceware.org In-reply-to: <640356ae-74e2-bcba-6c89-26bfbcd4fe36@redhat.com> (message from Pedro Alves on Thu, 13 Oct 2016 14:35:58 +0100) Subject: Re: [PATCH 1/3] Introduce gdb::unique_ptr Reply-to: Eli Zaretskii References: <4d49eb8f-5a0c-1e7e-d082-1a224179184f@redhat.com> <831szmd977.fsf@gnu.org> <83vawybol4.fsf@gnu.org> <6ba388f7-1696-42db-ae92-23df79e3ba11@redhat.com> <83oa2qaxe7.fsf@gnu.org> <83fuo1c02j.fsf@gnu.org> <20161012114515.GA26977@host1.jankratochvil.net> <831szlbwqt.fsf@gnu.org> <20161013090647.GA32613@host1.jankratochvil.net> <83y41s8swm.fsf@gnu.org> <53d106ee-26d3-b6dc-1810-0c7dcaef2f84@redhat.com> <83twcg8juq.fsf@gnu.org> <640356ae-74e2-bcba-6c89-26bfbcd4fe36@redhat.com> X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 2001:4830:134:3::e X-IsSubscribed: yes X-SW-Source: 2016-10/txt/msg00362.txt.bz2 > Cc: jan.kratochvil@redhat.com, brobecker@adacore.com, > markus.t.metzger@intel.com, gdb-patches@sourceware.org > From: Pedro Alves > Date: Thu, 13 Oct 2016 14:35:58 +0100 > > >> The newer compilers available as packages on these old distros > >> (e.g., DTS on RHEL) do _not_ replace the system compiler. They're > >> installed in parallel, in separate directories. You willfully add them > >> to the PATH or pass an overridden CXX to configure/make if you want to > >> use them. > > > > I don't see the difference, except for the worse: instead of one > > compiler you now have two, so one could easily select the wrong one > > when compiling some package. > > You said: > > "upgrading the system compiler is a serious decision. Installing a > newer compiler could easily break the build of several important > packages (...)" > > And I'm telling you that the packages in question don't upgrade > the system compiler at all. Of course, they do: you have a newer compiler on your system, which is about to be used for building some packages. > There's no risk of "easily break" things. Of course, there is: the new compiler will do that. That one can go back to the old one doesn't help at all, because that was also possible without a parallel installation: just uninstall the new one and install back the old one. Organizations rarely do this stuff. You want to install a compiler and let users use it without complications. Most of your users aren't hackers, they have no idea how to debug a package build problem. They will come back to you expecting that you fix the problem for them. > There's nothing complicated here. I respectfully disagree. We most probably have very different experience here, and very different users to deal with.