From the log, it seems that you have managed to build the ebe program, but not ebedecl. I have run into another person who had the same experience. The issue seems to be that the g++/gcc commands are actually implemented as clang++/clang and ebedecl mixes C and C++ which does not work well with clang.
The good news is that ebe can run without ebedecl. Ebedecl 's purpose is to parse assembly code to determine the components of structs (struc in yasm).
One possible immediate solution would be to prefix gcc and g++ in ebe/ebedecl/Makefile with /usr/local/bin to force the make command to build ebedecl with gcc/g++. Then issuing "make" from ebe/ebedecl should succeed and then you could copy ebedecl to /usr/bin to make it available.
My plan is to convert ebedecl to be entirely C which should then compile with with clang or gcc. This may take me a little time. It should have little impact on early use of ebe for assembly programming.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
From the log, it seems that you have managed to build the ebe program, but not ebedecl. I have run into another person who had the same experience. The issue seems to be that the g++/gcc commands are actually implemented as clang++/clang and ebedecl mixes C and C++ which does not work well with clang.
The good news is that ebe can run without ebedecl. Ebedecl 's purpose is to parse assembly code to determine the components of structs (struc in yasm).
One possible immediate solution would be to prefix gcc and g++ in ebe/ebedecl/Makefile with /usr/local/bin to force the make command to build ebedecl with gcc/g++. Then issuing "make" from ebe/ebedecl should succeed and then you could copy ebedecl to /usr/bin to make it available.
My plan is to convert ebedecl to be entirely C which should then compile with with clang or gcc. This may take me a little time. It should have little impact on early use of ebe for assembly programming.