Date: Tue, 12 Jul 2005 00:57:41 +0400 From: Vladimir Grebenschikov <vova@fbsd.ru> To: Dan Nelson <dnelson@allantgroup.com> Cc: freebsd-emulation@freebsd.org Subject: Re: Linking linux libs Message-ID: <1121115461.1043.3.camel@localhost> In-Reply-To: <20050711183241.GH5116@dan.emsphone.com> References: <000701c58643$71f3a190$6401a8c0@HomePC> <20050711183241.GH5116@dan.emsphone.com>
next in thread | previous in thread | raw e-mail | index | archive | help
=F7 =D0=CE, 11/07/2005 =D7 13:32 -0500, Dan Nelson =D0=C9=DB=C5=D4: > In the last episode (Jul 11), Jim Bodkikns (Dakotacom) said: > > A linux emulation question. > >=20 > > I suspect I know the answer to this, but what about linking to > > vendor supplied linux libs? (A vendor product that is provided in the > > form of libraries that are linked into your apps). >=20 > As long as you compile and link using linux gcc and ld to generate a > Linux executable, it'll work. Don't try and link a Linux library into > a FreeBSD executable, though, unless the ABI is very simple. For > example, a standalone crypto module that takes a buffer and a key would > probably work; anything that tries to do any stdio or call libc > functions that pass structures won't. I have know examples of more complex magic on linking big database linux static library into FreeBSD applications, but it was like black magic with lot of libc compatibility hacks. --=20 Vladimir B. Grebenschikov vova@fbsd.ru
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1121115461.1043.3.camel>