-
Notifications
You must be signed in to change notification settings - Fork 103
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
compile on Ubuntu 18.04 #14
Comments
Can you try following the instructions on https://github.com/OrchidTechnologies/orchid/blob/master/srv-shared/README.md to see if that helps? |
I was able to get it compiled by following the additional steps:
A guide on where to go from here would be appreciated. I'm looking to setup at least one node with bandwidth for the network. |
I don't seem to get past the iostreams error unless I add cflags += -stdlib=libstdc++ to srv-shared/makefile Then I run into './p2p/cppcoro/include/cppcoro/async_auto_reset_event.hpp:8:10: fatal error: 'experimental/coroutine' file not found' |
The iostream error goes away when you install the appropriate g++ package for your clang version. |
Ah, k, I'm dumb. It was easier for me going to ubuntu 19.10 and following the https://github.com/OrchidTechnologies/orchid/blob/master/srv-shared/README.md after installing the clang, clang++, clang-tidy, libc++-dev, libc++abi-dev and it worked. |
Hi there,
Do you know why is that? |
Hi, |
I reproduced @Geri1590's issue on an install using Fedora 31. The issue lies with the compiler's use of
This changes the linked to use I encountered the same issues on other distros, so there may be something to a PR against the |
Yes I solved it too by deleting ld binary to be able to symlink lld binary to replace the original ld. This was the last error. Then the binary will be built Edit : it’s a little dirty but works Now the thing is how to use it. A lot of args have to be entered from reading the output of —help arg which don’t help me so much. Someone is running orchidd ? |
When we compile orchidd for Linux, even when we do so on Linux, we do it as a cross-compile using debug=crossndk, in order to allow the resulting binary to run on older versions of Linux no matter where it was compiled (and also to get a more consistent build of the binary, as the goal is to have a fully deterministic and reproducible build). I thereby, honestly, just don't ever test "bare" / non-cross Linux compiles. I've gone ahead and added a target orchid-lnx-bad to the GitHub CI in 2180fcd that does a non-cross build of Orchid using the system copy of clang (which of course must be 8 or above, probably 9; you can do this either by selecting the "alternative" with dpkg or setting suffix=-9) and fixed all of the resulting build errors. I will thereby be able to maintain this build going forward to make sure it does not break again. |
command: make all-srv-lnx
Gets to here and fails:
[CC] lnx/x86_64 p2p/./openvpn3/client/ovpncli.cpp
p2p/./openvpn3/client/ovpncli.cpp:24:10: fatal error: 'iostream' file not found
#include
^~~~~~~~~~
1 error generated.
env/output.mk:146: recipe for target 'out-lnx/x86_64/./p2p/./openvpn3/client/ovpncli.cpp.o' failed
make[1]: *** [out-lnx/x86_64/./p2p/./openvpn3/client/ovpncli.cpp.o] Error 1
What am I missing?
The text was updated successfully, but these errors were encountered: