From owner-freebsd-questions@FreeBSD.ORG Sat Dec 20 19:32:35 2008 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id F306E1065673 for ; Sat, 20 Dec 2008 19:32:35 +0000 (UTC) (envelope-from eagletree@hughes.net) Received: from smtprelay.b.hostedemail.com (smtprelay0159.b.hostedemail.com [64.98.42.159]) by mx1.freebsd.org (Postfix) with ESMTP id AA0BB8FC19 for ; Sat, 20 Dec 2008 19:32:35 +0000 (UTC) (envelope-from eagletree@hughes.net) Received: from filter.hostedemail.com (b-bigip1 [10.5.19.254]) by smtprelay05.b.hostedemail.com (Postfix) with SMTP id 3DC9A4A0997D; Sat, 20 Dec 2008 19:32:34 +0000 (UTC) X-SpamScore: 1 X-Spam-Summary: 2, 0, 0, 9e844db1feda4f9d, 944facfeb153b4f0, eagletree@hughes.net, freebsd-questions@freebsd.org:bsam@ipt.ru, RULES_HIT:355:379:541:564:599:601:945:946:966:967:973:980:988:989:1260:1261:1277:1311:1313:1314:1345:1359:1437:1515:1516:1518:1535:1544:1593:1594:1605:1711:1730:1747:1766:1792:2194:2196:2198:2199:2200:2201:2379:2393:2525:2553:2559:2563:2682:2685:2689:2693:2857:2859:2902:2933:2937:2939:2942:2945:2947:2951:2954:3022:3027:3167:3636:3865:3866:3867:3868:3869:3870:3871:3872:3873:3874:3876:3877:3934:3936:3938:3941:3944:3947:3950:3953:3956:3959:4250:4321:4362:4385:4605:4860:5007:6114:6117:6119:7652:7679:7903:8501:8568:9010:9025:9388, 0, RBL:none, CacheIP:none, Bayesian:0.5, 0.5, 0.5, Netcheck:none, DomainCache:0, MSF:not bulk, SPF:, MSBL:none, DNSBL:none Received: from [192.168.0.3] (dpc6744118153.direcpc.com [67.44.118.153]) (Authenticated sender: eagletree@hughes.net) by omf04.b.hostedemail.com (Postfix) with ESMTP; Sat, 20 Dec 2008 19:32:24 +0000 (UTC) In-Reply-To: <03393450@ipt.ru> References: <34058EDE-BC14-4DCC-AF3C-100F77DEE486@hughes.net> <03393450@ipt.ru> Mime-Version: 1.0 (Apple Message framework v753) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: <0259344B-703E-466E-9925-7B065B54AD7B@hughes.net> Content-Transfer-Encoding: 7bit From: Chris Date: Sat, 20 Dec 2008 11:32:16 -0800 To: Boris Samorodov X-Mailer: Apple Mail (2.753) X-session-marker: 6561676C6574726565406875676865732E6E6574 Cc: FreeBSD-Questions Questions Subject: Re: Linking libraries for compat_linux X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 20 Dec 2008 19:32:36 -0000 On Dec 20, 2008, at 6:05 AM, Boris Samorodov wrote: > On Fri, 19 Dec 2008 09:46:03 -0800 Chris wrote: > > This question is may be better unswered at emulation@ ML. > Oops, I didn't ever notice that list as I've never needed Linux before. I hate to trouble development lists with an operational issue but this one is starting to look like an incompatibility that is beyond me. The Linux and FreeBSD versions of gamin both fail on inotify_init. Not having the source to the program I'm trying to run makes it very difficult to fix even though the functionality is there (perhaps even superior) on FreeBSD. I ended up using the linux libfam.so.0 from the gamin distribution for Fedora 9. Using it's server fails instantly, using the freebsd port version, the server doesn't fail until the Linux client library attempts to connect. Then it too gets "inotify_init not implemented". The Fam list appears to be defunct and I've not yet tried the direct mail contact to the gamin development page. I'm assuming the answer would be that you use native FreeBSD libfam.so on FreeBSD and the linux version on Linux. I've no way to tell the Intuit daemon to do that because of the ABI error and I presume there is an underlying reason why a native library can't be used by a linux binary. I will try the other list if no one has run into a similar problem with other Linux apps. I may be kicking a dead horse but it seems others have talked about using FreeBSD in this manner and it makes it an interesting challenge. The time I'm investing in this is probably not any more time that it would take to configure and secure an openSUSE or Fedora system (having never bothered with them before). Plus it would mean not adding an additional server into my net just for a trivial SMB/file monitoring application. Thanks for the response. >> I've bumped into a library I can't resolve and I must have a >> disconnect >> in how the linux_compat works because I can't see how it could be >> solved. >> I have the following: >> * compat_linux enabled in the kernel, >> * /usr/ports/emulators/linux_base_fc7 >> * sysctl kern.fallback_elf_brand=3 >> * rpm2cpio to alter rpms >> * cpio to create the directories and place the files where they >> belong in /compat/linux. > >> I have a program that now has all it's libraries resolved but one in >> preparation to attempt to run the Linux Quickbooks install on >> FreeBSD. >> The ldd output, prior to installing /usr/ports/devel/fam (a required >> shared >> library) looks like this. > >> ldd ./opt/qbes7/util/qbmonitord >> ./opt/qbes7/util/qbmonitord: >> libfam.so.0 => not found >> libpthread.so.0 => /lib/libpthread.so.0 (0x28072000) >> libstdc++.so.6 => /usr/lib/libstdc++.so.6 (0x28088000) >> libm.so.6 => /lib/libm.so.6 (0x28171000) >> libgcc_s.so.1 => /lib/libgcc_s.so.1 (0x28198000) >> libc.so.6 => /lib/libc.so.6 (0x281a4000) >> /lib/ld-linux.so.2 (0x28054000) > >> I install fam to get rid of the not found, perform the following >> link: >> ln /usr/local/lib/libfam.so.0 /compat/linux/lib/libfam.so.0 > >> and then I get this: > >> ldd ./opt/qbes7/util/qbmonitord >> ./opt/qbes7/util/qbmonitord: >> ./opt/qbes7/util/qbmonitord: error while loading shared libraries: / >> lib/libfam.so.0: ELF file OS ABI invalid >> ./opt/qbes7/util/qbmonitord: exit status 127 > >> which kind of makes sense since this library is not a linux library. >> I'd read >> that I don't need to brandelf -t linux a library but I tried that >> anyway, >> realizing it was likely meaningless (or harmful). It didn't help of >> course. > >> My next thought was to try and get a libfam.so.0 binary from a linux >> distro >> but stopped when it occurred to me that it would be illogical since >> fam uses >> kqueue on FreeBSD rather than something called imon. imon is not >> available >> for FreeBSD so a linux version shouldn't be able to function if it >> expects that. On >> FreeBSD, fam configures itself to not use imon. > >> What is the appropriate course of action to get a linux flavor shared >> library >> for fam (or anything which runs into such conflicts) that will work >> on FreeBSD >> yet be recognized as suitable for linux under the compat mode? > > Try to create and use linux-fam port. I also tried this but it appears that gamin is a more recent implementation. It also provides the libfam.so.0. > > > WBR > -- > bsam > _______________________________________________ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "freebsd-questions- > unsubscribe@freebsd.org" >