Date: Sun, 16 Nov 2008 19:15:12 -0800 From: "Peter Steele" <psteele@maxiscale.com> To: <freebsd-hackers@freebsd.org> Subject: RE: How can I add new binaries to the mfsroot image? Message-ID: <2ACA3DE8F9758A48B8BE2C7A847F91F23B5040@polaris.maxiscale.com> In-Reply-To: <Pine.GSO.4.64.0811161539450.1597@zeno.ucsd.edu> References: <2ACA3DE8F9758A48B8BE2C7A847F91F23B502B@polaris.maxiscale.com> <Pine.GSO.4.64.0811161539450.1597@zeno.ucsd.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
> How does it fail? There doesn't seem to be any error generated. Or at least I tried to capture stderr and got nothing. > Is the binary you added statically linked? The command I'm doing most of my testing with is gmirror. I pulled it from one of our operation FreeBSD boxes, and it appears to be referencing several shared libraries: # strings /stand/gmirror | grep '.so.' /libexec/ld-elf.so.1 libgeom.so.4 libsbuf.so.4 libbsdxml.so.3 libutil.so.7 libc.so.7 >Wild guess: the shared libraries are present somewhere else on the CD,=20 >which perhaps is either not mounted or not pointed to by LD_LIBRARY_PATH=20 >or similar until the fixit shell is run. All of these shared libraries exist under /dist, which is mounted as the FreeBSD CD. The first one is an absolute path that is in fact a symbolic link in the fixit shell that ends up pointing to a location under /dist. LD_LIBRARY_PATH is not set in the fixit shell, so I'm curious how these shared libraries are being located under /dist (the ones without the explicit path). I think you are right though, it might be related to the shared libraries. I'll try setting LD_LIBRARY_PATH explicitly to see if that solves the problem.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?2ACA3DE8F9758A48B8BE2C7A847F91F23B5040>