public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pavel at zhukoff dot net" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug ada/65477] New: gnat is built with nodlopen Date: Thu, 19 Mar 2015 22:25:00 -0000 [thread overview] Message-ID: <bug-65477-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65477 Bug ID: 65477 Summary: gnat is built with nodlopen Product: gcc Version: 4.9.3 Status: UNCONFIRMED Severity: trivial Priority: P3 Component: ada Assignee: unassigned at gcc dot gnu.org Reporter: pavel at zhukoff dot net Created attachment 35068 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=35068&action=edit test program It's not possible to write shared plugins in ada because libgnat (and only libgnat from gcc) is built with nodlopen option. Example: Error: unable to load plugin "~/.weechat/plugins/liblibaweeplug.so": libgnat-4.9.so: shared object cannot be dlopen()ed How to reproduce: Try to dlopen libgnat.so. dlopen returns NULL works fine for libc/libm/etc
next reply other threads:[~2015-03-19 20:54 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-03-19 22:25 pavel at zhukoff dot net [this message] 2015-03-20 8:43 ` [Bug ada/65477] " pavel at zhukoff dot net 2015-03-20 9:23 ` ebotcazou 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-65477-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).