Date: Mon, 16 Jan 2006 11:45:49 -0800 From: Kael Fischer <kael.fischer@gmail.com> To: Steve Kargl <sgk@troutmask.apl.washington.edu> Cc: freebsd-amd64@freebsd.org Subject: Re: Docs for running 32-bit apps? Message-ID: <cd02cc220601161145o5dca76f5s8e4095f882eb0e05@mail.gmail.com> In-Reply-To: <20060116191915.GB15316@troutmask.apl.washington.edu> References: <cd02cc220601161027o22df47d6m1e9642e40e13f957@mail.gmail.com> <20060116183735.GA15021@troutmask.apl.washington.edu> <cd02cc220601161047p3ffd016cy1dc70e2f33538dea@mail.gmail.com> <20060116191915.GB15316@troutmask.apl.washington.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
> > b1# ldconfig -32 /usr/lib32 > > Do you have libstdc++.so.3 and libm.so.2 in /usr/lib32? > Does ldconfig -32 -r show a list of files. > No, that was the complete output from all those commands. [clip] > If you can't recompile raftercc and blasta for amd64, then try > to find the missing 32bit libs and drop them im /usr/lib32. > You could create a symlink to get libm.so.2 (although I don't > recommend this approach). A symlink probably won't work for > libstdc++.co.3 because the C++ ABI changed. So in the normal buildworld on amd64 these get built, right? I'm trying to figure out if the vendor just screwed up the build/installworld and I should just redo it. Anyway I'm rebuilding on a blade to test it. Besides GENERIC and SMP the conf is: options BGE_FAKE_AUTONEG so it seems like lib32 stuff should be standard. -Kael -- Kael Fischer, Ph.D DeRisi Lab - Univ. Of California San Francisco
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?cd02cc220601161145o5dca76f5s8e4095f882eb0e05>