Skip to content

Elixir does not build #174

Description

@mikeowens
cd /opt/pkgsrc/lang/elixir
bmake
=> Bootstrap dependency digest>=20010302: found digest-20180917
=> Fetching elixir-1.7.4.tar.gz
=> Total size: 2139938 bytes
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100   126    0   126    0     0    408      0 --:--:-- --:--:-- --:--:--   442
100 2089k    0 2089k    0     0  2261k      0 --:--:-- --:--:-- --:--:-- 2261k
=> Checksum SHA1 OK for elixir-1.7.4.tar.gz
=> Checksum RMD160 OK for elixir-1.7.4.tar.gz
=> Checksum SHA512 OK for elixir-1.7.4.tar.gz
===> Installing dependencies for elixir-1.7.4
=> Tool dependency gmake>=3.81: found gmake-4.2.1nb1
=> Tool dependency nbpatch-[0-9]*: found nbpatch-20151107
=> Build dependency gcc7>=7.3: found gcc7-7.3.0nb4
=> Build dependency cwrappers>=20150314: found cwrappers-20180325
=> Full dependency erlang>=18.0: found erlang-21.2.4
===> Overriding tools for elixir-1.7.4
===> Extracting for elixir-1.7.4
===> Patching for elixir-1.7.4
=> Applying pkgsrc patches for elixir-1.7.4
===> Creating toolchain wrappers for elixir-1.7.4
===> Configuring for elixir-1.7.4
=> Replacing elixir interpreter in bin/mix.
===> Building for elixir-1.7.4
/bin/sh[1]: cd: lib/elixir: [No such file or directory]
gmake: *** [Makefile:65: erlang] Error 1
*** Error code 2

Stop.
bmake[1]: stopped in /opt/pkgsrc/lang/elixir
*** Error code 1

Stop.
bmake: stopped in /opt/pkgsrc/lang/elixir

From what I can tell, /bin/sh (ksh93) does not like stepping into directories called 'lib' which is a mystery to me. For example:

/bin/sh
[033[01;31m]dev [033[01;34m]W $ [033[00m]cd /tmp
[033[01;31m]dev [033[01;34m]W $ [033[00m]mkdir lib
[033[01;31m]dev [033[01;34m]W $ [033[00m]cd lib
/bin/sh: cd: lib: [No such file or directory]
[033[01;31m]dev [033[01;34m]W $ [033[00m]

Activity

  1. jperkin commented on Jan 30, 2019

    @jperkin
    Collaborator

    I can't reproduce the "cd lib" failure, is there something in your profile that would be causing this?

  2. self-assigned this
    on Jan 30, 2019
  3. mikeowens commented on Jan 30, 2019

    @mikeowens
    Author

    Well this doesn't happen in global zone either. So maybe I screwed up my build zone. I will create a new zone from scratch and start over.

  4. added a commit that references this issue on Jul 1, 2019
  5. added a commit that references this issue on Nov 6, 2019
  6. added a commit that references this issue on Nov 15, 2019
  7. added a commit that references this issue on Dec 15, 2019
  8. added a commit that references this issue on Mar 5, 2020
  9. added a commit that references this issue on May 3, 2020
  10. added a commit that references this issue on May 20, 2020
  11. 104 remaining items

  12. added a commit that references this issue on Jul 30, 2026
  13. added a commit that references this issue on Aug 26, 2026
  14. added a commit that references this issue on Sep 6, 2026
  15. added a commit that references this issue on Sep 22, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

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