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

Author Topic: Procedure entry point in xxxxxx not located in the libstdc++-6.dll  (Read 2849 times)

0 Members and 1 Guest are viewing this topic.

jalf86

  • Newbie
  • *
  • Posts: 11
    • View Profile
    • Email
Hi,

I've just installed SFML and went through the"Getting Started SFML and Code::Blocks (MinGW)" tutorial.  I compiled the tutorial code provide and got 0 errors, 0 warning, 0 etc ...

When I run it, I get the following error message:

The procedure entry point _ZNKSt7 __cxx1112basic_stringIcSt11char_traitsIcEsaIcEE3endEv cound not be located in the dynamic link library libstdc++-6.dll.

I've set Mingw compiler to point to the forked Mingw64.

Can anyone help?
« Last Edit: April 23, 2017, 12:36:44 am by jalf86 »

eXpl0it3r

  • SFML Team
  • Hero Member
  • *****
  • Posts: 11030
    • View Profile
    • development blog
    • Email
Re: Procedure entry point in xxxxxx not located in the libstdc++-6.dll
« Reply #1 on: April 23, 2017, 12:35:29 am »
It's a relatively common problem, did you try to search for an answer first?

You're using the wrong runtime dlls. You need to copy the ones that are shipped with the compiler that you built your application with.
Official FAQ: https://www.sfml-dev.org/faq.php
Official Discord Server: https://discord.gg/nr4X7Fh
——————————————————————
Dev Blog: https://duerrenberger.dev/blog/

jalf86

  • Newbie
  • *
  • Posts: 11
    • View Profile
    • Email
Re: Procedure entry point in xxxxxx not located in the libstdc++-6.dll
« Reply #2 on: April 23, 2017, 12:41:48 am »
Sorry,

I clicked the "Build" button vs. the "Re-Build" button after pointing to the correct version of Mingw. Now I'm getting compiler errors.

I'm guessing I still have incorrect dll's like you said. I'll keep looking.

eXpl0it3r

  • SFML Team
  • Hero Member
  • *****
  • Posts: 11030
    • View Profile
    • development blog
    • Email
Re: Procedure entry point in xxxxxx not located in the libstdc++-6.dll
« Reply #3 on: April 23, 2017, 01:00:40 am »
Compiler or linker errors?

If you use a MinGW version that wasn't used for building the pre-packaged SFML libs (as linked on the download page), you'll have to rebuild SFML yourself with you MinGW version.
Official FAQ: https://www.sfml-dev.org/faq.php
Official Discord Server: https://discord.gg/nr4X7Fh
——————————————————————
Dev Blog: https://duerrenberger.dev/blog/

jalf86

  • Newbie
  • *
  • Posts: 11
    • View Profile
    • Email
Re: Procedure entry point in xxxxxx not located in the libstdc++-6.dll
« Reply #4 on: April 23, 2017, 03:40:57 am »
Thanks.  After I did a rebuild, I got ... I'll try your suggestion and and bulid SFML with the MinGW64. Going to let my brain rest first. Went to the MinGW64 forum and there was a jumbled mess on what to do about migrating from MinGW32 to MinGW64.

jalf86

  • Newbie
  • *
  • Posts: 11
    • View Profile
    • Email
Re: Procedure entry point in xxxxxx not located in the libstdc++-6.dll
« Reply #5 on: April 24, 2017, 07:59:25 am »
I deleted  and then re-installed Code::Blocks and the fork, Mingw32-64.  Then deleted the Mingw that came with Code::Blocks.  Using CMake; built the Release and Debug Versions of SFML (32-bit, SJLJ).  Tested it. Worked.

Less than a minute after i ran the test program, I figured out what I did wrong.

What I did wrong was I downloaded SFML (Dwarf), but my Code::Blocks compiler was (SJLJ).  Codeblocks uses the TDM version of MinGW.

For those of you having installation problems, I found out there are two different compilers for the gcc family that aren't labeled as such. Dwarf and SJLJ.  The difference between them is the way each one handles exceptions.  You can't mix (Dwarf and SJLJ) compilers, executables, object code, and DLL's .  They all have to be the same type; one or the other. 

One weekend. Down the drain.

jalf86

  • Newbie
  • *
  • Posts: 11
    • View Profile
    • Email
Re: Procedure entry point in xxxxxx not located in the libstdc++-6.dll
« Reply #6 on: May 01, 2017, 10:18:49 pm »
I know this is very late.

Thank you, so very much, eXpl0it3r for replying.  I probably would have spent another week trying different configurations and not getting anywhere.