Sorry, I missed this post. On 20/3/19 10:34 pm, Adam Lindberg wrote: > I tried building our project in a completely clean macOS VM and that seems to > work. In my current environment I reduced the Homebrew packages to: > > bat pcre > bison pcre2 > exa python@2 > flex readline > gdbm reattach-to-user-namespace > gettext sqlite > git texinfo > libevent tmux > mercurial xz > ncurses zlib > openssl zsh > > I also reduced $PATH to the default macOS settings and removed any envs I > could think of that looked non-standard but I still get the error.
Did you try the clean machine with just Xcode to verify my results? > Is there _any_ way to actually make Was output some verbose info about what > it is doing and why it thinks its appropriate to create the directory "///o"? Running `./waf --help` shows the available commands. There is adding `-v` a number of times and during the configure phase add `--show-commands`. Chris _______________________________________________ users mailing list users@rtems.org http://lists.rtems.org/mailman/listinfo/users
