Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 16 Jul 2017 01:21:39 +0200
From:      Sid <sid@bsdmail.com>
To:        freebsd-toolchain@freebsd.org
Subject:   Re: suggestion for toolchain to have its own directories
Message-ID:  <trinity-bc87df55-8a78-40d5-9636-372de83ec91e-1500160899153@3capp-mailcom-lxa10>

next in thread | raw e-mail | index | archive | help
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 <theraven at FreeBSD=2Eorg> 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 <markmi at dsl-only=2Enet> 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



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?trinity-bc87df55-8a78-40d5-9636-372de83ec91e-1500160899153>