From owner-freebsd-current Wed May 22 15:17:12 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id PAA03309 for current-outgoing; Wed, 22 May 1996 15:17:12 -0700 (PDT) Received: from covina.lightside.com (covina.lightside.com [198.81.209.1]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id PAA03300 for ; Wed, 22 May 1996 15:17:10 -0700 (PDT) Received: by covina.lightside.com (Smail3.1.28.1 #6) id m0uMMDG-0004JzC; Wed, 22 May 96 15:17 PDT Date: Wed, 22 May 1996 15:16:58 -0700 (PDT) From: Jake Hamby To: current@FreeBSD.ORG Subject: Can't run Linux static ELF binaries? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk I just discovered, while trying to upgrade my /compat/linux/lib directory to the latest version of ld.so (1.7.14), that both the new ldconfig and ldd coredump immediately when run. Both are statically linked ELF executables. As a workaround, I installed everything in the ld.so package except for ldconfig and ldd, and am still using the old a.out ldconfig and ldd from linux_lib-2.0. The only problem is that the old ldconfig doesn't properly recognize libc.so.5.3.16 and libm.5.0.6 as valid ELF libraries and links the old versions. Oddly enough, it does link the new version of libc to a file called "syntax_options". I was able to workaround by deleting the old libc and libm, and manually creating the proper symlinks to libc.so.5. If any of the Linux/ELF-meisters have a chance to look at this bug it would be a good idea. Personally, I'm busy with adding SVR4 compatibility from NetBSD, so I might find some bugs from that end, but don't have time to investigate this one. Thanks! ---Jake