Sunday, June 30, 2019

Re: llvm-7.0.1 fallout: lang/crystal

On Sun, Jun 30, 2019 at 06:18:38PM +0200, Jeremie Courreges-Anglas wrote:
>
> Hi Wesley,
>
> On Wed, Feb 13 2019, Wesley Moxam <wesley.moxam@gmail.com> wrote:
> >> On Feb 13, 2019, at 7:47 AM, Jeremie Courreges-Anglas <jca@wxcvbn.org> wrote:
> >>
> >>> On Thu, Feb 07 2019, Stuart Henderson <stu@spacehopper.org> wrote:
> >>>> On 2019/02/07 18:02, Jeremie Courreges-Anglas wrote:
> >>>>
> >>>> Hi,
> >>>>
> >>>> I'm not sure you were notified so here's a heads-up: lang/crystal
> >>>> doesn't build any more after the update to clang 7 in both base and
> >>>> ports.
> >>>
> >>> Not handled upstream yet.
> >>> https://github.com/crystal-lang/crystal/issues/6754
> >>
> >> Wesley, I see that you have commented on this issue. Do you mind if
> >> we mark lang/crystal as temporarily BROKEN?
> >
> > That's fine with me. It may be a while before the issue is fixed
>
> Any news regarding lang/crystal? The issue is still open and "@bcardiff
> removed this from the 0.28.0 milestone on Mar 27".
>
> If upstream doesn't plan to support newer llvm releases and no
> alternative fix is found, then the port should be removed.

I don't know much about it, but can't it be built with ports gcc?

--
Antoine

No comments:

Post a Comment