Date: Fri, 28 Sep 2007 10:37:13 -0500 From: Dan Nelson <dnelson@allantgroup.com> To: vittorio <vdemart1@tin.it> Cc: freebsd-questions@freebsd.org Subject: Re: Compilation error libpcre.so.0: ELF file OS ABI invalid Message-ID: <20070928153713.GA62033@dan.emsphone.com> In-Reply-To: <200709280837.16084.vdemart1@tin.it> References: <200709280837.16084.vdemart1@tin.it>
next in thread | previous in thread | raw e-mail | index | archive | help
In the last episode (Sep 28), vittorio said: > Context: Intel Core Duo, FreeBSD 6.2-p7, latest portsnap, gcc-4.2.2. > Updating the statistical program R, some packages fail to compile (I use > tarballs) because this cryptic error pops up > > * Installing *source* package 'MCMCpack' ... > checking for C++ compiler default output file name... a.out > checking whether the C++ compiler works... yes > checking whether we are cross compiling... no > checking for suffix of executables... > checking for suffix of object files... o > checking whether we are using the GNU C++ compiler... grep: error while loading shared libraries: /usr/local/lib/libpcre.so.0: ELF file OS ABI invalid > yes > checking whether c++ accepts -g... grep: error while loading shared libraries: /usr/local/lib/libpcre.so.0: ELF file OS ABI invalid > yes > > It seems that during the compilation a-linux-connected-lib is being looked > for, doesn't it? > > Anyway, what should I do? I'd check $PATH and maybe $LD_PRELOAD for things pointing into /compat/linux . Moving /usr/compat/linux/lib/libpcre.so.0 out of the way might change the error message and help you track down the cause. Running "ktrace -d" or "truss -f" on your port build might help too. Another possibility is that the freebsd-port version of /usr/local/lib/libpcre.so.0 has gotten damaged somehow. FreeBSD's grep doesn't link with pcre so it's sort of unlikely that that would be the cause, though. -- Dan Nelson dnelson@allantgroup.com
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20070928153713.GA62033>