<div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr">On Thu, 7 Mar 2019 at 00:49, Harshavardhan Unnibhavi <<a href="mailto:hvubfoss@gmail.com">hvubfoss@gmail.com</a>> wrote:<br></div><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div>Hi,</div><div>I have built criu. But while running tests, I get an error as follows:</div><div><br></div><div>./zdtm.py run -a --parallel 2<br>./zdtm.py:21: DeprecationWarning: the imp module is deprecated in favour of importlib; see the module's documentation for alternative uses<br> import imp<br>make[3]: *** No rule to make target 'umount2'. Stop.<br>Traceback (most recent call last):<br> File "./zdtm.py", line 2304, in <module><br> tst.available()<br> File "./zdtm.py", line 566, in available<br> subprocess.check_call(["make", "umount2"])<br> File "/usr/lib/python3.7/subprocess.py", line 347, in check_call<br> raise CalledProcessError(retcode, cmd)<br>subprocess.CalledProcessError: Command '['make', 'umount2']' returned non-zero exit status 2.<br>Makefile:23: recipe for target 'zdtm' failed<br>make[2]: *** [zdtm] Error 1<br>Makefile:7: recipe for target 'all' failed<br>make[1]: *** [all] Error 2<br>Makefile:294: recipe for target 'test' failed<br>make: *** [test] Error 2</div><div><br></div><div>Is it because of the absence of a make rule in the test/Makefile ? Will adding a make target and rule for umount2 help in the Makefile?</div></div></div></div></blockquote><div><br></div><div>make has lost of implicit rules, including something like %: %.c (meaning if you run "make woo" it will look for woo.c).</div><div><br></div><div>It works for me:<br><br><div>$ make umount2</div><div>cc -D_GNU_SOURCE umount2.c -o umount2</div></div><div>$ make --version</div><div><div>GNU Make 4.1</div><div>Built for x86_64-pc-linux-gnu</div><div>Copyright (C) 1988-2014 Free Software Foundation, Inc.</div><div>License GPLv3+: GNU GPL version 3 or later <<a href="http://gnu.org/licenses/gpl.html">http://gnu.org/licenses/gpl.html</a>></div><div>This is free software: you are free to change and redistribute it.</div><div>There is NO WARRANTY, to the extent permitted by law.</div></div><div><br></div><div>Can you please provide the output of the above two commands?</div><div> <br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div><br></div><div>Thanks,</div><div>Harsha<br></div></div></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Thu, Mar 7, 2019 at 12:30 AM Pavel Emelianov <<a href="mailto:xemul@virtuozzo.com" target="_blank">xemul@virtuozzo.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Thank you, Radostin :) A few words from my side, inline.<br>
<br>
>> 2) Are previous contributions necessary to get selected into CRIU as<br>
>> part of GSoC?<br>
> We ask the students to have a small upstream contribution, but this is<br>
> only as a proof that you know how to clone and build CRIU, as well as<br>
> send patches or create GitHub pull requests.<br>
> <br>
> <a href="https://criu.org/Google_Summer_of_Code" rel="noreferrer" target="_blank">https://criu.org/Google_Summer_of_Code</a><br>
<br>
Yes, previous contributions are not a 'must have', but additional<br>
benefit. If you haven't played with criu previously a quick start<br>
up guide is <a href="https://criu.org/GSoC_Students_Recommendations" rel="noreferrer" target="_blank">https://criu.org/GSoC_Students_Recommendations</a><br>
<br>
>> 3) What are skills apart from C, are necessary for the project?<br>
> Understanding how CRIU works is an important preparation step to work on<br>
> the project. However, we do understand the complexity of the project and<br>
> the limited amount of time that contributors could invest. Thus,<br>
> reviewing the wiki pages in the "Under the hood" category might be useful.<br>
> <br>
> <a href="https://criu.org/Category:Under_the_hood" rel="noreferrer" target="_blank">https://criu.org/Category:Under_the_hood</a><br>
<br>
Absolutely. I'd also add that knowing Linux API is often needed<br>
badly. In particular, if choosing the 'optimizing the pre-dump'<br>
task, one would need to get familiar with Linux mm API including <br>
mmap(7), contents of the /proc/{pid}/maps and pagemap.<br>
<br>
-- Pavel<br>
</blockquote></div>
_______________________________________________<br>
CRIU mailing list<br>
<a href="mailto:CRIU@openvz.org" target="_blank">CRIU@openvz.org</a><br>
<a href="https://lists.openvz.org/mailman/listinfo/criu" rel="noreferrer" target="_blank">https://lists.openvz.org/mailman/listinfo/criu</a><br>
</blockquote></div></div></div></div>