Skip to content

Possible bug in the OTP version management #91

@sylane

Description

@sylane

When having a build section and a specific local version of OTP with a less defined version in the rebar.config, it seems it is confusing the OTP version selection:

rebar.config:

{grisp, [
    {otp, [{version, "26"}]},
    {platform, grisp2},
    {build, [
       {toolchain, [
           {docker, "grisp/grisp2-rtems-toolchain"}
       ]}
    ]},
   ...
]}.
...

Built OTP:

❯ ls -la _grisp/grisp2/otp
total 0
drwxr-xr-x  3 sebastien  staff   96 Aug  1 16:33 .
drwxr-xr-x  3 sebastien  staff   96 Aug  1 16:33 ..
drwxr-xr-x  4 sebastien  staff  128 Aug  1 16:47 26.2.5.2

When building:

===> Compiling grisp_demo
* Resolving OTP version
    26.2.5.3 (requirement was "26")
* Using custom OTP (e2b108e0)
===> Unexpected error: {error,
                                              {rlx_config,
                                               {bad_system_libs,
                                                "/Users/sebastien/.../_grisp/grisp2/otp/26.2.5.3/install/lib"}}}

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions