[ldv-project] LDV project Help.

Wed Nov 7 11:24:43 MSK 2018

Dear Amitoj,

ср, 7 нояб. 2018 г. в 2:36, Amitoj Kaur Chawla <amitoj1606 at gmail.com>:

> On Tue, Nov 6, 2018 at 7:45 AM Ilja Zakharov <ilja.zakharov at ispras.ru>
> wrote:
> >
> > Dear Amitoj,
> >
> > 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.
> >
> > 1. Choose your favorite Ubuntu/Debian image. The instruction below is
> prepared for Ubuntu 18 but it not strictly required.
> > 2. Download and create a new desktop installation or virtual machine
> with the system.  Don't forget about our hardware requirements!
> > 3. Download our software verification framework:
> > sudo apt-get install git
> > git clone https://github.com/ldv-klever/klever.git
> >
> > 4. Then follow deployment steps 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:
> > sudo $KLEVER_SRC/deploys/bin/deploy-local --deployment-directory
> $KLEVER_DEPLOY_DIR install production
> >
> > 5. After Klever installation you can build the kernel and create build
> base.
> >
> > Download the kernel:
> > wget https://cdn.kernel.org/pub/linux/kernel/v3.x/linux-3.14.79.tar.gz
> > tar -xf linux-3.14.79.tar.gz
> >
> > Install a suitable compiler:
> > sudo update-alternatives --install /usr/bin/gcc gcc /usr/bin/gcc-4.8 10
> > sudo update-alternatives --config gcc
> > And choose 4.8 compiler there
> >
> > Prepare your PATH environment variable:
> > export PATH=$KLEVER_DEPLOY_DIR/klever-addons/CIF/bin/:$PATH
> >
> > Then run the following commands. It will take a lot of time
> > make allmodconfig
> > clade-intercept make -j8 modules_prepare
> > clade-intercept -a make -j8 all
> > clade-all -p linux_kernel ./cmds.txt
> > echo "[\"$(readlink -f .)\"]" > ./clade/Storage/working source trees.json
> >
>
> Hi Ilja,
>
> I'm a little confused in these steps. I believe I'll be running the
> make command in the linux repo I downloaded earlier, but confused on
> the clade-intercept steps.
>

Year, this is a bit imprecise, you need to run clade-intercept commands
inside the Linux source directory. Clade intercepts the build commands that
Make performs building your kernel, so Clade runs what exactly you give it.
I used in the example make commands to build all loadable kernel modules
for instance.

> It's mentioned in the documentation that clade should be used to
> obtain build bases, I cloned the clade repo from the link but unsure
> of how to go on. Could you help me out or point me to some
> documentation which helps me do so?
>

In case you are interested in Clade documentation, it is available
from the GitHub
Clade page <https://github.com/17451k/clade>. However, Klever at
installation installs all necessary packages including Clade, so you do not
need to install it manually or clone its repo if you already installed
Klever 2.0 (or current master branch).

>
> Amitoj
> > 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.
> > mv clade $NEW_PLACE/linux-3.14.79
> >
> > 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:
> > "Klever Build Bases": ["$NEW_PLACE/linux-3.14.79"]
> >
> > Instead of $NEW_PLACE set an absolute path to the directory with your
> build base.
> >
> > 8 Update the Klever installation:
> > sudo $KLEVER_SRC/deploys/bin/deploy-local --deployment-directory
> $KLEVER_DEPLOY_DIR update production
> >
> > 9. Now you can run verification.
> > Open localhost:8998 in the web browser.
> > Input username: manager, password: manager.
> > Click "Linux 3.14".
> > Click Job->Edit or ->Copy and edit job.json and other files depending on
> your needs.
> > In the job.json set "build base": "linux-3.14.79" or an another name if
> you named your build base differently.
> > Before running any large target such as all modules first try to verify
> modules given with the example.
> > 10. Click Decision->Start.
> > 11. Click "Start" or "Start with default values".
> > 13. Wait for verification results. It can take very much time especially
> if your hardware isn't powerful enough.
> >
> > 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.
> >
> > Best regards,
> > Ilia Zakharov
> >
> >
> > пт, 26 окт. 2018 г. в 23:57, Alexey Khoroshilov <khoroshilov at ispras.ru>:
> >>
> >> Dear Amitoj,
> >>
> >> On 24.10.2018 4:03, Amitoj Kaur Chawla wrote:
> >> > Hi Alexey,
> >> >
> >> > I followed the klever documentation and I am a little confused about
> >> > the Local Deployment command
> >> > in particular:
> >> > $ sudo $KLEVER_SRC/deploys/bin/deploy-local --deployment-directory
> >> > $KLEVER_DEPLOY_DIR install production
> >> > What exactly is the $KLEVER_DEPLOY_DIR deployment directory here?
> >> KLEVER_DEPLOY_DIR is a directory where KLEVER should be installed.
> >>
> >> > Also, if I understand correctly, klever will run on the linux tarball
> >> > versions I'm downloading for the Target Software?
> >> Yes, that is correct.
> >> After installation you should open localhost:8998 in your web browser,
> >> login as Manager (login: manager, password: manager) and run
> >> verification of one of available programs.
> >>
> >>
> >> We have added you to the mailing list.
> >> I hope it will work for you now.
> >>
> >> Best regards,
> >> Alexey
> >>
> >>
> >> _______________________________________________
> >> ldv-project mailing list
> >> ldv-project at linuxtesting.org
> >> http://linuxtesting.org/cgi-bin/mailman/listinfo/ldv-project
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://linuxtesting.org/pipermail/ldv-project/attachments/20181107/cf9bc20e/attachment.html>