public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "ktietz at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/48881] Dynamic link to libstdc++-6.dll / libgcc_s_sjlj-1.dll produces broken binaries Date: Mon, 19 Dec 2011 10:27:00 -0000 [thread overview] Message-ID: <bug-48881-4-PJCHI30yVR@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-48881-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=48881 --- Comment #5 from Kai Tietz <ktietz at gcc dot gnu.org> 2011-12-19 10:23:51 UTC --- Well, I wouldn't say that this was rude. The issue here is most likely, that the runtime DLLs by gcc aren't in search-path when you are trying to execute your built application. But this isn't a subject of gcc itself. I see that you have this issue, but user-support questions on how to setup environment for built applications, or what is necessary to provide along-side built-application so that they run, is more something related to gcc's user ML, or even better to ask directly for it on mingw.org's or mingw-w64's public user-mailing lists. On those later lists you can be sure that you will find a solution for your issue.
next prev parent reply other threads:[~2011-12-19 10:24 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-05-05 9:53 [Bug libstdc++/48881] New: " astrand at cendio dot se 2011-05-25 10:15 ` [Bug libstdc++/48881] " paolo.carlini at oracle dot com 2011-12-17 16:15 ` ktietz at gcc dot gnu.org 2011-12-17 16:35 ` paolo.carlini at oracle dot com 2011-12-19 10:14 ` ossman at cendio dot se 2011-12-19 10:27 ` ktietz at gcc dot gnu.org [this message] 2011-12-19 12:25 ` astrand at cendio dot se 2011-12-19 12:26 ` astrand at cendio dot se 2011-12-19 12:34 ` astrand at cendio dot se 2012-12-21 16:26 ` ktietz at gcc dot gnu.org
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: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=bug-48881-4-PJCHI30yVR@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe 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).