Setting up a development environment

YlqyY commented 1 year ago

I under the root run curl - proto '= HTTPS' - tlsv1.2 - sSf https://apt.llvm.org/llvm.sh | bash - s - 13 orders, appeared the following contents:

Hit: 1 http://archive.ubuntu.com/ubuntu jammy InRelease Hit: 3 http://archive.ubuntu.com/ubuntu jammy - updates InRelease Hit: 4 http://archive.ubuntu.com/ubuntu jammy - backports InRelease Hit: 6 http://archive.ubuntu.com/ubuntu jammy ws-security InRelease Ignore: 2 https://apt.llvm.org/jammy LLVM toolchain -- jammy - 12 InRelease Hit: 5 https://apt.llvm.org/jammy LLVM toolchain -- jammy - 13 InRelease Error: 7 https://apt.llvm.org/jammy LLVM toolchain -- jammy - 12 Release 404 Not Found [IP: 151.101.54.49443] Reading package list... complete W: http://apt.llvm.org/jammy/dists/llvm-toolchain-jammy-13/InRelease: Key is stored in legacy trusted.gpg keyring (/etc/apt/trusted.gpg), see the DEPRECATION section in apt-key(8) for details. E: warehouse "http://apt.llvm.org/jammy LLVM toolchain -- jammy - 12 Release" no Release documents. N: This source cannot be safely updated, so it is disabled by default. N: See the apt-secure(8) manual for details on warehouse creation and user configuration.

Hope to get your help, thank you!

emil916 commented 1 year ago

Something is wrong, for some packages it picks up version 12. Not really sure whats going on. You may want to skip that script and instead, try installing LLVM manually.

YlqyY commented 1 year ago

I would like to know the version number of Debian you are using and the version number of the dependent tools you are using. Hope to get your help, thank you!

emil916 commented 1 year ago

Ubuntu 20.04 LTS. The list of the deps should be in the repo main directory. The installation should be smooth once Ubuntu 20 is used.

YlqyY commented 1 year ago

The following error occurred after using the make install command:

fatal: no visit ' https://github.com/gwsystems/jsmn.git/ ': Failed to connect to github.com port 443: refuse connect fatal: unaccounted' https://github.com/gwsystems/jsmn.git 'to the model route '/home/yy/sledge-servers-frame/runtime/third party/jsmn' Burkina runtime/third party/jsmn failed. Going to '/home/yy/sledge-serverless-frame/runtime/third party/ck'... fatal: no visit ' https://github.com/gwsystems/ck.git/ ': Failed to connect to github.com port 443: refuse connect fatal: unaccounted' https://github.com/gwsystems/ck.git 'to the model route '/home/yy/sledge-servers-frame/runtime/third party/ck' Second attempt to run time/third party/ck failed, leaving make: ** [Makefile:11: submodules] error 1

How to solve these problems? Hope to get your help, thank you!

emil916 commented 1 year ago

Hum.. Seems the script cannot reach github. You using the docker script or the debian?

YlqyY commented 1 year ago

This is Debian's script, which I executed on ubuntu 20.04.

emil916 commented 1 year ago

Have you made any changes to the original script? If not, I'd like to see the entire output generated in order to be able to say what is the precise issue.

YlqyY commented 1 year ago

I didn't change the original script. Here is the whole process:

yy@yy-virtual-machine :~/sledge-serverless-framework$ make install git submodule update --init --recursive Cloning to '/home/yy/sledge-serverless framework/runtime/thirdparty/ck' Cloning to '/home/yy/sledge-serverless framework/runtime/thirdparty/http parser' Fatal: Unable to access' https://github.com/gwsystems/http-parser.git/ '：GnuTLS recv error (-54): Error in the pull function. Fatal: Cannot clone ' https://github.com/gwsystems/http-parser.git 'Path to sub-module'/home/yy/leade-serverless framework/runtime/thirdparty/http parser ' Failed to clone 'runtime/thirdparty/http parser'. Retry as scheduled Cloning to '/home/yy/sledge-serverless framework/runtime/thirdparty/jsmn' Fatal: Unable to access' https://github.com/gwsystems/jsmn.git/ ': Failed to connect to github.com port 443: refused to connect Fatal: Cannot clone ' https://github.com/gwsystems/jsmn.git 'Path to sub-module'/home/yy/leade-serverless framework/runtime/thirdparty/jsmn ' Failed to clone 'runtime/thirdparty/jsmn'. Retry as scheduled Cloning to '/home/yy/sledge-serverless framework/runtime/thirdparty/http parser' Fatal: Unable to access' https://github.com/gwsystems/http-parser.git/ ': Failed to connect to github.com port 443: refused to connect Fatal: Cannot clone ' https://github.com/gwsystems/http-parser.git 'Path to sub-module'/home/yy/leade-serverless framework/runtime/thirdparty/http parser ' The second attempt to clone 'runtime/thirdparty/http parser' failed. Exit Make: * [Makefile: 11: submiodules] Error 1

Have you made any changes to the original script? If not, I'd like to see the entire output generated in order to be able to say what is the precise issue.

emil916 commented 1 year ago

Humm.. Seems you are having networking issues, which have nothing to do with Sledge. Might also be the case where the "yy" user does not have enough privileges to download in parallel?

I just tried the following git submodule update --init --recursive on a new machine and it works.

Either add the user to the su group or run the above command with sudo git submodule update --init --recursive.

If that fails too, then it must be the either the DNS setttings of the machine or the router, no clue. Again, not Sledge problem.

YlqyY commented 1 year ago

How to deal with the following problems?

root@yy-virtual-machine :/home/yy/sledge-serverless-framework# make install git submodule update --init --recursive Cloning to '/home/yy/sledge-serverless framework/runtime/thirdparty/http parser' Cloning to '/home/yy/sledge-serverless framework/runtime/thirdparty/jsmn' Sub-module path 'runtime/thirdparty/ck': detect '94f37128144287d35274225f99da4927d3f41ab4' Sub-module path 'runtime/thirdparty/http parser': detect '2343fd6b5214b2ded2cdcf76de2bf60903bb90cd' Sub-module path 'runtime/thirdparty/jsmn': check out '053d3cd29200edb1bfd181d917d140c16c1f8834' ln -sr awsm/applications/wasm_ apps/ applications/ cd awsm && cargo build --release error: could not find Cargo.toml in /home/yy/sledge-serverless-framework/awsm or any parent directory Make: * [Makefile: 19: awsm] Error 101

emil916 commented 1 year ago

Hum, the awsm submodule seems to be missing in the submodules list. Have you changed the contents of the .gitsubmodules file? Should be like this: https://github.com/gwsystems/sledge-serverless-framework/blob/master/.gitmodules

In any case, aWsm module must be loaded first. Worst case scenario, do this inside the main sledge folder:

mkdir aWsm
cd aWsm
git clone https://github.com/gwsystems/aWsm.git

And then execute make install again.

YlqyY commented 1 year ago

I didn't change the contents of the .gitsubmodules file, I ran it the way you did and still get the following error:

root@yy-virtual-machine:/home/yy/sledge-serverless-framework# make install git submodule update --init --recursive ln -sr awsm/applications/wasm_apps/ applications/ cd awsm && cargo build --release Finished release [optimized + debuginfo] target(s) in 0.09s warning: the following packages contain code that will be rejected by a future version of Rust: wasmparser v0.58.0 note: to see what the problems were, use the option --future-incompat-report, or run cargo report future-incompatibilities --id 2 make -C libsledge dist/libsledge.a make[1]: Go to the directory "/home/yy/sledge-serverless-framework/libsledge" clang -fPIC -O3 -flto -ftls-model=initial-exec -DNDEBUG -c -Iinclude/ -o dist/control_instructions.o src/control_instructions.c clang -fPIC -O3 -flto -ftls-model=initial-exec -DNDEBUG -c -Iinclude/ -o dist/memory_instructions.o src/memory_instructions.c clang -fPIC -O3 -flto -ftls-model=initial-exec -DNDEBUG -c -Iinclude/ -o dist/numeric_instructions.o src/numeric_instructions.c clang -fPIC -O3 -flto -ftls-model=initial-exec -DNDEBUG -c -Iinclude/ -o dist/table_instructions.o src/table_instructions.c clang -fPIC -O3 -flto -ftls-model=initial-exec -DNDEBUG -c -Iinclude/ -o dist/variable_instructions.o src/variable_instructions.c clang -fPIC -O3 -flto -ftls-model=initial-exec -DNDEBUG -c -Iinclude/ -o dist/instantiation.o src/instantiation.c clang -fPIC -O3 -flto -ftls-model=initial-exec -DNDEBUG -c -Iinclude/ -o dist/wasi_snapshot_preview1.o src/wasi_snapshot_preview1.c clang -fPIC -O3 -flto -ftls-model=initial-exec -DNDEBUG -c -Iinclude/ -o dist/sledge_extensions.o src/sledge_extensions.c ar rcs dist/libsledge.a dist/control_instructions.o dist/memory_instructions.o dist/numeric_instructions.o dist/table_instructions.o dist/variable_instructions.o dist/ instantiation.o dist/wasi_snapshot_preview1.o dist/sledge_extensions.o make[1]: leave directory "/home/yy/sledge-serverless-framework/libsledge" make -C runtime make[1]: Go to the directory "/home/yy/sledge-serverless-framework/runtime" Compiling thirdparty make[2]: You don't need to do anything with "build". make[1]: Leave directory "/home/yy/sledge-serverless-framework/runtime" make -C applications all make[1]: Go to the directory "/home/yy/sledge-serverless-framework/applications" make -C wasm_apps dist/cifar10.wasm make[2]: Go to the directory "/home/yy/sledge-serverless-framework/awsm/applications/wasm_apps" make[2]: There are no rules for making the target "dist/cifar10.wasm". Stop it. make[2]: Leave directory "/home/yy/sledge-serverless-framework/awsm/applications/wasm_apps" make[1]: [Makefile:42:wasm_apps/dist/cifar10.wasm] Error 2 make[1]: Leave directory "/home/yy/sledge-serverless-framework/applications" make: *** [Makefile:47:applications] Error 2

emil916 commented 1 year ago

It does not make sense. I still feel like the awsm repo is not loaded correctly. Can you run the following command in the sledge main directory and copy the output here?

find . | sed -e "s/[^-][^\/]*\// |/g" -e "s/|$[^ ]$/|-\1/"

YlqyY commented 1 year ago

emil916 commented 1 year ago

Okay I was right. I think there problem is you have two directories of the awsm repo.

So. Start fresh. Remove everything. And do this:

git clone https://github.com/gwsystems/sledge-serverless-framework.git sledge
cd sledge/
git clone https://github.com/gwsystems/aWsm.git awsm
cd awsm/
git submodule update --init --recursive
cd ..
make install

YlqyY commented 1 year ago

After i followed the command steps you provided, the following prompt appeared:

warning: the following packages contain code that will be rejected by a future version of Rust: wasmparser v0.58.0 note: to see what the problems were, use the option --future-incompat-report, or run cargo report future-incompatibilities --id 1

---[ Concurrency Kit has installed successfully. Make [2] : * no rule to make target "JSMN/JSMN. H", by "/ home/many/many/runtime/thirdparty/dist / / include/JSMN. H" requirements. Stop. make[1]: [Makefile:161: thirdparty] error 2 Make [1] : leave the directory "/ home/many/many/runtime" make: [Makefile:37: runtime] Error 2

emil916 commented 1 year ago

With all due respect, I believe this issue is either tied to the machine/system you're using or the lack of privileges the user has. Unfortunately, there is nothing else we can help with at this point. I am going to close this thread.

gwsystems / sledge-serverless-framework

Setting up a development environment #372