Yes, that's why I was afraid for, the patch breaking the build. thank you a lot for the detailed information !
I will try and hope it works On Wed, May 1, 2013 at 4:05 PM, Daniel Liew <[email protected]>wrote: > I'm not sure your patch is applying cleanly there but the bigger > problem is that the configure step can't find the STP header file > hence nothing can be built. > > Take a look at config.log (generated when running configure in the > KLEE directory) for hints about what went wrong but it looks like > configure had trouble with your STP installation (STP is the > constraint solver KLEE uses and it is separate from KLEE). > > Given that you've got this far it is probably better to try to do the > rest by hand instead of rerunning the installation script. > > 1. Check STP built and installed correctly (if you run make again, > make sure you use the arguments used in the script - with the > variables expanded of course) > 2. Reperform the configure command for KLEE > 3. If the above succeeds you should be able to build KLEE. > > I glanced at the patch for KLEE and it doesn't look like it changes > any part of the build system so you could actually build KLEE first > apply the patch and then build again to be sure that the patch did not > break the build. > > > On 1 May 2013 14:46, Alexandru Ionut Diaconescu > <[email protected]> wrote: > > > > I started to apply the installation script from the beginning. And KLEE > is > > not installing anymore, having : > > > > patching file lib/Module/KModule.cpp > > patching file tools/klee/main.cpp > > patch unexpectedly ends in middle of line > > Hunk #3 succeeded at 1314 with fuzz 1. > > checking build system type... i686-pc-linux-gnu > > checking host system type... i686-pc-linux-gnu > > ... > > configure: error: Unable to use stp/c_interface.h header > > Makefile:15: Makefile.config: No such file or directory > > Makefile.common:3: Makefile.config: No such file or directory > > Makefile.common:6: /Makefile.config: No such file or directory > > Makefile.common:21: /Makefile.rules: No such file or directory > > make: *** No rule to make target `/Makefile.rules'. Stop. > > /home/pc/Desktop/llvm/NEWKLEE > > run . ./setenv.sh for setting up the environment > > Done. Try: > > cd klee/examples/taint > > make > > > > In the script from http://cs.famaf.unc.edu.ar/~rcorin/kleecrypto/ , all > the > > steps from installing KLEE seem to be respected... > > > > On Wed, May 1, 2013 at 2:49 PM, Alexandru Ionut Diaconescu > > <[email protected]> wrote: > >> > >> > >> > >> ---------- Forwarded message ---------- > >> From: Alexandru Ionut Diaconescu <[email protected]> > >> Date: Wed, May 1, 2013 at 2:48 PM > >> Subject: Re: [klee-dev] failed external call > >> To: Daniel Liew <[email protected]> > >> > >> > >> Yes, I saw in the script the patch usage and I didn't received any error > >> during running their script. And still, I have the original KLEE files, > >> their patch being not applied.. > >> > >> > >> On Wed, May 1, 2013 at 2:46 PM, Daniel Liew <[email protected] > > > >> wrote: > >>> > >>> You can apply the patch as follows > >>> > >>> $ cd klee_root # this is where the include/, lib/ and other folders are > >>> $ patch -p1 < the_patch_to_apply.patch > >>> > >>> If you're using git you can also use > >>> > >>> $ git apply the_patch_to_apply.patch > >>> > >>> I've not tried actually applying the patch so I can't tell you if it > >>> will apply cleanly. > >>> > >>> > >>> On 1 May 2013 13:42, Alexandru Ionut Diaconescu > >>> <[email protected]> wrote: > >>> > I was trying again to use wget and patch but it seems it doesn't > work. > >>> > I > >>> > will look for the warnings received during installation. > >>> > > >>> > Sorry for the beginner questions, I will try to solve it. > >> > >> > >> > >> > >> -- > >> Best regards, > >> Alexandru Ionut Diaconescu > >> > >> > >> > >> -- > >> Best regards, > >> Alexandru Ionut Diaconescu > > > > > > > > > > -- > > Best regards, > > Alexandru Ionut Diaconescu > -- Best regards, Alexandru Ionut Diaconescu
_______________________________________________ klee-dev mailing list [email protected] https://mailman.ic.ac.uk/mailman/listinfo/klee-dev
