public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "arsoftware25 at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c/102193] New: DLL linking with a external referenced DLL Date: Fri, 03 Sep 2021 16:43:13 +0000 [thread overview] Message-ID: <bug-102193-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102193 Bug ID: 102193 Summary: DLL linking with a external referenced DLL Product: gcc Version: unknown Status: UNCONFIRMED Severity: normal Priority: P3 Component: c Assignee: unassigned at gcc dot gnu.org Reporter: arsoftware25 at gmail dot com Target Milestone: --- Hi Corina just figured out that a .def file in a dll may export function from a dll that is referenced in the compilation stage like this: gcc file.c external.dll def.def -o out.dll if in the def.def it has a function that is in the file.c and also available in external.dll it may generate an invalid out.dll I don't know but this looks like a problem in gcc that need to be fixed, spend one hour modifying my function in file.c and it was linking with external.dll then I commented the function inside file.c and saw the compilation stage finished without a link error if it is a GCC feature then a warning about expernal DLL linkage could help a lot when the function exported is inside an external DLL hope to have explained it in an easy way Ricardo
next reply other threads:[~2021-09-03 16:43 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-09-03 16:43 arsoftware25 at gmail dot com [this message] 2021-09-03 19:02 ` [Bug driver/102193] " pinskia at gcc dot gnu.org 2021-09-03 19:52 ` arsoftware25 at gmail dot com
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-102193-4@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).