From owner-freebsd-toolchain@freebsd.org Sun Jul 2 01:53:42 2017 Return-Path: Delivered-To: freebsd-toolchain@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 2BC28D981F7 for ; Sun, 2 Jul 2017 01:53:42 +0000 (UTC) (envelope-from sid@bsdmail.com) Received: from mout.gmx.com (mout.gmx.com [74.208.4.200]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "mail.gmx.com", Issuer "thawte SSL CA - G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id DB54D7A0F5 for ; Sun, 2 Jul 2017 01:53:41 +0000 (UTC) (envelope-from sid@bsdmail.com) Received: from [108.70.50.7] by 3capp-mailcom-lxa04.server.lan (via HTTP); Sun, 2 Jul 2017 03:53:34 +0200 MIME-Version: 1.0 Message-ID: From: Sid To: freebsd-toolchain@freebsd.org Subject: Re: suggestion for toolchain to have its own directories Content-Type: text/plain; charset=UTF-8 Date: Sun, 2 Jul 2017 03:53:34 +0200 Importance: normal Sensitivity: Normal Content-Transfer-Encoding: quoted-printable X-Priority: 3 X-Provags-ID: V03:K1:cbC3V3T9F7ePnF2cYmxj9d82YNdh4i6yJVzOmvDSDKl whtuPSgGGcLK94v0KI24DwKlybJzQFvhR85+hbHcJGhA4c7u2A wo2J02SPahweKZMkvZX5uEEU5ydDyUVXGFlvb6axeaxhZ+lh2r o63PZApz/1GV9T2o56t67XoARu4OHAkr/nbu7Lk0ibQT684cVZ y+QnVEId+i5K3ujQ+7zOEVTlCKPZNPnKoMvZVW8qoUfF/AJl79 YH4F91TY/lSOa9yfanE85Ogy7DeCRXsMVI2uPIcz4K5lddV+XJ G2shuz+98eNIIh/EK/jjrlQqKeX X-UI-Out-Filterresults: notjunk:1;V01:K0:xghnZ8K46wo=:F4yUtpHKiO41UR4rooLixO OvT16HRbJ0YZzOC+iBOUMm/iJM4FTv07lBmEmJ8F6DJ854nLXgySg81M4WGDg18vSuQCSRpeY ny2bd3e/NqqZ5BBnV+lfFRCerQJ7LD3iVdptaWKjt0L2ohGhMJVPkSe0WWcs7PNXbXQrl7LfU JbglGRIz1Cd2cMLOr4IBJsjUvsQ5CtwJah85ZWre4UI3XeGQD/rco28N8Gk7aT0vQ0mMk+n3f aONpt1SPIyf8nTfPEdQvr3fgXsgAYcUB9CeiITiz91P10VWAQ6gYcIiH5lsMC7zpuR+yV9icm 3OFJiOqe82nVRnxQbdvupK058aDL3/yFD29ifutqwdLT8KLf6VvkyJTesIfWITSEifU04M2+r 72WweasF0BzGeRmMqxm7jX2Mewz7x0Dq1fV/bzd86K2NvW2lHmyCcZJSVg4NoXL7CEYJJBeGA mwBj0jpOew8QnHPK9udXIXNfPGiFPQhyQMfudb4Vui30LjqA5gLrjLUQNJ+JJ2kfcovxxHW6d ODeOrSbni0TjYs+4jFDI0M= X-BeenThere: freebsd-toolchain@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Maintenance of FreeBSD's integrated toolchain List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 02 Jul 2017 01:53:42 -0000 Any drastic change would have to be done in the head branch=2E What about keeping ports' compilers as they are, by not using /usr/local/t= oolchain/* at all=2E Then going with the directory for the base system=2E For instance: /usr/to= olchain/bin/, /usr/toolchain/sbin/, and /usr/toolchain/lib/ for shared file= s=2E Then using /usr/toolchain/clang/ and /usr/toolchain/gcc/ for specifica= lly needed files? of course the directory name can be abbreviated or otherw= ise shortened=2E This suggestion is kind of like the include/ directories= =2E If that's more difficult then, I'll redact my argument=2E In a way it s= hould be more organized=2E However, in another way, perhaps it is more upke= ep, which I intended to propose the opposite effect=2E Fri Jun 30 21:13:32 UTC 2017, Mark Millard wrot= e: >There is some commonality=2E Both contexts are based on >earlier Unix and Unix-like hierarchies=2E And the >commonality helps with making ports and such easier >to support as an example=2E The types of systems are not >completely independent=2E >Lots of tools and such are based on knowing current >placements and general properties of the hierarchies=2E >Reorganizations are a big deal and do not happen >often=2E >It is also messy for ports to organize things differently >than upstream does=2E So things like lang/gcc7-devel are >unlikely to go to the effort of being significantly >different when the commonality covers most of the >placements already (at least for default configurations)=2E Sat Jul 1 10:01:29 UTC 2017, David Chisnall wr= ote: >Debian does something like this, and it=E2=80=99s a huge pain to work wit= h=2E The problem is that toolchains are not self-contained >monolithic com= ponents (though gcc likes to pretend that they are)=2E For example, we wan= t gcc and clang to use the same >linker, the same C and C++ standard librar= y implementations, and the same system headers, irrespective of the compile= r >version=2E Things that actually are private to a compiler are in separa= te directories (see /usr/lib/clang, for example)=2E >David