public inbox for
 help / color / mirror / Atom feed
From: Kyle Schwarz <>
Subject: entry point strncpy_s could not be located
Date: Tue, 16 Jul 2013 23:03:00 -0000	[thread overview]
Message-ID: <> (raw)

I'm getting the following error while trying to run FFmpeg with Windows 
XP using the latest version of pthreads-win32: "The procedure entry 
point strncpy_s could not be located in the dynamic link library msvcrt.dll"

Here is a little more information about the bug:
> This is because of a change in the pthreads-w32 CVS. I encountered it after I updated to GCC 4.8.1 but didn't realize anything was wrong until I'd gotten x264 and FFmpeg built. Thankfully, none of the aggregate libraries seem to be affected by pthreads doing this, so it seems relatively benign. The binaries as distributed will work fine on Vista and higher since the version of msvcrt.dll has the secure API functions necessary. If WinXP is a target, pthreads needs a little patching.

That was posted by the user qyot27 at: 

There is also a patch that he submitted that seems to fix the issue:
> # For Windows XP users only:
> sed -i 's/ -DMINGW_HAS_SECURE_API//' GNUmakefile
>      sed -i -e '60i#ifdef MINGW_HAS_SECURE_API' \
>      -e '61i#else\n  strncpy(name, tp->name, len - 1);\n#endif' pthread_getname_np.c
>      sed -i -e '46i#ifdef MINGW_HAS_SECURE_API' \
>      -e '47i#else\n  strncpy(name, tp->name, len - 1);\n#endif' pthread_attr_getname_np.c

I would really apprciate any help on this, currently my FFmpeg builds 
are useless to Windows XP users because I utilize pthread-w32.

Best regards,

             reply	other threads:[~2013-07-16 23:03 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-16 23:03 Kyle Schwarz [this message]
2013-07-17  1:16 ` Ross Johnson

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).