Re: Undefined SSL symbols when linking against libgnomevfs

[James Andrewartha <jamesa daa com au>]

[ Actually cc:ing {desktop,tools}-discuss opensolaris org ]

>  The biggest blocker at the moment is
>> libgnomevfs-2.so being linked against libssl, causing undefined symbol
> errors when linking binaries linked against libgnomevfs-2.so.
> [...]
>> This looks like the GNU ld vs Sun ld linker problem mentioned on
> http://wikis.sun.com/display/SolarisDeveloper/Issues+when+porting+OpenSource+projects+to+Solaris
> and http://bugzilla.gnome.org/show_bug.cgi?id=532093 because libssl.so
> is in
>> /usr/sfw/lib and no -L -R options are passed. I thought the way to deal
> with
>> this would be to edit gnome-vfs-2.0.pc and add -L/usr/sfw/lib
>> -R/usr/sfw/lib
>> to Libs, but I checked the gnome-vfs-2.0.pc file from
> SUNWgnome-vfs-devel and it doesn't have that in Libs, so I'm not sure
> what the correct solution
>> is, and how compiling against /usr/lib/libgnomevfs-2.so works.

I poked around the libraries with objdump, and found this difference:
jhbuilt libgnomevfs-2.so:
00000000         *UND*  00000000              SSL_new
Sun built libgnomevfs-2.so:
00000000       F *UND*  00000000              SSL_new

The objdump manpage says F indicates the symbol is the name of a function,
and a space indicates it's "just a normal symbol". So I guess it's some
linker option that's causing this. The Sun build [1] adds "-Wl,-zignore
-Wl,-zcombreloc -Wl,-Bdirect" to LDFLAGS, is one of these what sets the
function flag?

> unfortunately I don't have any experience whatsoever compiling stuff for
> this environment, so I cannot point you to the right solution. I would
> send this question to a mailing list more subscribers, since that way you
> have a better chance to find someone with experience on this specific
> field. I think gnome-love could be a good place for that.

Ok, cc:ed gnome-love and opensolaris tools-discuss.

[1] http://src.opensolaris.org/source/xref/jds/spec-files/trunk/include/Solaris.inc#59

-- 
James Andrewartha