public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug libmudflap/28188]  New: dynamic linkage error for shared libraries compiled and linked against libmudflapth
@ 2006-06-28 15:11 melfar at gmail dot com
  2008-03-16 22:50 ` [Bug libmudflap/28188] " starlight at binnacle dot cx
  0 siblings, 1 reply; 3+ messages in thread
From: melfar at gmail dot com @ 2006-06-28 15:11 UTC (permalink / raw)
  To: gcc-bugs

I'm building a shared library with libpthread and libmudflapth support.
Flags used to compile are: -fstack-protector -fmudflapth
Flags used to link are: -lmudflapth

When trying to dlopen the shared lib at runtime I get:
symbol lookup error: /home/melfar/gcc4/lib/libmudflapth.so.0: undefined symbol:
_start

and the lib fails to open.
Is multithreaded mudflap currently supported for shared libraries?


-- 
           Summary: dynamic linkage error for shared libraries compiled and
                    linked against libmudflapth
           Product: gcc
           Version: 4.1.1
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: libmudflap
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: melfar at gmail dot com
  GCC host triplet: i686-linux-gnu


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=28188


^ permalink raw reply	[flat|nested] 3+ messages in thread

* [Bug libmudflap/28188] dynamic linkage error for shared libraries compiled and linked against libmudflapth
  2006-06-28 15:11 [Bug libmudflap/28188] New: dynamic linkage error for shared libraries compiled and linked against libmudflapth melfar at gmail dot com
@ 2008-03-16 22:50 ` starlight at binnacle dot cx
  0 siblings, 0 replies; 3+ messages in thread
From: starlight at binnacle dot cx @ 2008-03-16 22:50 UTC (permalink / raw)
  To: gcc-bugs



------- Comment #1 from starlight at binnacle dot cx  2008-03-16 22:49 -------
Hit this same issue.  The problem is likely that the -fvisibility=hidden
option is also on the compile line.  Removing it makes the problem go
away, at least for single-threaded mudflap.

Produced with gcc 4.2.3, x86_64 under CentOS 4.6.


-- 

starlight at binnacle dot cx changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |starlight at binnacle dot cx


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=28188


^ permalink raw reply	[flat|nested] 3+ messages in thread

* [Bug libmudflap/28188] dynamic linkage error for shared libraries compiled and linked against libmudflapth
       [not found] <bug-28188-4@http.gcc.gnu.org/bugzilla/>
@ 2013-11-10  5:43 ` pinskia at gcc dot gnu.org
  0 siblings, 0 replies; 3+ messages in thread
From: pinskia at gcc dot gnu.org @ 2013-11-10  5:43 UTC (permalink / raw)
  To: gcc-bugs

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=28188

Andrew Pinski <pinskia at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |RESOLVED
         Resolution|---                         |WONTFIX
   Target Milestone|---                         |4.9.0

--- Comment #2 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
fmudflap support has been removed.


^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2013-11-10  5:43 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2006-06-28 15:11 [Bug libmudflap/28188] New: dynamic linkage error for shared libraries compiled and linked against libmudflapth melfar at gmail dot com
2008-03-16 22:50 ` [Bug libmudflap/28188] " starlight at binnacle dot cx
     [not found] <bug-28188-4@http.gcc.gnu.org/bugzilla/>
2013-11-10  5:43 ` pinskia at gcc dot gnu.org

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).