Welcome, Guest. Please login or register. Did you miss your activation email?

Author Topic: The procedure entry point _gxx_personality_v0 could not be locate  (Read 1799 times)

0 Members and 1 Guest are viewing this topic.

cqui

  • Newbie
  • *
  • Posts: 2
    • View Profile
Hello,

I'm trying to get SFML to run but I get the following error :
The procedure entry point_gxx_personality_v0 could not be located in the dynamic link library sfml-graphics-2.dll

I've done some tests, before that I had the error
The procedure entry point _ZSt24__throw_out_of_range_fmtPKcz could not be located in the dynamic link library sfml-graphics-2.dll

I'm using code::block with GCC 5.1 and SFML 2.3.2

Compile goes well, no error or warning,
running the exe file fails with the above error.

I've found one post with same error, the guy could not compile a simple empty program, I can. And they don't indicate the solution.

Another post on stack overflow suggest that the files used at compile time don't match the DLLs found at run time, they all come from the same pack, should'nt they match?

I'm trying to compile the test code found there : http://www.sfml-dev.org/tutorials/2.3/start-cb-fr.php

Thanks for reading me so far, I hope you've got the solution.

eXpl0it3r

  • SFML Team
  • Hero Member
  • *****
  • Posts: 10901
    • View Profile
    • development blog
    • Email
The procedure entry point _gxx_personality_v0 could not be locate
« Reply #1 on: October 22, 2015, 10:04:17 pm »
You use GCC 5.1, SFML doesn't provide a package for that compiler version, they don't match and thus it doesn't work.

At best you build SFML from source with your compiler by following the CMake tutorial.
Official FAQ: https://www.sfml-dev.org/faq.php
Official Discord Server: https://discord.gg/nr4X7Fh
——————————————————————
Dev Blog: https://duerrenberger.dev/blog/

cqui

  • Newbie
  • *
  • Posts: 2
    • View Profile
Re: The procedure entry point _gxx_personality_v0 could not be locate
« Reply #2 on: October 22, 2015, 11:34:43 pm »
Ouch! This was the answer that I dreaded.

Thanks.