On 2017/03/02 22:03, Karel Gardas wrote:
> On Thu, Mar 2, 2017 at 9:23 PM, Matthias Kilian <k...@outback.escape.de>
> wrote:
> > Also, I've no idea wether --with-clang=${CC} will work after the
> > switch to clang. On the other hand, the diff is just a workaround,
>
> > +MODGHC_SETUP_CONF_ARGS += --with-gcc=${CC} --with-clang=${CC}
>
>
> Hi Kili,
>
> I'm curious why this is there at all, I mean --with-clang=${CC} -- if
> I understand policy, then i386/amd64 are not going to be migrated to
> clang anytime soon and clang is default only for arm64 (new port which
> is not supported by in tree gcc) where ghc does not exist yet. So my
> curiosity and question why to bother with it at all?
One of the prerequisites for switching other architectures is that it
won't cause too much damage to the ports tree..
