Date: Mon, 07 May 2012 14:16:38 -0700 From: "Ronald F. Guilmette" <rfg@tristatelogic.com> To: Konstantin Belousov <kostikbel@gmail.com> Cc: pav@freebsd.org, freebsd-gnome@freebsd.org, freebsd-ports@freebsd.org, Shawn Webb <lattera@gmail.com> Subject: Re: Need a little help with a dynamic linking problem Message-ID: <28678.1336425398@tristatelogic.com> In-Reply-To: <20120426080649.GO2358@deviant.kiev.zoral.com.ua>
next in thread | previous in thread | raw e-mail | index | archive | help
Sorry for my late reply... I was tied up on other projects. A few days ago, in a galaxy not far away... In message <20120426080649.GO2358@deviant.kiev.zoral.com.ua>, Konstantin Belousov <kostikbel@gmail.com> wrote: >You need to pass --export-dynamic to the linker when linking binary that >is supposed to export its own symbols. Yes! Thank you Konstantin. Using that linker option... or more accurately it's gcc equivalent (-rdynamic) did indeed clear up the problem I was having with gthumb's (dynamic plug-in?) extension modules not seeing the symbols in the main exectuable. I'm not at all sure why this option wasn't already integrated into the relevant Makefiles (for gthumb). I will be looking into that further. Regards, rfg P.S. If it were me, I think I would have implemented that linker option the other way around, i.e. made the default that symbols in the main executable _are_ externally visible by default, and then I would have provided an option to make them non-visible, when and if that is/was ever useful. Sigh. Oh well. I wasn't there at the time. It's just water under the bridge now.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?28678.1336425398>