Date: Mon, 9 Jan 2006 13:59:31 -0800 (PST) From: Eric Allman <eric@sendmail.org> To: FreeBSD-gnats-submit@FreeBSD.org Subject: amd64/91571: amd64 startup not initializing 32-bit librarys in ldconfig Message-ID: <200601092159.k09LxVcA001283@knecht.neophilic.com> Resent-Message-ID: <200601092200.k09M0F96040843@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
>Number: 91571 >Category: amd64 >Synopsis: amd64 startup not initializing 32-bit librarys in ldconfig >Confidential: no >Severity: non-critical >Priority: medium >Responsible: freebsd-amd64 >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Mon Jan 09 22:00:14 GMT 2006 >Closed-Date: >Last-Modified: >Originator: Eric Allman >Release: FreeBSD 6.0-STABLE amd64 >Organization: >Environment: System: FreeBSD knecht.neophilic.com 6.0-STABLE FreeBSD 6.0-STABLE #0: Sat Jan 7 14:01:13 PST 2006 root@newknecht.neophilic.com:/usr/obj/usr/src/sys/GENERIC amd64 >Description: It appears that the system startup scripts (notably /etc/rc.d/ldconfig) do not run a pass over the 32-bit libraries (e.g., /usr/lib32, /usr/local/lib32). As a result, 32-bit binaries immediately fail with "/usr/libexec/ld-elf.so.1: Shared object "libc.so.4" not found, required by ...". >How-To-Repeat: Start up the system. Execute a 32-bit binary. >Fix: Workaround is easy: hard-code the "ldconfig -32 ..." call in /etc/rc.local. True fix is probably to replicate /etc/rc.d/ldconfig into ldconfig32 and do a proper search there. Or maybe extend the existing script. >Release-Note: >Audit-Trail: >Unformatted:
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200601092159.k09LxVcA001283>