<div dir="ltr"><div><div><div>Dear Amitoj,<br><br></div><div>We released a new version of Klever software verification framework, so some deployment and verification steps changed a bit. In case you would like to try it out there is a guide to run verification using the new Klever version.<br></div><div><br>1. Choose your favorite Ubuntu/Debian image. The instruction below is prepared for Ubuntu 18 but it not strictly required.<br></div><div>2. Download and create a new desktop installation or virtual machine with the system. Don't forget about our hardware <a href="https://klever.readthedocs.io/en/latest/deploy.html#hardware-requirements">requirements</a>!<br></div><div>3. Download our software verification framework:</div><div>sudo apt-get install git<br></div><div>git clone <a href="https://github.com/ldv-klever/klever.git">https://github.com/ldv-klever/klever.git</a></div><div><br></div><div>4. Then follow <a href="https://klever.readthedocs.io/en/latest/deploy_local.html">deployment steps</a>
for the local deployment. In particular modify
klever-minimal.json.sample and save it as klever.json in
$KLEVER_SRC/deployment/conf/ directory. Also set environment variables
to specify $KLEVER_SRC directory with Klever source files and target
installation directory $KLEVER_DEPLOY_DIR. Then install Klever with the
command:<br>sudo $KLEVER_SRC/deploys/bin/deploy-local --deployment-directory $KLEVER_DEPLOY_DIR install production<br></div><div><br></div><div>5. After Klever installation you can build the kernel and create build base. <br></div><div><br></div><div>Download the kernel: <br></div><div><div>wget <a href="https://cdn.kernel.org/pub/linux/kernel/v3.x/linux-3.14.79.tar.gz">https://cdn.kernel.org/pub/linux/kernel/v3.x/linux-3.14.79.tar.gz</a><br>tar -xf linux-3.14.79.tar.gz<br><br></div><div>Install a suitable compiler:<br>sudo update-alternatives --install /usr/bin/gcc gcc /usr/bin/gcc-4.8 10<br>sudo update-alternatives --config gcc</div><div>And choose 4.8 compiler there</div><div><br></div><div>Prepare your PATH environment variable:<br>export PATH=$KLEVER_DEPLOY_DIR/klever-addons/CIF/bin/:$PATH</div><div><br></div><div>Then run the following commands. It will take a lot of time<br>make allmodconfig<br>clade-intercept make -j8 modules_prepare</div><div>clade-intercept -a make -j8 all</div><div>clade-all -p linux_kernel ./cmds.txt</div><div>echo "[\"$(readlink -f .)\"]" > ./clade/Storage/working source trees.json<br><br></div><div>6.
Move this build base to another place. This is an optional step but
if you are going to build more bases in this directory then it is better
to do it. Note, then you need a new base for each new configuration or
kernel version. <br></div><div>mv clade $NEW_PLACE/linux-3.14.79</div><div><br></div><div>7.
Modify your deployment klever.json file in $KLEVER_DEPLOY_DIR and add
there a new section at the end of the file in the root JSON object:<br>"Klever Build Bases": ["$NEW_PLACE/linux-3.14.79"]</div><div><br></div><div>Instead of $NEW_PLACE set an absolute path to the directory with your build base.<br><br></div><div>8 Update the Klever installation:<br>sudo $KLEVER_SRC/deploys/bin/deploy-local --deployment-directory $KLEVER_DEPLOY_DIR update production<br><br></div><div>9. Now you can run verification.<br></div><div><div>Open localhost:8998 in the web browser.</div><div>Input username: manager, password: manager.</div><div>Click "Linux 3.14".</div><div>Click Job->Edit or ->Copy and edit job.json and other files depending on your needs.</div><div>In the job.json set "build base": "linux-3.14.79" or an another name if you named your build base differently.<br></div><div>Before running any large target such as all modules first try to verify modules given with the example.<br></div><div>10. Click Decision->Start.</div><div>11. Click "Start" or "Start with default values".</div><div>13. Wait for verification results. It can take very much time especially if your hardware isn't powerful enough. <br></div><div><br>If
you will meet some issues, please, report them to us. We will try to
solve or workaround them together. Note also, that we renamed some
files, so there are some differences from the Klever-1.1 version in job
files.</div></div></div><br></div>Best regards,<br></div>Ilia Zakharov<br><div><div><br><br><div class="gmail_quote"><div dir="ltr">пт, 26 окт. 2018 г. в 23:57, Alexey Khoroshilov <<a href="mailto:khoroshilov@ispras.ru">khoroshilov@ispras.ru</a>>:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Dear Amitoj,<br>
<br>
On 24.10.2018 4:03, Amitoj Kaur Chawla wrote:<br>
> Hi Alexey,<br>
><br>
> I followed the klever documentation and I am a little confused about<br>
> the Local Deployment command<br>
> in particular:<br>
> $ sudo $KLEVER_SRC/deploys/bin/deploy-local --deployment-directory<br>
> $KLEVER_DEPLOY_DIR install production<br>
> What exactly is the $KLEVER_DEPLOY_DIR deployment directory here?<br>
KLEVER_DEPLOY_DIR is a directory where KLEVER should be installed.<br>
<br>
> Also, if I understand correctly, klever will run on the linux tarball<br>
> versions I'm downloading for the Target Software?<br>
Yes, that is correct.<br>
After installation you should open localhost:8998 in your web browser,<br>
login as Manager (login: manager, password: manager) and run<br>
verification of one of available programs.<br>
<br>
<br>
We have added you to the mailing list.<br>
I hope it will work for you now.<br>
<br>
Best regards,<br>
Alexey<br>
<br>
<br>
_______________________________________________<br>
ldv-project mailing list<br>
<a href="mailto:ldv-project@linuxtesting.org" target="_blank">ldv-project@linuxtesting.org</a><br>
<a href="http://linuxtesting.org/cgi-bin/mailman/listinfo/ldv-project" rel="noreferrer" target="_blank">http://linuxtesting.org/cgi-bin/mailman/listinfo/ldv-project</a><br>
</blockquote></div></div></div></div>