Btw, ther is a gdc which stil uses c++ version of dfrontend, so on DragonFlyBSD you can build dmd using gdc.
On Mon, Jan 15, 2018 at 2:25 PM, Daniel Kozak <kozz...@gmail.com> wrote: > So why not to use cross compilation? > > On Mon, Jan 15, 2018 at 2:10 PM, Joakim via Digitalmars-d < > digitalmars-d@puremagic.com> wrote: > >> On Monday, 15 January 2018 at 12:15:27 UTC, Temtaime wrote: >> >>> And what builds C++ compiler from source ? :) >>> >> >> The system C/C++ compiler is already built and there, obviously. Since >> nobody ships a D compiler with their OS, I'm not sure how you think that's >> relevant. >> >> On Monday, 15 January 2018 at 12:36:04 UTC, Daniel Kozak wrote: >> >>> Exactly, there is no reason to build 2.067, 2.076, and 2.078, just build >>> the latest one with the previos one. It is common (in case you do not have >>> dlang compiler in your distribution) to start with downloading existing >>> binary and compile lastest version as a package, then you can use this >>> package as a dependency for building new versions. >>> >> >> There is no existing binary for an OS that doesn't have a port yet! >> >> Take the current DragonFlyBSD port that's being done: he had to port both >> dmd 2.067, which is written in C++, and the latest dmd master to DragonFly, >> in order to have source packages for their ports repository: >> >> https://github.com/dlang/dmd/pull/7463 >> >> If you bump the D compiler required for latest master, he'll have to port >> every bumped D compiler too, ie 2.067, 2.076, and 2.078, in order to have a >> source package. That's going to be a huge pain that will stop many from >> doing the initial port. >> > >