Building on a Mac

[torntrousers]

I run esp-rs/build.sh --install and get the following fail:

esp-rs/build.sh --install
info: component 'rust-std' for target 'i686-unknown-linux-gnu' is up to date
Building mrustc/minicargo@b5b7089
make: Nothing to be done for `RUSTCSRC'.
/Applications/Xcode.app/Contents/Developer/usr/bin/make -f Makefile all
[CXX] -o .obj/main.o
In file included from src/main.cpp:25:
In file included from src/trans/main_bindings.hpp:10:
src/trans/trans_list.hpp:62:1: warning: 'TransList' defined as a class here but previously declared as a struct [-Wmismatched-tags]
class TransList
^
src/mir/main_bindings.hpp:14:1: note: did you mean class here?
struct TransList;
^~~~~~
class
src/main.cpp:72:3: error: "Unable to detect a suitable default target"
# error "Unable to detect a suitable default target"
  ^
src/main.cpp:181:30: error: use of undeclared identifier 'DEFAULT_TARGET_NAME'
    ::std::string   target = DEFAULT_TARGET_NAME;
                             ^
1 warning and 2 errors generated.
make[1]: *** [.obj/main.o] Error 1
make: *** [bin/mrustc] Error 2
C02V83QTG8WN-478:rust-esp8266 anthonyelder$

Any ideas on how to fix or debug this?

[torntrousers]

Adding define DEFAULT_TARGET_NAME "x86_64-apple-macosx" in src/main.cpp got past that but hit two further errors, fixed with:

git diff src/expand/proc_macro.cpp
diff --git a/src/expand/proc_macro.cpp b/src/expand/proc_macro.cpp
index d34a91a5..0c29a215 100644
--- a/src/expand/proc_macro.cpp
+++ b/src/expand/proc_macro.cpp
@@ -27,6 +27,7 @@
 #if defined(__OpenBSD__) || defined(__NetBSD__)
 extern char **environ;
 #endif
+extern char **environ;

 #define NEWNODE(_ty, ...)   ::AST::ExprNodeP(new ::AST::ExprNode##_ty(__VA_ARGS__))

and

git diff Makefile
diff --git a/Makefile b/Makefile
index 18415510..2b734aa3 100644
--- a/Makefile
+++ b/Makefile
@@ -308,9 +308,9 @@ $(BIN): $(OBJ) tools/bin/common_lib.a
        $V$(CXX) -o $@ $(LINKFLAGS) $(OBJ) tools/bin/common_lib.a $(LIBS)
 ifeq ($(OS),Windows_NT)
 else
-       objcopy --only-keep-debug $(BIN) $(BIN).debug
-       objcopy --add-gnu-debuglink=$(BIN).debug $(BIN)
-       strip $(BIN)
+       gobjcopy --only-keep-debug $(BIN) $(BIN).debug
+       gobjcopy --add-gnu-debuglink=$(BIN).debug $(BIN)
+       # strip $(BIN)
 endif

but then it fails with:

esp-rs/build.sh --install
info: component 'rust-std' for target 'i686-unknown-linux-gnu' is up to date
Building mrustc/minicargo@b5b7089
make: Nothing to be done for `RUSTCSRC'.
/Applications/Xcode.app/Contents/Developer/usr/bin/make -f Makefile all
[CXX] -o .obj/expand/proc_macro.o
[CXX] -o bin/mrustc
gobjcopy --only-keep-debug bin/mrustc bin/mrustc.debug
gobjcopy --add-gnu-debuglink=bin/mrustc.debug bin/mrustc
# strip bin/mrustc
test -e bin/mrustc
/Applications/Xcode.app/Contents/Developer/usr/bin/make -C tools/minicargo/
make[1]: Nothing to be done for `all'.
test -e tools/bin/minicargo
tools/bin/minicargo rustc-1.19.0-src/src/libstd --script-overrides script-overrides/stable-1.19.0-linux/ --output-dir output/
EXCEPTION: Empty path being constructed
make: *** [output/libstd.hir] Error 1

Trying:

C02V83QTG8WN-478:mrustc anthonyelder$ pwd
/Users/anthonyelder/.esp-rs/mrustc
C02V83QTG8WN-478:mrustc anthonyelder$ bin/mrustc rustc-1.19.0-src/src/libcore/lib.rs --crate-name core --crate-type rlib -g --cfg debug_assertions -O -o output/libcore.hir -L output
Killed: 9

Actually, simply bin/mrustc gives Killed: 9.

Any ideas how to fix that?

[arve0]

Using the Dockerfile seems to work:

git clone https://github.com/emosenkis/esp-rs
cd esp-rs
docker build .

[torntrousers]

I gave the Dockerfile a try, it seemed to be going well and spent ages compiling stuff then eventually failed with:

...
Run Build- DEBUG: - rustdoc has 7 deps remaining
Run Build- DEBUG: Building output/rustc-build/librustc.hir - Missing
BUILDING rustc from rustc v0.0.0 with features []
Run Build- Calling /root/.esp-rs/mrustc/bin/mrustc rustc-1.19.0-src/src/librustc/lib.rs --crate-name rustc --crate-type rlib -g --cfg debug_assertions -O -o output/rustc-build/librustc.hir -L output/rustc-build --extern arena=output/rustc-build/libarena.hir --extern fmt_macros=output/rustc-build/libfmt_macros.hir --extern graphviz=output/rustc-build/libgraphviz.hir --extern log=output/rustc-build/liblog-0_3_7.hir --extern owning_ref=output/rustc-build/libowning_ref-0_3_3.hir --extern rustc_back=output/rustc-build/librustc_back.hir --extern rustc_bitflags=output/rustc-build/librustc_bitflags.hir --extern rustc_const_math=output/rustc-build/librustc_const_math.hir --extern rustc_data_structures=output/rustc-build/librustc_data_structures.hir --extern rustc_errors=output/rustc-build/librustc_errors.hir --extern serialize=output/rustc-build/libserialize.hir --extern syntax=output/rustc-build/libsyntax.hir --extern syntax_pos=output/rustc-build/libsyntax_pos.hir -L output
Run Build- DEBUG: Environment { OUT_DIR=/root/.esp-rs/mrustc/output/rustc-build/build_rustc CARGO_MANIFEST_DIR=/root/.esp-rs/mrustc/rustc-1.19.0-src/src/librustc CARGO_PKG_VERSION=0.0.0 CARGO_PKG_VERSION_MAJOR=0 CARGO_PKG_VERSION_MINOR=0 CARGO_PKG_VERSION_PATCH=0 }
BUILD FAILED
Run Build- DEBUG: Compiler was terminated with signal 9
Run Build- DEBUG: See output/rustc-build/librustc.hir_dbg.txt for the compiler output
minicargo.mk:83: recipe for target 'output/rustc' failed
make: *** [output/rustc] Error 1
The command '/bin/sh -c ./build.sh --install' returned a non-zero code: 1

I can't find output/rustc-build/librustc.hir_dbg.txt (docker newbie), where is that?

[arve0]

Probably inside the docker file system. Normally you can get a terminal inside the image with

docker exec container-name bash

, but unsure if this holds for crashed images. You can list your containers with docker ps -a to get the container-name.

[torntrousers]

docker ps -a
CONTAINER ID        IMAGE               COMMAND                  CREATED             STATUS                   PORTS               NAMES
d877e27ad42a        3283fc1eaec7        "/bin/sh -c './bui..."   3 days ago          Exited (1) 2 hours ago                       objective_hypatia
$ docker exec d877e27ad42a bash
Error response from daemon: Container d877e27ad42aa0205ab6e64d5e3edc7905e768ddd82eaf0f3e7381ad8166b501 is not running

[arve0]

You might try docker run -i -t --entrypoint /bin/bash container-name.

Anyhow, on first attempt, docker build failed with out of space, fixed in Docker preferences → Disk.

Second attempt went well:

tool-esptool @ 1.413.0 has been successfully installed!
The platform 'espressif8266' has been successfully installed!
The rest of packages will be installed automatically depending on your build environment.
Removing intermediate container 6b3522c2d389
 ---> ac39d4399729
Successfully built ac39d4399729

Docker image size is ~20GB:

$ docker images
REPOSITORY                                          TAG                 IMAGE ID            CREATED             SIZE
<none>                                              <none>              ac39d4399729        26 minutes ago      19.4GB

[emosenkis]

Anything here that you might be able to add to the Dockerfile, README, or build.sh to help others have an easier time with this? I'd be happy to get a pull request.

[emosenkis]

@antonok-edm who initially contributed the Dockerfile

[antonok-edm]

It's hard to tell without confirmation from @torntrousers but that looks to me like it could have been a disk space error. If so, adding information about the required disk space would certainly be useful.

[torntrousers]

I can't see how to change the disk space. In the Docker Preferences, in the Advanced tab where I can set CPUs and memory, it shows the location of the disk image but mentions nothing about changing the size (looking in Mac Finder its 38.21GB).

[antonok-edm]

@torntrousers Docker doesn't impose any artificial limits on a container's available disk space, so check that you still have space on the drive your Docker images are located on.

[arve0]

Docker doesn't impose any artificial limits on a container's available disk space

That is correct for linux, but not for Mac, at least not for version 18.06:

[torntrousers]

I had an older version of Docker, newer versions for a Mac do have a disk option, so I've updated to Version 2.0.0.0-mac82 (29268). I've set the disk size to 64.0GB which is the max it would let me. Then I deleted all the old docker images with docker system prune -a and that ended with Total reclaimed space: 30.13GB. Then built this, with docker build . and that trundled away for a couple of hours and failed, the end of the log is:

...
Run Build- DEBUG: - rustdoc has 7 deps remaining
Run Build- DEBUG: Building output/rustc-build/librustc.hir - Missing
BUILDING rustc from rustc v0.0.0 with features []
Run Build- Calling /root/.esp-rs/mrustc/bin/mrustc rustc-1.19.0-src/src/librustc/lib.rs --crate-name rustc --crate-type rlib -g --cfg debug_assertions -O -o output/rustc-build/librustc.hir -L output/rustc-build --extern arena=output/rustc-build/libarena.hir --extern fmt_macros=output/rustc-build/libfmt_macros.hir --extern graphviz=output/rustc-build/libgraphviz.hir --extern log=output/rustc-build/liblog-0_3_7.hir --extern owning_ref=output/rustc-build/libowning_ref-0_3_3.hir --extern rustc_back=output/rustc-build/librustc_back.hir --extern rustc_bitflags=output/rustc-build/librustc_bitflags.hir --extern rustc_const_math=output/rustc-build/librustc_const_math.hir --extern rustc_data_structures=output/rustc-build/librustc_data_structures.hir --extern rustc_errors=output/rustc-build/librustc_errors.hir --extern serialize=output/rustc-build/libserialize.hir --extern syntax=output/rustc-build/libsyntax.hir --extern syntax_pos=output/rustc-build/libsyntax_pos.hir -L output
Run Build- DEBUG: Environment { OUT_DIR=/root/.esp-rs/mrustc/output/rustc-build/build_rustc CARGO_MANIFEST_DIR=/root/.esp-rs/mrustc/rustc-1.19.0-src/src/librustc CARGO_PKG_VERSION=0.0.0 CARGO_PKG_VERSION_MAJOR=0 CARGO_PKG_VERSION_MINOR=0 CARGO_PKG_VERSION_PATCH=0 }
The command '/bin/sh -c ./build.sh --install' returned a non-zero code: 137

Any ideas on that?

[torntrousers]

Success! I upped the Docker memory to 6GB and swap to 1.5GB ( I can't remember what there were before) and tried again and now it works.

...
Unpacking
tool-esptool @ 1.413.0 has been successfully installed!
The platform 'espressif8266' has been successfully installed!
The rest of packages will be installed automatically depending on your build environment.
Removing intermediate container 493e729a21ba
 ---> 49363eba1b56
Successfully built 49363eba1b56
$

Now what? Has it built a binary image somewhere I can flash on an ESP8266?