.bashrcdoesn't get sourced when sshing unless you instruct it to be sourced in
.bash_profile. I suggest you go in the machine and clean the build dir. Then try something like this:
ssh -c "export CC="clang-5.0"; export CXX="clang++-5.0"; cd /vagrant/test/net/integration/udp; python test.py"
builddir because I had a previous failed attempt that was messing up all subsequent attempts
sshpass -p 'password' ssh vm2@'ip_address' "export CC="clang-6.0"; export CXX="clang++-6.0"; cd 'path to the directory of udp'; python test.py"
I have used the above one only after making sure that I have cleaned the build directory. I am still facing the error
sshpassis messing up your session because I've never used it
I guess I found the problem. Of course I am not sure.
I am placing the
includeos directory in the folder named
IncludeOS_install (bcoz of previous discussions I had in this group) in
home folder. The error which I posted earlier is mentioning about
not able to load fileas it is searching in the
\usr\localwhich is the default place for the
I am not sure why it is searching over there as I have changed the entry of
INCLUDE_PREFIX in the
So I have changed the entry of
udp folder which I am using.
But I am facing this error
One more issue is, when ever I run in individual VMs, I run as
root and while running from shell script to connect to remote machine it will run as a
user. Will this make difference ?
export CXXFLAGSbut it might not work. If you want to make sure I'd edit
<your-install>/includeos/post.service.cmakewhich comes out of
<repo>/cmake/post.service.cmake. Or I'd ask @KristianJerpetjon :-)