Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

build_static.sh not working for recent release versions #551

Open
joexue opened this issue Dec 5, 2022 · 12 comments
Open

build_static.sh not working for recent release versions #551

joexue opened this issue Dec 5, 2022 · 12 comments

Comments

@joexue
Copy link

joexue commented Dec 5, 2022

If you have set up ET correctly and are having an issue connecting/maintaining a session, please consider running in verbose mode and adding client & server logs to your issue.

To run in verbose mode, pass the --verbose=9 flag to et.

To collect logs, run the following on your client:

tar -cvzPhf /tmp/etclientLogs.tar.gz /tmp/etclient_err /tmp/etclient.INFO

Then run this on your server:

tar -cvzPhf /tmp/etserverLogs.tar.gz /tmp/etserver_err /tmp/etserver.INFO

The logs will contain the IP addresses & username of the client and server, but will not contain any of the data transmitted.

If you are experiencing a crash, please also post a backtrace. To do this, replace this line in your et script:

CLIENT_BINARY="etclient"

to this:

CLIENT_BINARY="lldb -- etclient"

then rerun with lldb and when it crashes, type "bt" to give me the stack trace. If you are running the client under linux, replace with:

CLIENT_BINARY="gdb --args etclient"

@jshort jshort changed the title build_statis.sh not working for recent release versions build_static.sh not working for recent release versions Dec 5, 2022
@jshort
Copy link
Collaborator

jshort commented Dec 5, 2022

@joexue Can you explain what the issue is: errors, logs etc?

@joexue
Copy link
Author

joexue commented Dec 6, 2022

-- Architecture: aarch64
-- VCPKG TRIPLET: arm64-linux
-- Bootstrapping vcpkg before install
-- Bootstrapping vcpkg before install - failed
CMake Error at external/vcpkg/scripts/buildsystems/vcpkg.cmake:863 (message):
vcpkg install failed. See logs for more information:
/home/joe/test/EternalTerminal/build/vcpkg-bootstrap.log
Call Stack (most recent call first):
deps/out/share/cmake-3.15/Modules/CMakeDetermineSystem.cmake:93 (include)
CMakeLists.txt:76 (project)
CMake Error: CMake was unable to find a build program corresponding to "Unix Makefiles". CMAKE_MAKE_PROGRAM is not set. You probably need to select a different build tool.
-- Configuring incomplete, errors occurred!

EternalTerminal/build/vcpkg-bootstrap.log

Unable to determine a binary release of vcpkg; attempting to build from source.
Building vcpkg-tool...
CMake Error at CMakeLists.txt:1 (cmake_minimum_required):
CMake 3.15 or higher is required. You are running version 3.12.1
-- Configuring incomplete, errors occurred!

@joexue
Copy link
Author

joexue commented Dec 6, 2022

By the way manually change the cmake dependency version doesn't help, because it use cmake from system instead of using the cmake built by it self

@jshort
Copy link
Collaborator

jshort commented Dec 6, 2022

@joexue can you confirm that export PATH="$PWD"/out/bin:/usr/sbin:/usr/bin:/sbin:/bin is setting your path correctly and that $PWD/out/bin has cmake of the correct version (higher than 3.15)?

@joexue
Copy link
Author

joexue commented Dec 6, 2022

@joexue can you confirm that export PATH="$PWD"/out/bin:/usr/sbin:/usr/bin:/sbin:/bin is setting your path correctly and that $PWD/out/bin has cmake of the correct version (higher than 3.15)?

do you mean the build will set the path or I have to set path myself?

I set it and not working

build/vcpkg-bootstrap.log

Unable to determine a binary release of vcpkg; attempting to build from source.
Building vcpkg-tool...
CMake Error: CMake was unable to find a build program corresponding to "Ninja". CMAKE_MAKE_PROGRAM is not set. You probably need to select a different build tool.
CMake Error: CMAKE_CXX_COMPILER not set, after EnableLanguage
-- Configuring incomplete, errors occurred!
See also "/home/joe/test/EternalTerminal/external/vcpkg/buildtrees/_vcpkg/build/CMakeFiles/CMakeOutput.log".

build/CMakeFiles/CMakeOutput.log

The system is: Linux - 4.19.36-vhulk1907.1.0.h453.eulerosv2r8.aarch64 - aarch64

@joexue
Copy link
Author

joexue commented Dec 6, 2022

~/test/EternalTerminal/build$ cmake --version
cmake version 3.15.2

CMake suite maintained and supported by Kitware (kitware.com/cmake).

@jshort
Copy link
Collaborator

jshort commented Dec 7, 2022

do you mean the build will set the path or I have to set path myself?

No, the script does exactly that, but I was just implying that you can add some debug to the script to confirm (see below).

Try ~/test/EternalTerminal/out/bin/cmake --version, that is the cmake executable that will be used during the build process. In the build_static.sh you can call which cmake to confirm that is the cmake being used.

However, your most recent error CMake Error: CMAKE_CXX_COMPILER implies that cmake can't find a c++ compiler (g++, clang etc).

@joexue
Copy link
Author

joexue commented Dec 8, 2022

do you mean the build will set the path or I have to set path myself?

No, the script does exactly that, but I was just implying that you can add some debug to the script to confirm (see below).

Try ~/test/EternalTerminal/out/bin/cmake --version, that is the cmake executable that will be used during the build process. In the build_static.sh you can call which cmake to confirm that is the cmake being used.

However, your most recent error CMake Error: CMAKE_CXX_COMPILER implies that cmake can't fine a c++ compiler (g++, clang etc).

I'm sure the cmake version I'm using is the built one 3.15.2, I also sure the g++ is there, the protobuf is built successfully already priors to "vcpng". Can you just try to do the something if you have the environment?

@jshort
Copy link
Collaborator

jshort commented Dec 8, 2022

I haven't ever used that script and it hasn't been updated in 3 years so I'm going to assume it is in need of updates (or we can just delete it). Have you tried just using the Build From Source instructions in the README: https://github.com/MisterTea/EternalTerminal#building-from-source ? I've used them on CentOS and MacOS and have had no problems.

If you feel like bringing build_static.sh up to date, we'd happily accept a PR, but purely based on the versions of the deps, I'm guessing that script is hopeless in its current form.

@joexue
Copy link
Author

joexue commented Dec 12, 2022

I haven't ever used that script and it hasn't been updated in 3 years so I'm going to assume it is in need of updates (or we can just delete it). Have you tried just using the Build From Source instructions in the README: https://github.com/MisterTea/EternalTerminal#building-from-source ? I've used them on CentOS and MacOS and have had no problems.

If you feel like bringing build_static.sh up to date, we'd happily accept a PR, but purely based on the versions of the deps, I'm guessing that script is hopeless in its current form.

Let me raise PR once I get a change to dig it and find the solution. Thanks

@Lotusshaney
Copy link

Getting the same problem on macOS 14 using the https://github.com/MisterTea/EternalTerminal#building-from-source process at the cmake ../ part

@MisterTea
Copy link
Owner

@Lotusshaney try to brew update and install again. I made some changes.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants