From owner-freebsd-toolchain@freebsd.org Sat Jul 15 23:34:37 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 0670AB7E127 for ; Sat, 15 Jul 2017 23:34:37 +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 B57F43B3E for ; Sat, 15 Jul 2017 23:34:36 +0000 (UTC) (envelope-from sid@bsdmail.com) Received: from [108.70.50.7] by 3capp-mailcom-lxa10.server.lan (via HTTP); Sun, 16 Jul 2017 01:21:39 +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, 16 Jul 2017 01:21:39 +0200 Importance: normal Sensitivity: Normal Content-Transfer-Encoding: quoted-printable X-Priority: 3 X-Provags-ID: V03:K1:Sb/nB46LJWiyU4KypWS8/iZZb6vfVfw+Y8TfQ5aIFTJ GcuoLU4rMfCKi2RosDTnkH5Nwr863yCZppeVlyy/v1CJggVu+B CFNoly2M9NTK7IIEjfgwPzeqP0wd7dzeCjOLiULBqLhAWOfG99 NFrCXuZ9Xm1Teu4NCHcwQMzjIn0Oc+tWzu7vQjJDV971kBxUTT MQkcGnTsI9hoCwk+lSVjKfitKnhoDILENvvkUqtYgVd7XTkzQm VluGn9scHKiaaOwiqC2UVVYLMSJXSP9TZNx3FXgBmP783QNMT8 kgJb6xL6/el+6e9mNfyrMHSn1RQ X-UI-Out-Filterresults: notjunk:1;V01:K0:thnb8RJ2jpY=:tt1xXhLGnGijU2hJESIW48 yyUi6+aREEK8kuFGP7w1lIKsoAC02kLPqi7qEx7pOeuqkcD44y82XwllAOCEHK7D6fO+kmFVp rfom/F6dF7EPKKOsbyzL+e6ybnTAPUizLXGRTyS00h4ARuvxlDNPv1LdCXXcynHGJ2W3HrlKj i64OrP98ojgmfEGb1uFhVnkJKDzcnFU/c7DTQZNUVSqctHbTQeICK+BNQwvoF61CCqN+I8yA7 715Qkrz73fcrF09tSH7/I2+BEQfbEn4kdUl1W4AvppvuJ/fGurHr1ct4dgywS1y1PSf+Wft7V nprWRpmfMjdgnIc6hWXnLrAd1mMuqIgDlN59bx/SQuFtCsQBDdYOnqtvcTUx7kRw8SSS+RYnk BIKiVzu4290nOFeEjpi8l7XL6//UrSFlu8zJUhBdEHgddTyu1z0E0/orrvQpIMRtvfAT6T4E5 fimP/dURhGGdrnlshBdeVaEfSkCq6eHaUk5kgApUYjoTALJcJjXm6ZOJt/HNeyY907e21EVn1 RUTmnKslax6gKdzSL4fME7tiZs2W86ucxNnGMjMNDm7 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: Sat, 15 Jul 2017 23:34:37 -0000 How about going with a toolchain directory for the base system only=2E It w= ould use shared files, and have subdirectories specific to clang, gcc, or o= ther compiling components or versions=2E This way it is both modular and or= ganized=2E For instance: /usr/toolchain/bin/, /usr/toolchain/sbin/, and /usr/toolchai= n/lib/ can be used for shared files=2E /usr/toolchain/clang/, /usr/toolchai= n/gcc/, etc, and their (lib, sbin, bin, include) subdirectories can be used= for specifically needed files=2E The old directories can be softlinked to = there=2E Any drastic changes can only be tried in the head branch=2E Port compilers= should definitely be left alone, by not using /usr/local/toolchain/* at al= l=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 comp= onents (though gcc likes to pretend that they are)=2E For example, we want = gcc and clang to use the same >linker, the same C and C++ standard library = implementations, and the same system headers, irrespective of the compiler = >version=2E Things that actually are private to a compiler are in separate = directories (see /usr/lib/clang, for example)=2E Fri Jun 30 21:13:32 UTC 2017, Mark Millard wrot= e: >commonality helps with making ports and such easier >to support as an example=2E The types of systems are not >completely independent=2E =2E=2E=2E >Reorganizations are a big deal and do not happen >often=2E =2E=2E=2E >It is also messy for ports to organize things differently >than upstream does=2E