securify2 icon indicating copy to clipboard operation
securify2 copied to clipboard

libfunctors.so not compiled error

Open Enigmatic331 opened this issue 4 years ago • 6 comments

Hope all is well!

Let me first caveat that I might be missing out a step or two and being incredibly dumb here. :)

Did a repo clone, followed by the docker build process, and currently testing my set up image through bash. Running the command securify --from-blockchain returned a libfunctors.so not compiled error:

image

Is there something I might be missing? Thanks in advance.

Enigmatic331 avatar Mar 06 '20 10:03 Enigmatic331

Hello, Unfortunately, I wasn't able to reproduce the error. What result do you get when you run: docker build -t securify . then docker run -it securify -b <address of contract> and then provide the API key manually? I tested your contract and it revealed a bug in securify which I fixed and pushed to the develop branch. Your feedback on that would be useful as well.

YannisSach avatar Mar 07 '20 12:03 YannisSach

Thanks a ton @YannisSach! I did gotten a little further than where I was 3 days back.

Apparently while running docker build -t securify ., I missed a few errors while the compile_functos.sh ran (maybe it's a directory/path thing): image

Pulling out the contents of the shell script and running the g++ commands directly seems to work so I am using that as an interim measure - Until I figure out what went wrong running the shell script. image

Though currently I am stuck on step 17 (I think it's doing some souffle setup, or I could be dumb): image

Trying to figure this bit out, and if I could, the remainder ENV and ENTRYPOINT commands should work as-is and I can start experimenting with SecurifyV2. :)

And yes, looking forward to be providing feedback from there.

Enigmatic331 avatar Mar 09 '20 03:03 Enigmatic331

image

Kinda strange - I think I will dig around Souffle for a bit to figure this out.

Enigmatic331 avatar Mar 09 '20 04:03 Enigmatic331

It seems something went wrong with the linking. Could you resolve it?

b-scholz avatar Mar 09 '20 10:03 b-scholz

PS: Sorry - Currently caught up with something else - But I will round back to this and try out a couple of things, then report back.

Enigmatic331 avatar Mar 13 '20 04:03 Enigmatic331

any news on this issue?

opetznick avatar Oct 11 '20 19:10 opetznick