On Sat, Sep 15, 2018 at 05:19:40PM -0700, William Orr wrote:
> This diff adds erlang major versions 20 and 21. Tested by building
> elixir and running the test suite.
How did you do so when the respective devel/rebar flavours are missing?

kn:/usr/ports/lang/elixir:4362$ make MODERL_VERSION=21 test
===>  Checking files for elixir-1.7.3
`/var/distfiles/elixir-1.7.3.tar.gz' is up to date.
>> (SHA256) elixir-1.7.3.tar.gz: OK
Invalid FLAVOR set: erlang21 (in devel/rebar)
Fatal: Unknown flavor: erlang21 (in devel/rebar)
   (Possible flavors are: erlang16 erlang17 erlang18 erlang19 ). (in 
devel/rebar)
*** Error 1 in /usr/ports/devel/rebar 
(/usr/ports/infrastructure/mk/bsd.port.mk:3528 '.BEGIN': @exit 1)
Problem with dependency devel/rebar,erlang21
*** Error 1 in . (/usr/ports/infrastructure/mk/bsd.port.mk:2107 
'/tmp/pobj/elixir-1.7.3/.dep-devel-rebar,erlang21')
*** Error 1 in . (/usr/ports/infrastructure/mk/bsd.port.mk:2498 
'/tmp/pobj/elixir-1.7.3/.extract_done')
*** Error 1 in /usr/ports/lang/elixir 
(/usr/ports/infrastructure/mk/bsd.port.mk:2419 'test')


That said, we need to port https://github.com/erlang/rebar3 as our
rebar-2.6.2 is deprecated.

> Given that erlang 16 is no longer supported, it may be a good idea
> to remove that, however I haven't included that change in my diff.
I agree, but that's a job for after the 6.4 release.  Since 16 is the
default version in our tree, which should be next?  Either ways, this
should go through a bulk build.

> The 20 and 21 dirs are included in the tarball.
Both build fine on sparc64.

Reply via email to